What does a lawsuit cost a restaurant after a customer eats a "gluten-free" cake and ends up in the hospital? Behind every "contains / free-from / may contain traces" statement on a menu sits a chain of liability. The EU's Food Information to Consumers Regulation (1169/2011), the FDA's FALCPA in the US, and equivalent laws in most countries regulate this strictly.
"Contains": mandatory and absolute
If an EU-14 (or FDA top-9) allergen is in a menu item, a "contains" declaration is mandatory. This includes not just obvious ingredients like "milk" or "wheat" but opaque ones — casein in a dessert sauce, hidden wheat flour in a stock — that customers won't infer from the dish name.
Failure exposes the operator to administrative fines (Trading Standards in the UK, regional health authorities elsewhere) and, more dangerously, civil liability if a guest suffers a reaction.
"Free-from": binding, with the burden of proof on you
"Gluten-free", "peanut-free", "vegan" — the moment you write these on the menu, they become a guarantee. If a guest reacts, the burden of proof shifts to the restaurant: yes, we had verification procedures; yes, the supplier provided certification; yes, kitchen isolation was enforced.
If you can't prove "free-from," don't claim it. Use instead: "gluten-free recipe, prepared in a shared kitchen." That phrasing is honest and provides legal cover.
"May contain traces": precautionary allergen labeling
"May contain traces" — known as Precautionary Allergen Labeling (PAL) — is used when the allergen isn't a formal ingredient but cross-contact is possible. It shifts risk acceptance to the diner and gives the restaurant the "we warned you" position if a reaction occurs.
But overuse devalues the warning. If "may contain peanut" appears on every item, guests ignore it. Apply PAL selectively, only where genuine risk exists.
The liability chain
If a supplier mislabels an ingredient, the restaurant can pursue them in turn — but to the diner, the restaurant is the primary defendant. Archiving supplier certifications, tracking batch numbers, and dating menu changes are all essential for defense.
Digital menu systems like thMenu keep a version history: "on date X, item Y was marked with allergen Z." That trace becomes a critical evidence tool in a dispute. Static printed menus have no such record.
Practical formula
List every allergen present + add PAL where genuine cross-contact risk exists + only claim "free-from" when you can prove it. Those three principles balance legal exposure with customer trust — and they're cheaper than the smallest of allergic-reaction lawsuits.
Found this helpful? Share it.
Related articles
Why Digital Menus Increase Restaurant Revenue by Up to 30%
Studies show restaurants using digital QR menus see measurable increases in aver…
When a Customer Downgrades, What Happens to Old Features? — The Silent Feature-Drift Problem in SaaS
Most SaaS apps run a single line of code when a customer downgrades — but old fe…
JWT alg-confusion attack — why Supabase's HS256 → RS256/JWKS migration breaks legacy verifiers
Verifiers that never decode the JWT header are wide open to `alg=none` and alg-c…