Allergen management for hospitality: the system behind the answer

Last updated: August 2026 · ~10 min read

When a guest asks whether a dish contains sesame, somebody has to answer in about four seconds, and everything behind that answer either exists or does not. This guide is about what has to exist: where allergen data comes from, how it stays true when a recipe changes, what gets labelled, what the team has to know, and what record you are left holding afterwards. It covers the hospitality-wide system. For handling a guest list at a booked catering event, read the dietary guide linked at the end of each section.

1. The problems hospitality businesses hit with allergens

When a guest asks whether a dish contains sesame, somebody has about four seconds to answer. Everything behind that answer either exists or it does not, and in most businesses it half exists.

One person keeps the allergen file and everybody else trusts it. The file is a binder in the office or a spreadsheet on a shared drive, and most of the team has never opened it and would not know where to look. A recipe changed and the sheet did not, and nothing on the sheet says the sheet is out of date. Meanwhile the menu says one thing and the allergen sheet says another, because two different people typed those two documents by hand, months apart, and nobody has compared them since.

Suppliers move the ground underneath all of it. A reformulated sauce, or a product that moves to a factory which also handles nuts, changes your answer without changing your recipe.

And the person who gets asked is rarely the person who knows. Weekend staff and agency cover are asked exactly the same question your head chef is asked, often in their first week. Nobody has written down how the gluten free plate stays away from the bread either; the chef on duty keeps the two apart because that chef remembers to. Six months later, "what did you check" has no written answer at all.

2. What UK law asks for, in plain words

A food business in the UK has to give accurate information about the 14 allergens the Food Standards Agency regulates, and that information has to be available to the customer.

For food that is not prepacked, which covers most restaurant and catering service, the information can be written or signposted and given verbally, as long as it is accurate and consistently available. For prepacked for direct sale food, the kind of item a team makes and wraps on site before a customer orders it, a full ingredient list with allergens emphasised has to be on the pack. That is the rule most people know as Natasha’s Law.

Owen’s Law is coming and would require full written allergen information for diners rather than information on request. Read the Natasha’s Law guide and the Owen’s Law guide for the detail.

3. Data belongs at ingredient level, and nowhere else

This is the single decision that determines whether allergen management works at scale.

Tag allergens once, on the ingredient. Every recipe that uses the ingredient inherits the tag. Every menu built on those recipes inherits it again. Change a recipe and everything downstream updates on its own.

The alternative, declaring allergens on each dish, is workable for twenty dishes and impossible for four hundred. Worse, it fails silently: a dish whose recipe changed still carries the old declaration, and nothing about the document looks wrong.

Allergens tagged on the ingredient

4. Suppliers are part of your allergen data

Your allergen answer is only as good as the product specifications behind it, and those change without asking you. A supplier reformulates a sauce. A product moves to a factory that also handles nuts. A substitution arrives at the back door because the usual line was out of stock.

Two habits cover most of this. Record which supplier product each ingredient maps to, so a specification change has somewhere to land. And treat a delivery substitution as an allergen event, not just a stock one, because a swapped product is a different specification.

5. The outputs: matrix, labels, and the sheet the kitchen reads

Good allergen data produces three different documents for three different audiences, and all three should come from the same source.

• The matrix. Dishes against the 14 allergens, for the team and for the client.
• The label. For prepacked for direct sale items: food name, full ingredient list, allergens emphasised.
• The service sheet. What the kitchen and floor work from during service, with the affected covers visible.

If those three are maintained separately, they will eventually disagree, and the one that is wrong will be the one somebody read.

The matrix, generated

6. Booked events change the shape of the problem

Day-to-day service is a question-and-answer problem: a guest asks, you answer. A booked catering event is a planning problem: you know the guest list days ahead, so the work is to arrange in advance that every guest has something they can eat.

That is a different job with different outputs, and it is worth treating separately. Read dietary and allergen management for catering for the per-guest version: the replacement dish, the matrix attached to the BEO, and the sign-off.

7. The part software cannot do

Handling, storage and separation happen with hands. A system can carry the plan and record that somebody followed it. A system cannot keep the gluten free plate away from the bread.

What good practice looks like is unglamorous: separate prep areas or separate times, colour coded boards, labelled and covered containers, a plated dish carried and marked so it reaches the right seat, and a briefing before service that names which covers are affected.

Training is the same. Everyone who might be asked the question needs to know the process for answering it, including agency staff on their first shift. The right process is short enough to remember: do not guess, check the record, and escalate to the chef.

The answer, in a pocket

8. What this means for your role

9. What to check before you buy

• Allergens tagged at ingredient level and inherited by recipes
• All 14 regulated allergens, not a shorter list
• A matrix that regenerates when a recipe changes
• PPDS labels produced from the same data
• Supplier product mapping, so a specification change lands somewhere
• A required sign-off step with a name and a time on it
• A history you can show six months later
• Something that works on a phone during service

10. Questions people ask

11. Where Havenue fits

Havenue tags allergens from ingredient data and lets every recipe and menu inherit them, so a recipe change updates the matrix rather than leaving it stale. The matrix is generated from the same record as the BEO, every check carries a name and a time, and the whole thing is readable on a phone during service.

See the Dietary and Catering Engine, the BEO and allergen matrix and reporting and compliance.