Allergens at the Restaurant: the Legal Obligations (EU Reg. 1169/2011)

Table 8, two covers. A guest asks the server: “My son is allergic to peanuts. Severe. Is there any tree nut in the pesto?” The server, in a rush, gives the answer that sounds reasonable: “No, don’t worry, it’s just basil.” Wrong: that pesto is finished with cashews instead of pine nuts. In the best case it ends with a guest who never returns. In the worst, with an ambulance outside the door and a lawsuit.

Allergens aren’t a “modification” like any other. They’re the one area of dish management where a mistake can put a person’s life at risk — and where the law leaves no room for interpretation. This is the practical guide to obligations, penalties, and the operational handling of allergies and intolerances at the restaurant in 2026.

Allergy, intolerance, preference: three different things

Before the law, conceptual clarity. Confusing these three is the root of most mistakes.

• Allergy: an immune-system reaction to a substance. It can be mild (itching, hives) but also extremely severe, up to anaphylactic shock, potentially fatal within minutes. It’s a safety matter, full stop.
• Intolerance: the body’s difficulty digesting a substance (lactose being the classic). It causes unpleasant symptoms — bloating, pain, gastrointestinal trouble — but isn’t life-threatening.
• Preference: a choice of taste or diet (“I don’t like cilantro,” “I avoid carbs”). No health risk.

The distinction matters because it sets the level of rigor. Preferences fall under normal service flexibility, which we cover in the guide on what to accept and what to refuse. Allergies and intolerances carry a different weight — and for allergens the law imposes specific obligations. Let’s look at them.

The 14 allergens you must declare

The reference, across the European Union, is Regulation EU 1169/2011 (the “FIC” regulation, Food Information to Consumers), which applies to food service too. Its Annex II lists the 14 categories of allergenic substances that must be declared to the consumer:

1. Cereals containing gluten (wheat, rye, barley, oats, spelt, kamut and derivatives)
2. Crustaceans and products thereof
3. Eggs and derivatives
4. Fish and derivatives
5. Peanuts and derivatives
6. Soybeans and derivatives
7. Milk and derivatives (including lactose)
8. Tree nuts (almonds, hazelnuts, walnuts, cashews, pistachios, pecans, etc.)
9. Celery and derivatives
10. Mustard and derivatives
11. Sesame seeds and derivatives
12. Sulphur dioxide and sulphites (above 10 mg/kg or mg/l)
13. Lupin and derivatives
14. Molluscs and derivatives

These 14 — no more, no fewer — are the allergens subject to mandatory declaration in the EU. (Outside the EU the lists are similar but not identical: the US, for instance, regulates a “Big 9” under FALCPA, adding sesame in 2023.) Knowing them by heart is the first duty of anyone in the kitchen and on the floor.

The obligation: what the law actually says

The Regulation’s principle is simple: the guest must be able to know, before ordering, whether a dish contains one of the 14 allergens. The obligation applies to every venue serving ready-to-eat food: restaurants, trattorias, pizzerias, bars with a kitchen, canteens, catering.

How must the information be given? The law allows several formats, but with one fundamental constraint: it must rest on a written support. The accepted options are:

• Direct indication on the menu, next to each dish (e.g. with a numeric legend or symbols)
• A dedicated register or document available on request
• A clearly visible sign pointing to the documentation

What is not compliant is relying solely on staff’s verbal information. The classic accepted formula is: “For information on substances and allergens, please consult the dedicated documentation provided by our staff.” But that documentation must genuinely exist, be up to date, and be easily accessible — both to the guest and to the inspecting authority.

An often-overlooked point: the information must be truthful and current. If you change an ingredient or a supplier, the allergen sheet must be updated accordingly. A menu declaring “gluten-free” a dish that no longer is, is worse than a menu declaring nothing. (This is precisely the gap the UK’s Natasha’s Law closed in 2021, after a fatal reaction to an undeclared allergen.)

The penalties: up to €24,000

Italy’s penalty regime sits in Legislative Decree 231/2017, which implemented the European Regulation. The fines are administrative and vary by type of violation:

• Failure to declare allergens: fines that can reach up to €24,000.
• Information given in a non-compliant, incomplete, or misleading way: fines starting around €1,000 and rising with severity.

But the fine is only part of the exposure. The most serious consequence of mishandling allergens is liability if a guest has a reaction: if someone suffers an allergic reaction because of wrong or omitted information, the operator can be liable for damages, with implications far beyond the administrative fine. That’s why allergen handling shouldn’t be seen as box-ticking, but as a safety procedure.

The figures cited are indicative and refer to the regime in force in 2026. For specific cases and updates, always refer to the applicable law in your jurisdiction and to professional advice. This article is informational and does not replace legal counsel.

Cross-contamination: the risk you don’t see

Declaring ingredients correctly isn’t enough. The most insidious risk is cross-contamination: traces of an allergen ending up in a dish that, on paper, shouldn’t contain it. Typical examples:

• The same fryer used for chips and for breaded rolls (gluten)
• The knife that cuts cheese first and fruit next (milk)
• The ladle moving from a shellfish sauce to another dish
• The same work surface for normal bread and gluten-free bread

For a celiac or severely allergic guest, even a trace can trigger a reaction. Correct handling means dedicated stations, utensils, and procedures when preparing a “free-from” dish, and honest communication of your limits: if you can’t rule out contamination, you must say so. “We can prepare a dish with no gluten in the ingredients, but we work with flour in the kitchen and can’t guarantee the total absence of traces” is an uncomfortable but correct sentence — and infinitely better than a false “don’t worry.”

Here, floor-to-kitchen communication is decisive: an allergy flagged at the table must reach the brigade unambiguously, not muttered in passing. It’s one of the themes of floor-to-kitchen communication and the expediter.

Operational handling: from booking to plate

The difference between a restaurant that handles allergens well and one that improvises isn’t goodwill, it’s process. A solid flow has four steps.

1. Capture the information at booking. An “allergies and intolerances” field in the booking form lets you know in advance who’s coming and what they need. It’s the most valuable moment, because it gives you time to prepare. The same principle we apply to the celiac guest and the bread basket, covered in coperto, celiac disease, and allergies.

2. Carry it into the pre-shift briefing. The allergy captured at booking must appear in the daily briefing: “Table 8, 8:30 PM, severe peanut allergy.” That way the whole team is aligned before the guest even walks in.

3. Keep an allergen sheet current and accessible. For every dish, the list of allergens present. Digital beats paper: it updates in seconds when a recipe or supplier changes, and anyone can consult it, anywhere.

4. Record the data for next time. If a guest declared an allergy, that data should be waiting for you on their next visit. It’s where safety meets loyalty, which we explore in remembering guest preferences.

When these four steps live in a single system — booking, briefing, dish sheet, guest history — human error drops sharply. Allergen handling stops depending on one server’s memory and becomes a procedure of the house.

In short

Allergens are the one chapter of dish management where a mistake can cost a guest’s health — and where the law is explicit. EU Regulation 1169/2011 requires declaring 14 allergen categories via a written support (menu, register, or sign); Italy’s Legislative Decree 231/2017 sets fines up to €24,000 for failure to declare, and similar regimes apply across markets. Beyond the fine, there’s direct liability if a reaction occurs.

But formal compliance isn’t enough: what counts is managing cross-contamination, being honest about your limits, and above all a solid process that carries the information from booking to plate without getting lost. Allergies and intolerances demand rigor; plain preferences fall under service flexibility. Knowing how to tell them apart — and handling them with a method — is what separates a reliable restaurant from one that, sooner or later, will have a serious problem.

Coperti is the reservation and guest-CRM system born from the experience of people who ran a restaurant for years. It lets you capture allergies and intolerances at booking time, surface them in the pre-shift briefing, and find them again in the guest’s history. The critical information reaches the team before the table is seated. Tell us about your restaurant — the trial is free and lasts 30 days.