In October 2021, Natasha's Law came into force in England, Wales and Northern Ireland, tightening the rules around allergen labelling for food prepacked for direct sale. Named after Natasha Ednan-Laperouse, who died in 2016 after eating a baguette that contained sesame — an allergen not declared on the packaging — the legislation was a direct response to a preventable tragedy.
The law itself is well understood by now. Food businesses broadly know what it requires. The harder question — and the one this piece is concerned with — is what happens beyond the label. Because labelling is the beginning of allergen compliance, not the end. Most incidents do not happen because a business failed to print the right words on a packet. They happen in the gap between what the menu says, what the kitchen prepares, and what the guest receives.
That gap is a systems problem. And it has a systems solution.
The 14 regulated allergens
UK food law requires businesses to declare the presence of 14 specific allergens whenever they appear as ingredients in a dish. These are not obscure substances — they are common ingredients that appear throughout a typical hospitality menu, often in places that are not immediately obvious.
The requirement to declare these allergens applies to food served in restaurants, cafes, pubs, hotels, takeaways, and any other food service business — not only to packaged products sold in retail. If a dish on your menu contains any of these ingredients, your guests have a legal right to that information before they order.
Where compliance actually breaks down
The businesses that get into difficulty with allergen compliance are rarely those that have chosen to ignore the rules. They are typically businesses that have systems in place — a menu with allergen information, a staff training programme, a process for handling allergen queries — but where those systems have gaps the business has not identified.
Allergen information on a printed menu or website is only accurate if it reflects what the kitchen is actually preparing today. When suppliers change, when a chef substitutes an ingredient, when a seasonal special is added mid-week — the menu and the kitchen can quietly diverge. Nobody intends this to happen. It happens anyway, through the ordinary churn of a working kitchen.
A guest tells their server they have a nut allergy. The server tells the kitchen verbally. The kitchen is in the middle of a busy service. The message either does not reach the right person, or it reaches them without the context needed to act on it correctly. Verbal allergen communication is the weakest link in the chain — not because staff do not care, but because human memory and verbal handoffs degrade under pressure.
On a standard kitchen printer ticket, an allergen note is a line of text alongside everything else on the order. Under the conditions of a busy service — noise, speed, multiple tickets — there is no guarantee that line is read, processed, and acted upon correctly every single time. Consistency is not achievable through attention alone.
A dish is updated. The allergen information for the new version is known to the head chef. It has not yet been updated on the menu boards, the QR code, the delivery platform listing, or the EPOS product file. In the window between the change and the update, the information guests receive is wrong.
A guest with a severe allergy to nuts orders a dish that contains no nuts. The dish is prepared on a surface or with equipment that has been used for a nut-containing dish and not adequately cleaned between uses. The guest has a reaction. The business believed it was compliant because the dish itself contained no allergens — but cross-contamination in food handling is part of the legal duty of care, not a separate informal concern.
"Most allergen incidents do not happen because a business ignored the rules. They happen in the gap between what the menu says, what the kitchen prepares, and what the guest receives."
The legal exposure is real
A failure in allergen compliance is not primarily a reputational risk or a customer service issue — though it is both of those things. It is a criminal liability. Under the Food Safety Act 1990 and the Food Information Regulations 2014, providing inaccurate allergen information that causes harm can result in prosecution, unlimited fines, and in the most serious cases, imprisonment.
The defence of "the staff member made a mistake" is not a complete defence under food safety law. Businesses are required to have adequate systems in place to prevent allergen information failures. A system that depends entirely on individual staff members remembering verbal instructions under pressure is not, in the eyes of regulators, an adequate system.
The Food Standards Agency conducts enforcement visits, and allergen compliance is among the areas inspectors examine. A business that cannot demonstrate a documented, systematic approach to allergen management — not just a printed menu and a training record — is exposed.
What a proper system looks like
The gap between having allergen information and communicating it reliably at every point of the guest journey is where technology does its most important work. A well-configured EPOS and kitchen display system does not just help with compliance — it makes consistent compliance achievable in a way that manual processes cannot.
When allergen information is stored against each menu item in the EPOS product database, it travels with the item everywhere it appears — on the till screen, on the order receipt, on the kitchen display. Staff do not need to remember which dishes contain which allergens. The system carries that information consistently, and it is updated centrally when the dish changes.
When an order containing an allergen-sensitive item reaches the kitchen display, the allergen flag is shown prominently alongside the item — not as a footnote on a printed ticket, but as a clear visual indicator that is part of how the order looks on screen. A chef does not need to search for the information. It is there, every time, for every order that requires it.
QR ordering, table ordering apps, and online menus powered by the same EPOS product file display allergen information automatically at the point where the guest makes their choice. The guest sees the information before they order, not after the dish arrives. This is the point in the process where informed consent actually happens.
When a guest with an allergy places an order and notes their requirement, that note is attached to the order record in the system. It reaches the kitchen as part of the order, on the same display as the items being prepared. There is no verbal handoff. There is no risk of the message being lost between the floor and the pass.
When a dish changes, the allergen update is made once, in the EPOS product file, and it propagates to every channel simultaneously — the till, the QR menu, the kitchen display, the website integration. There is no window where the printed menu and the digital menu disagree. There is no version of the dish with the old allergen information still in circulation.
Training and technology together
Technology does not replace the need for staff training on allergen awareness — it makes that training more effective. When staff know that allergen information is embedded in the system and will appear automatically, they can focus their training on the edge cases: how to handle a guest who discloses an allergy after ordering, what to do when a dish has been prepared and a concern arises, when to escalate to a manager rather than make a judgement call.
The staff member at the till who takes an order from a guest with a severe allergy is not the last line of defence in a well-designed system. They are one part of a chain in which the product file, the kitchen display, the preparation protocol, and the serving process all carry the same information. That redundancy is what makes consistent compliance achievable at scale, through shift changes, through busy services, and across multiple sites.
A practical starting point
For operators who want to improve their allergen compliance posture, the most useful first step is usually an audit of where allergen information currently lives and how it travels through the operation:
- Is allergen information stored in the EPOS product file, or maintained separately in a spreadsheet or printed document?
- When a menu item changes, what is the process for updating allergen information across every channel it appears on?
- How does allergen information from a guest at the point of ordering reach the kitchen — verbally, or through the order system?
- What does a kitchen ticket or display show when an order contains an allergen-relevant item?
- Do staff know what to do when a guest discloses an allergy that was not noted at the point of ordering?
The answers to those questions will identify where the gaps are. Most of the gaps that create legal exposure are not the result of indifference — they are the result of processes that work well enough most of the time, but are not systematic enough to be reliable all of the time.
That is the standard the law holds food businesses to. Reliable, not usually. The technology exists to meet it. The question is whether the systems in place are designed to deliver it.