Allergens in food service: inspections, the menu, and staying compliant

The question that keeps many operators up at night isn't "which allergens" — it's "what if there's an inspection?". Fear of a check breeds stories about enormous fines, many of them unsourced, and the result is usually too much anxiety and too little method. Let's talk about what an inspection actually looks at, and how to stay calm. First, the note that matters: this article is not legal advice. The procedures, the size of any penalties and the enforcement criteria change over time and depend on the specific case; penalties vary — for figures and for your situation, ask your local authority or your accountant. What follows is the principle and the practice, not an opinion.

Regulation 1169/2011 and the inspector: who checks what

The foundation is European: Regulation (EU) 1169/2011 on food information to consumers. At its core it says: before ordering, the guest must be able to find out whether a dish contains any of the 14 declarable allergens. Who enforces this in food service varies by country — in Portugal it's the ASAE, in France the DGCCRF, elsewhere it's a national body or local health inspectors. The authority changes; the principle being checked doesn't. National law implements the regulation, but the core is European, and it's that core an inspection targets.

An important note on consequences: yes, non-compliance can lead to penalties, but the amounts vary with the type of breach, the size of the business and the circumstances — we won't invent figures here. If you need the range that applies to your case, that's exactly the question for your authority or your accountant.

The 14 allergens the menu must declare

The object of any check is the fourteen declarable allergens, identical across Europe: cereals containing gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, tree nuts, celery, mustard, sesame, sulphur dioxide and sulphites, lupin and molluscs. The full list, with the sub-categories and where each allergen tends to hide, is in our allergen table guide. Here the interest is different: how an inspection checks that the declaration exists, is accurate, and matches the dishes.

What an inspection typically looks at

Without going into details that shift from one check to the next, there are three axes any food-information inspection tends to examine:

• The information exists and is accessible to the guest. On the menu, by key or code, or with a clear sign that it's available on request with a written basis behind it. What doesn't pass is nothing at all.
• The information is consistent with what the kitchen serves. If the menu says a dish doesn't contain an allergen and the actual recipe does, that's a problem — and it's exactly the kind of inconsistency a careful check catches, cross-referencing menu, recipe sheets and supplier labels.
• There's a documented basis. Recipe sheets, semi-finished-product labels, a record staff rely on to answer. Documentation isn't bureaucracy: it's the proof that the information is grounded, not guessed.

The common denominator is simple: whoever keeps the information organised and true has no reason to fear an inspection. The nerves come from improvising, not from the check.

Keeping the information right as the kitchen changes

Here's the point that separates those who sail through an inspection from those caught out: allergen information isn't a document you make once. The supplier changes the sauce recipe and mustard appears; the bread switches to another baker; the daily special rotates every week. Each of these changes can shift a dish's allergens — and if the declaration doesn't follow, you create exactly the inconsistency a check finds.

Two routines solve almost everything: for every new product coming in, read the label and update the record; and review the declaration whenever you change a recipe. It's the same rigour a well-run gluten-free offer demands, where a single swapped ingredient changes everything. To build the basis from scratch, the free allergen table gives you the grid, dish by dish.

From paper to digital: the menu that doesn't lie

The Achilles heel of all this is the printed medium. A paper menu is updated when it's reprinted — that is, almost never — so the version the guest reads is rarely the one the kitchen serves today. That's precisely where an inspection finds the inconsistency.

With a digital menu, the information follows the kitchen to the minute. With Menudetto, the AI detects the allergens in a dish and its ingredients and proposes the declaration — but before anything is published, a human reviews and confirms. The AI does the busywork; responsibility for the plate stays in the kitchen, where it belongs. Swapped a semi-finished product? You update the record in seconds from your phone, and the menu behind the QR code is right at once. It isn't a magic compliance guarantee — that always depends on the kitchen — but it's the tool that makes simple what was impossible on paper: keeping the information true every day.

In short

Allergen enforcement in food service rests on Regulation (EU) 1169/2011, checked by whichever authority your country appoints (Portugal's ASAE, France's DGCCRF, elsewhere a national or local body): the 14 allergens must be declared accessibly, consistently with what the kitchen serves, and backed by documentation; an inspection mainly checks that the information exists, is true and follows the dishes; and the secret to a calm mind is keeping the declaration current as the kitchen changes. On penalties and on your specific case: penalties vary — ask your authority or your accountant. This article is a practical guide, not legal advice.