If you run a food business in the EU or UK, allergen documentation is not optional paperwork. It is the record of how you protect customers from a known and potentially severe hazard. When an inspector asks to see your allergen records, they are not checking a formality. They are checking whether the business actually knows what allergens are present, how that information reaches the customer, and what controls exist to stop cross-contact or misinformation.
In practice, most businesses need a core set of allergen documents covering ingredients, recipes, product or menu declarations, customer communication, cross-contact controls, and staff training. Higher-risk or more complex operations often need more than that, especially where PPDS, manufacturing, or multi-site control is involved.
This is practical guidance for EU and UK food businesses, not legal advice. It explains what the documentation usually needs to achieve and how to keep it usable in real operations. If you want the wider PinkPepper logic behind this kind of answer, see our methodology and the regulations covered page.
Why allergen documentation matters
Allergen control is one of the clearest examples of why documentation matters in food safety. Staff memory is not enough, verbal assumptions are not enough, and a menu statement on its own is not enough. If the business cannot trace an allergen answer back to written and current information, the system is weak.
Allergen documentation matters for three practical reasons:
- Accuracy: you need a reliable record of which allergens are present in ingredients and finished foods.
- Traceability: if a supplier changes a formulation, a customer reports a reaction, or an inspector tests your process, you need to follow the information chain quickly.
- Proof of control: inspectors and auditors want to see that allergen management is systematic rather than based on memory or goodwill.
For a customer with a serious allergy, the consequences of bad information can be immediate and severe. That is why allergen documentation is treated as a core operational control, not an administrative extra.
The core allergen documents most businesses should maintain
The exact format varies by business model, menu complexity, product range, and operational risk. But most EU and UK food businesses should be able to produce the following core documents without hesitation.
1. Ingredient specifications and supplier allergen information
Allergen control starts with knowing what is in the ingredients you buy. For each relevant ingredient or supplier item, the business should hold documented allergen information that is current enough to trust and structured enough to use.
That usually includes:
- supplier specifications showing which allergens are intentionally present
- relevant handling or cross-contact declarations where they affect the control decision
- records showing when the information was obtained or reviewed
- a process for updating the file when suppliers or formulations change
A label or invoice is not always enough on its own. The important point is that the business can show where the allergen information came from and why it is still considered current.
2. An allergen matrix or equivalent product-level record
An allergen matrix is one of the most practical working documents a food business can maintain. It translates supplier and recipe information into a format that staff can actually use during service, production, or review.
A useful matrix should:
- list each menu item or finished product
- show which regulated allergens are present
- be based on verified ingredient and recipe data
- be updated when recipes, ingredients, or suppliers change
- be accessible to the people answering customer or inspector questions
The allergen matrix template is the simplest way to make this practical without starting from a blank spreadsheet.
3. Recipe or formulation records with allergen control built in
Allergen information needs to be grounded in the actual recipe or formulation, not just a top-level summary sheet. Recipe records should make it possible to see which ingredients drive the allergen declaration and how any changes affect the final product or dish.
That is especially important when:
- a supplier changes a sauce, spice blend, or compound ingredient
- the kitchen swaps one branded ingredient for another
- a garnish, topping, or side item changes the final allergen profile
- the production recipe differs from the menu or product name in a meaningful way
Without recipe-level control, the allergen matrix becomes harder to trust and harder to update properly.
4. Customer-facing allergen communication records
The business also needs a documented route from the internal allergen records to the information given to the customer. That could include menus, allergen folders, printed guides, product labels, or a controlled verbal process supported by written records.
The key point is consistency. If the internal matrix says one thing and the menu or staff answer says another, the documentation system has failed.
For hospitality businesses, that often means a written source staff can check before answering. For retail or manufacturing businesses, it usually means the finished label or product declaration must tie back to the controlled allergen records behind it.
5. Cross-contact control documentation
Knowing which allergens are intentionally present is only one part of the picture. You also need records showing how cross-contact is controlled during storage, preparation, production, cleaning, and service.
Depending on the business, that may include documented controls for:
- segregated storage of allergenic ingredients
- dedicated or controlled use of equipment and utensils
- clean-down between allergen and non-allergen work
- production sequencing
- fryer management or shared-oil decisions
- rework decisions in manufacturing
These controls do not all need to live in one document, but the record trail needs to exist. If you need to strengthen the hygiene side of this, the cleaning and disinfection SOP is the right support document.
6. Staff training records for allergen awareness
Staff training is part of allergen documentation because people are often the last link between the written system and the customer. The business should be able to show that relevant staff have been trained in allergen awareness, customer communication, and the local process for checking information rather than guessing.
That usually includes records for:
- initial allergen awareness training
- refresher training
- training after recipe, menu, or process changes
- role-specific instruction where customer communication or production control is involved
The employee food safety training record is the simplest supporting template here.
What higher-risk or more complex businesses may also need
Some businesses need a broader allergen-documentation pack because the operational risk is higher or the workflow is more complex.
PPDS-specific control records
Where the business handles prepacked food for direct sale, the documentation needs to support accurate labelling based on current ingredient and recipe information. That usually means tighter control between supplier specifications, recipe versions, and the final label workflow.
If PPDS is part of the operation, it is also worth linking this article with the more specific page on Natasha's Law and PPDS allergen obligations.
Supplier assurance and change-notification controls
Larger or more technical businesses often maintain stronger supplier-assurance records for allergen control, especially where compound ingredients, contract manufacturing, or imported ingredients are involved.
Verification or testing records
Some businesses include allergen verification activity such as post-cleaning checks, swab testing, or other structured review. Where that exists, the records should sit clearly inside the allergen control system rather than floating separately.
Production scheduling and rework controls
Manufacturing or central production sites that handle multiple allergen profiles often need clearer records on run sequencing, rework control, and product-change decisions to show how cross-contact risk is being managed.
Common allergen-documentation mistakes
Relying on memory instead of records
"The chef knows" or "the staff just ask the kitchen" is not a control system. If the answer is not backed by a written and current record, the process is too fragile.
Failing to update the documents when something changes
Supplier changes, recipe substitutions, menu edits, and reformulations are where allergen systems often break. A matrix that was right last month may be wrong today if the process for updating it is weak.
Incomplete ingredient breakdowns
Compound ingredients such as sauces, spice blends, coatings, and bakery mixes often hide the real allergen logic. If the business only records the top-level ingredient name and not the relevant allergen profile behind it, the documentation is incomplete.
Treating cross-contact as an afterthought
Many teams document declared allergens well but barely record how cross-contact is prevented. That leaves a major gap between the documented ingredient truth and the actual service or production reality.
Confusing "contains" with "may contain"
Precautionary statements and declared ingredients are not the same thing. The documentation should make that distinction clear and show how the business interprets supplier information inside its own customer communication and risk decisions.
How to keep allergen documentation usable
- Build one source of truth. Supplier specs, recipe files, matrices, and customer-facing information should connect instead of drifting separately.
- Keep the records accessible during service or production. If staff cannot reach them quickly, the system will break at the point of use.
- Review on a schedule and on change. Periodic review matters, but so does immediate review when an ingredient, supplier, or recipe changes.
- Train in layers. Formal training helps, but short refreshers around changes and near-misses are often what keep the system alive.
- Run your own trace-back checks. Pick a product and make sure the team can follow its allergen profile back through the internal documents without confusion.
If the whole system is becoming too fragmented across paper files and disconnected spreadsheets, that is usually the point where businesses need a tighter workflow. The practical route is the allergen matrix template, the food safety document checklist, the staff training record, and the wider PinkPepper workflow on pricing.
Conclusion
Allergen documentation is the written proof that your business knows what allergens are present, how that information is communicated, and how cross-contact is controlled. The exact format can vary by business, but the principle does not. If the information is not documented, reviewed, and accessible, the business is too exposed.
The strongest systems are the ones that operators actually use: current supplier information, an updated allergen matrix, clear recipe and change control, customer-facing consistency, and training records that prove staff understand the process. That is what makes allergen documentation hold up under pressure.
Frequently asked questions
Do I legally need a document called an allergen matrix?
No. The law does not require that exact document name. But you do need a reliable written system that allows the business to provide accurate allergen information and prove how it is controlled. In practice, an allergen matrix is one of the most useful formats.
How often should allergen documentation be updated?
Whenever ingredients, suppliers, recipes, labels, or product composition change in a way that could affect allergen information. Routine review on a regular schedule is also important to make sure the records remain current.
Do small cafes and restaurants need the same allergen documentation as manufacturers?
No. The depth should be proportionate to the business model and risk. But even a small hospitality business still needs accurate written allergen information, a controlled way to communicate it, and evidence that staff understand the process.
Is PPDS a separate allergen-documentation issue?
It sits inside the same overall allergen control system, but businesses handling PPDS usually need tighter label-control documentation and stronger links between ingredients, recipes, and final customer-facing information.
Can I rely on staff knowledge if the menu is simple?
No. Staff knowledge helps, but it should be backed by written and current records. Simplicity reduces complexity, not the need for documentation.
What should I do if a customer reports an allergic reaction?
Take it seriously, document the incident, review the records for the product immediately, and assess whether the system failed through ingredients, communication, or cross-contact control. The incident and the response should become part of your corrective-action record.
Next steps
- Use these templates: Allergen matrix template, food safety document checklist, and employee food safety training record
- Read next: Natasha's Law and PPDS allergen obligations
- See the trust layer: How PinkPepper forms answers and which EU and UK rules it is grounded in
- Create a free account: Keep allergen records, updates, and customer-facing documents in one workflow.