Allergen management in professional kitchens: from ingredient to plate, without gaps

In Europe, Regulation (EU) No 1169/2011 — commonly known as the FIC Regulation — requires food business operators to inform consumers about the presence of 14 major allergens in every dish on offer. In Switzerland, the equivalent obligations come from the Food Ordinance (LGV / LIV). Whichever side of the border you operate on, the principle is the same: if an allergen is present, it must be declared. Silence is not a legal option.

In practice, many professional kitchens still manage this with Excel lists, paper cards or wall charts in the dining room. These approaches work as long as recipes do not change, suppliers stay the same and nobody copies the wrong column. None of those conditions can be guaranteed.

Why manual lists create blind spots

The risk does not come from deliberate negligence. It comes from the number of times information must be re-entered by hand.

An allergen is first declared by the supplier on the product data sheet. Someone copies it into the ingredient register. Someone else carries it across to the recipe card. A third person adds it to the posted menu. At every step, a transcription error, a missed field or a partial update is possible.

This problem grows with the ordinary changes of kitchen life: a supplier replaced at short notice, a recipe adjusted because of a stockout, a sub-ingredient swapped. If the update is not propagated to all the downstream records, the menu shows information that no longer matches what is being served.

For a guest with an allergy, that gap can have serious consequences. For the establishment, it creates civil and criminal liability.

The cascade logic in CalcMenu

CalcMenu is built around a three-level data structure: ingredient, recipe and menu. Allergens are declared once, at the ingredient level. They propagate automatically to every recipe that uses that ingredient, and from there to every menu that includes that recipe.

If a supplier notifies you that their soy sauce now contains traces of sesame, you update the ingredient record. Every recipe containing that sauce — and every menu that depends on it — immediately reflects the updated allergen. You act in one place only.

The cascade works in the other direction too: if you look at a menu and wonder why the dish of the day is flagged for gluten, you can trace it back to the source ingredient in a few clicks. Traceability is complete and auditable.

What this changes in practice

For kitchen teams, the recipe editing screen shows allergens in real time as each ingredient is added. There is nothing to tick manually — the information is inherited. If an ingredient has not yet been qualified, CalcMenu flags it: the allergen list cannot claim to be complete if source data is missing.

For front-of-house staff or anyone managing displays, menus generated from CalcMenu include allergens in the expected format — text list, standardised symbols or both. The export can feed ordering kiosks, printed menus or ESL shelf labels without any additional data entry.

For quality managers and directors, allergen compliance reports are generated from actual production data, not from a static list written at the start of the year. If your establishment is subject to a food safety inspection, the documents are ready in minutes.

Two sets of regulations, one database

The main difference between the FIC Regulation (EU) and the Swiss LIV concerns disclosure channels: in the EU, Regulation 1169/2011 leaves the form of allergen information for non-prepacked food to each Member State — in France, for instance, it must be written, visible and legible, verbal information alone being insufficient; in Switzerland, information for food sold loose may be given orally, provided a clearly visible written notice says so and the information is available to staff in writing or can be supplied immediately by a knowledgeable person. CalcMenu handles both: exports are configurable to match the applicable regulatory context.

If you operate across multiple sites — for example establishments in France and sites in Switzerland — you work from a shared database with display rules adapted to each territory.

And in the United States?

The United States draws the line differently. Packaged food is governed by FALCPA, the federal allergen labelling law, which requires nine major allergens to be declared — sesame joined the list in January 2023. Restaurant food, by contrast, carries no federal declaration duty: the applicable rules come from the states. Massachusetts, for instance, requires allergen training for managers and an advisory notice on menus; California goes further with SB 68, which from July 1, 2026 requires chains with 20 or more locations to disclose all nine major allergens in writing for every menu item.

For an international operator, this only strengthens the case for a single source of truth: one allergen database able to serve the EU’s written formats, the Swiss oral-information-with-written-notice model — and now written per-item disclosure on US chain menus.

---

Allergen management is not something that can be handled with a static table. It is a data flow that must stay in sync with every recipe change, every supplier update, every menu adjustment. To see how CalcMenu manages this cascade in your own setup, request a demonstration.