Why Allergen Info Should Be Frozen on the Order, Not Just the Menu: Restaurant Allergen Records (2026)

August 4, 2026 at 2:20 PMTabres Team

allergen records food allergy compliance restaurant pos allergen traceability kitchen ticket

Your menu changes. Your orders can't. That single sentence is the whole argument, and most restaurant systems get it backwards.

Short answer: allergen information should be copied onto the order at the moment the guest orders — frozen, like the price — and carried through to the kitchen ticket, the bill and the receipt. If your order history just points back at today's menu, then every recipe edit you make quietly rewrites your own history. Change the bun supplier on Wednesday and Monday's order now shows Wednesday's allergens. That's not a record. That's a guess with a timestamp.

Restaurants spend months building allergen matrices and tagging dishes. Then they store the one thing that actually proves what happened — the order — as a pointer to a file they edit every week. Here's why that breaks, and how to fix it in an afternoon.

A menu is a document. An order is a record.

These two things have opposite jobs, and mixing them up causes most allergen data problems.

	The menu	The order
What it is	What you sell today	What you sold on that night
Should it change?	Constantly	Never, once placed
Who it's for	Guests choosing	Kitchen, guest, inspector, insurer, you
Lifespan	Until the next edit	Years

A menu is meant to be edited. You 86 the sea bass, you swap suppliers, you fix a typo in the allergen tags. All healthy.

An order is meant to be evidence. It says: on 12 March at 8:41pm, table 9 ordered this dish, and this is what we declared about it at that moment.

The moment your order reads from the menu instead of storing a copy, those two jobs collide. And the record always loses.

You already freeze the price. Do the same with allergens.

Nobody would accept a system where raising the burger price by $2 retroactively changes last month's receipts. Your accountant would lose their mind. Your tax office would lose theirs.

So every POS on earth freezes the price onto the order line. It copies the number at the moment of the sale, and that copy never moves again.

Allergens deserve exactly the same treatment. They're a declaration about a specific plate on a specific night, not a property of a menu entry that floats through time.

Here's the honest test for your own setup: change an allergen tag on a dish right now, then open an order from three months ago. If the old order shows the new tag, your allergen history doesn't exist. You have one version of the truth, and it's always today's.

Five ways this breaks in a real kitchen

None of these are hypothetical. They happen in ordinary weeks, in ordinary venues.

1. The supplier changed and nobody called you. Your bakery quietly reformulated the brioche in April to include sesame. You update the tag in May. Every order from January to April now claims it contained sesame — including the ones that didn't. Your data is now wrong in both directions, and you can't tell which is which.

2. Somebody fixed a mistake. A chef notices the risotto was never tagged for celery. Good catch. They fix it. And in one click, four months of orders that were served with the wrong declaration now look perfect. The mistake is invisible. You can't audit what you can't see, and you'll never learn how it happened.

3. The dish came off the menu. Seasonal special, deleted in October. Now open a September order. If your order line only holds a product ID, you get a blank, a dash, or "product not found". The order still exists. The allergen truth doesn't.

4. Delivery outran your edit. An order goes out at 7:10pm. At 7:25pm someone updates the menu. At 7:40pm the courier hands over a bag whose paperwork says one thing while the app says another. Delivery already has the highest rate of "that's not what I ordered" disputes — don't add allergens to that pile.

5. Two branches, two versions. Multi-branch groups often run slightly different recipes. If the order doesn't carry its own copy, a report across branches blends them into one fictional dish. It's the same class of problem as POS data that doesn't line up across locations, just with much worse consequences.

What "frozen" actually means

Frozen doesn't mean locked or read-only. It means copied. Plain and simple.

When the guest orders, the system takes a snapshot of the declared allergens and writes those values into the order line itself — as text or codes that live on that line forever. No lookup. No reference. No dependency on a menu that will change next Tuesday.

Three rules make a snapshot real:

Copy, don't point. The order stores the allergen names, not a link to the product.
Write once. Nothing that happens to the menu later can touch it.
Travel with it. Whatever the kitchen prints and the guest receives shows the same frozen values.

If you're wondering whether your system does this, ask your provider one question: "Are allergens stored on the order line, or looked up from the product?" The answer takes ten seconds and tells you everything.

The five places a frozen allergen has to show up

Freezing the data is only useful if people actually see it. Five surfaces, in order of how often they're missed:

The order line itself. The single source. Everything else is a view of this.
The kitchen ticket. The chef needs the declaration that was made, not the tag that exists now.
The bill. Guests sometimes check before paying — especially parents ordering for a child.
The receipt. This is your proof after the fact. A bill and a receipt are different documents, and the receipt is the one that survives.
The order export or history. The screen you'll open under stress, months later, when someone asks a hard question.

Miss number 5 and you've built a nice feature with no memory. That's the one that matters at 9am on a Monday when the phone rings.

The one night that decides whether you did this right

Picture it. A guest ate at your place eleven weeks ago. They had a reaction that evening. Now there's a letter, or an inspector, or an insurer, or all three.

Everyone asks the same four questions:

What did the guest order?
What did you declare about it at that moment?
Who took the order, and what was recorded?
Can you prove none of this was edited afterwards?

With frozen allergens, that's a two-minute answer with a printout. Without them, your best answer is "here's what the menu says today" — and everyone in the room knows the menu has been edited since. You're not lying. You just can't prove you're telling the truth, which in practice lands in the same place.

This is also the part people miss: frozen data protects your staff. The waiter who did everything right deserves a record that shows it. Memory doesn't hold up under questioning. A timestamped order line does. If you're building the floor routine around it, our food allergy protocol for waiters and kitchens covers the exact words and handoffs.

What the law expects: declaration is only half the duty

Most owners know the declaration rules. Far fewer know the record rules that sit underneath them.

The pattern is consistent almost everywhere: you must tell the guest what's in the food, and you must be able to show what you did. The first duty lives on the menu. The second one lives on the order.

Where	Declaration duty	The record part people forget
United States	Federal law names 9 major allergens (milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans, sesame). Menu labelling isn't required federally, but the FDA Food Code expects allergen-aware management	Records are what your insurer and any civil claim will run on. In the US the real pressure isn't an inspector — it's discovery in a lawsuit. States like Massachusetts, Rhode Island, Illinois and Michigan add their own menu-notice or staff-training rules, and being able to show training plus order records is what turns a claim into a non-event
United Kingdom	Allergen info must be available for non-prepacked food, with a clear notice pointing to it. The FSA recommends written allergen information plus a spoken check at the point of order. Pre-packed for direct sale needs full labelling (Natasha's Law)	Environmental Health officers ask how you know. A written record of what was communicated is a core part of a due-diligence defence under food safety law
EU baseline	14 allergens declared for every dish, available before the guest orders (Regulation 1169/2011). Each country sets the method under Article 44	Regulation 178/2002 Article 18 requires traceability — one step back, one step forward. Your HACCP plan is expected to be documented and kept. Orders are the cleanest proof that the plan was followed on a given date
Ireland	In writing, clear and legible, without the guest having to ask (FSAI)	The FSAI expects the information to be current and verifiable — which means dated records, not a folder someone updated "recently"
Australia & NZ	The FSANZ Food Standards Code names the declarable allergens, and Plain English Allergen Labelling (PEAL) has been mandatory since February 2024	State and territory food authorities audit process, not just signage
Canada	CFIA and Health Canada name the priority allergens; provincial rules cover food service	Provinces such as Ontario require allergen-aware procedures and staff training in food premises — procedures you have to evidence

Two things hold nearly everywhere:

Nobody prescribes "freeze allergens on the order" by name. No law uses that phrase. But every framework asks you to prove what you did on a specific date, and a frozen order line is the cheapest way to do it.
Retention periods vary. Some countries expect food safety records kept for months, others for years. Ask your local authority once, write the number down, and set your system to keep orders at least that long.

Check your own regulator before you rely on any of this: the FDA and your state health department in the US, the FSA in the UK, the FSAI in Ireland, AESAN in Spain, the NVWA in the Netherlands, FSANZ in Australia and New Zealand, CFIA in Canada. For the full country-by-country picture in Europe, our guide to restaurant allergen menu requirements in Europe breaks down how the method changes at each border.

The reasons owners actually do it (none of them are legal)

Compliance gets people to nod. These get people to act.

Insurance. After an incident, the first thing an insurer asks for is documentation. Good records shorten a claim from months to weeks — and sometimes decide whether you're covered at all.
The review you can't answer. "They told me it was dairy free." Without a record, you're arguing with a public post using your memory. With one, you can respond calmly and factually. Our guide on replying to bad restaurant reviews covers the tone that works.
Staff turnover. The waiter who took that order left in June. Your system is the only witness left.
Sleep. Genuinely. Owners who've been through an allergy scare describe the record as the thing that let them stop replaying the night in their head.
It makes allergen data get maintained. Data that's used seriously gets updated seriously. Data that's decorative rots.

There's a local flavour to this too. In tourist towns, the allergy question arrives in five languages and the guest can't verify anything you say — so trust does all the work. In small towns, the guest is a neighbour, and a bad night follows you around for years. In cities with an active claims culture, the record is simply cheaper than the argument. Same practice, three completely different motivations.

Free text is not a substitute for structured allergen data

Almost every POS has an order note. Most kitchens use it for allergies: "NUT ALLERGY — table 4".

Keep doing that. It's essential. But a note is not the same thing as a frozen allergen field, and using one to replace the other is a common, expensive mistake.

	The order note	The frozen allergen field
Comes from	The waiter, at the table	The product's declaration
Says	What the guest can't eat	What the dish contains
Format	Free text, typed in a hurry	Structured codes or names
Searchable later?	Barely	Yes — filter, count, export
Fails when	It's misspelled, vague, or in the wrong field	The product was never tagged

You need both, and they answer different questions. The note captures the guest. The frozen field captures the plate. An incident review needs the two side by side — that's when you can see whether the declaration and the request actually lined up.

One floor rule that costs nothing: the allergy goes onto the order as text, never onto a waiter's hand or memory. Allergy requests are really just dish changes, so the kitchen needs a routine for them — handling off-menu orders covers how to say yes without chaos.

Delivery and takeaway: the order you never get to explain

There's no waiter standing there. No "just to check — this contains milk, is that OK?" The order leaves and the conversation is over.

That makes freezing non-negotiable for off-premise sales:

The online menu must show allergens before the guest confirms — same duty as the dining room.
The frozen values must print on the bag label or the driver's slip.
The receipt must carry them, because it's the only document the guest keeps.
The order must still make sense an hour later, after someone edited the menu mid-service.

Delivery is also where a small mismatch becomes a public one. Marketplace complaints are visible, permanent and fast. Getting the paperwork right costs one line of setup. Getting it wrong costs a chargeback, a review and possibly a lot more. If you're working out whether the channel even pays, our real financial math on third-party delivery is worth ten minutes.

Set it up this week

You probably have the hard part — the allergen matrix — already. This is plumbing.

Run the three-month test. Change one allergen tag. Open an old order. If it changed too, you now know your gap. 2 minutes.
Ask your POS provider the one question. "Are allergens stored on the order line or looked up from the product?" Get it in writing. 5 minutes.
Turn on allergens for kitchen tickets and receipts. Most systems have the toggle; almost nobody has it on. 10 minutes.
Tag your top 20 dishes first. They're roughly 80% of orders. 30 minutes.
Stop deleting products. Hide or disable them instead. A deleted product takes its history with it. Policy change, 0 minutes.
Check your retention setting. Make sure orders are kept at least as long as your local rules ask. 10 minutes.
Print one order and read it like an inspector. Does it answer the four questions above? 5 minutes.

If you're still choosing a system, ask about allergen freezing during the demo rather than after — it's much harder to add later. Our breakdowns of restaurant POS system costs and hidden POS fees to watch for cover the rest of the shopping list, and switching without retyping your menu removes the usual excuse for staying put.

If your system can't freeze allergens

Some tools just don't do this yet. You're not stuck — you're just doing it manually.

Keep the kitchen ticket. A printed ticket with allergens on it is a frozen record. Box them by month. Cheap and effective.
Export orders weekly to PDF or spreadsheet, with allergen columns included, and store the export somewhere you can't edit it.
Version your menu. Save a dated PDF every time you change allergen data. A menu with a date beats a menu without one.
Log recipe changes in one shared sheet: date, dish, what changed, who approved it. Five seconds per change.
Never delete, always disable. This one habit saves more history than any other.

None of it is elegant. All of it works. And it costs nothing but discipline until you upgrade.

What good looks like on the plate

For what it's worth: Tabres freezes the declared allergen codes onto each order line at the moment of ordering, so the kitchen ticket, the bill and the receipt all show what was declared then — across all 15 declarable allergens, in every menu language you publish. It's free, and our reasoning for that is public.

Use whatever tool suits your kitchen. The principle travels: copy the declaration onto the order, and never let the menu edit the past.

Seven mistakes that quietly destroy your allergen history

Storing a product link instead of a copy. Every menu edit rewrites the past. Fix: snapshot on order.
Deleting old products. History disappears with them. Fix: disable, never delete.
Allergens on the menu but not on the kitchen ticket. The chef cooks blind. Fix: print them.
No allergens on the receipt. The guest's only copy says nothing. Fix: turn it on.
Using the order note as the whole record. Free text isn't searchable or complete. Fix: use both.
Editing an old order "to correct it". That's not a correction, it's tampering. Fix: add a dated note instead.
Keeping orders for 30 days. Allergy questions arrive months later. Fix: match your local retention rule.

Frequently asked questions

What does it mean to freeze allergen info on an order? It means the system copies the dish's declared allergens onto the order line at the moment the guest orders, and stores that copy permanently. Later changes to the menu never affect it. The kitchen ticket, bill and receipt all show the values as they were on that date.

Why isn't it enough to have allergens on the menu? Because a menu shows what's true today, and an order needs to show what was true then. Recipes change, suppliers change, and tags get corrected. If your order only points at the menu, every edit silently rewrites your own history.

Is freezing allergen data a legal requirement? No law uses that wording. But food safety frameworks in the EU, UK, US, Canada, Australia and New Zealand all expect you to show what you did on a specific date, and traceability rules like EU Regulation 178/2002 Article 18 assume you can. A frozen order line is the simplest way to meet that expectation. Check your own regulator for the exact duties where you trade.

How long should I keep order records with allergen data? It varies by country and by the type of record, from months to several years. Ask your local food authority once, note the answer, and configure your system to keep orders at least that long. When in doubt, longer is cheaper than shorter.

Does the order note cover this instead? No. The note records what the guest told you. The frozen allergen field records what the dish contained. You need both — an incident review compares them, and each one is useless on its own.

Should allergens print on the kitchen ticket? Yes. The chef is the last person who can stop a mistake, and they shouldn't have to check a screen or remember a tag. The ticket should show the frozen declaration plus the guest's own allergy note.

What about delivery and takeaway orders? Same duty, higher risk, because there's no waiter to double-check. Allergens must be visible on the online menu before the guest confirms, and travel with the order on the bag label and the receipt.

What if I fix an allergen mistake on a dish — does that change old orders? It shouldn't. Fixing the product is right and you should do it immediately. But old orders must keep the declaration that was actually made at the time. If they change, you've lost the ability to find out how the mistake happened.

Can I just print and keep the tickets? Yes, and it's a genuinely valid fallback. A dated printed ticket showing the allergens is a frozen record. Box them by month and store them for as long as your local rules require.

How do I check whether my POS does this? Change one allergen tag on a dish, then open an order from a few months ago. If the old order shows the new tag, allergens are being looked up, not frozen. Ask your provider to confirm in writing.

Do allergens need to be frozen in every menu language? If you publish the menu in several languages, the guest's receipt should be readable by the guest. Store the codes once and render them per language — the record stays consistent while the words change. Our guide to declaring allergens on a digital menu covers the layout side.

Where do I start if I've never tagged allergens at all? Start with the allergen list itself, then tag your twenty best sellers. Our guide to the 15 food allergens restaurants must know has every name plus the one most menus miss, and training staff to handle it turns it into a floor habit.

Here's the summary worth remembering. Your menu is a promise about today. Your order is a record of a night. Those are different jobs, and one file can't do both.

Freeze the allergens onto the order, print them on the ticket and the receipt, and stop deleting products. Twenty minutes of setup buys you something you'll probably never need — and will be extremely glad to have if you ever do.