Allergens on a Restaurant Menu: What the Law Requires

A guest with a nut allergy asks the server if today's special sauce is safe. The server doesn't know, because the recipe changed a week ago and the allergen binder sitting in the kitchen was never updated. That scene plays out in restaurants all the time, and it ends in either a complaint or something worse. Allergen labeling on a restaurant menu isn't a once-a-year compliance chore: it's a concrete legal requirement and a daily practice that can be handled far better than a paper binder.

What the law says: 14 allergens and a duty to inform

EU Regulation 1169/2011 (this applies in Poland and across the EU; check local implementation details for your country) requires food businesses to inform guests about the presence of 14 substances or products known to cause allergies or intolerances. That includes gluten, eggs, fish, crustaceans, nuts, milk, soy, celery, mustard, sesame, lupin, mollusks, sulfur dioxide and sulfites, and peanuts.

What matters is how the information is delivered, not just whether it exists somewhere. It has to be available to the guest at the moment of ordering, in a form they can actually read and understand. The rules don't mandate one specific format (a printed card, a table sign, or a verbal explanation from trained staff all count), but they do require the guest to have certainty before placing an order, not after the fact.

One important note: this is a practical guide, not legal advice. Regulations and their interpretation get updated, and implementation details vary between EU countries. Before changing how you communicate allergen information, it's worth checking with a lawyer or your local health authority to confirm the current requirements.

How restaurants handle it today: binders and asterisks

In practice, most venues rely on one of two approaches.

The allergen binder. A separate document, usually kept in the kitchen or behind the bar, listing dishes and their allergens in a table. A guest who asks gets shown the binder, or the server checks it and relays the answer verbally.

Asterisks and footnotes on the menu. A small asterisk or number next to a dish name, with a legend at the bottom of the page explaining what it means. Sometimes it's just one blanket note: "dishes may contain allergens, ask your server."

Both approaches work fine, right up until something changes. And in a restaurant kitchen, almost everything changes.

Why this breaks down in practice

The binder and the asterisks share the same weakness: they live a life of their own, disconnected from what's actually happening in the kitchen.

• Updating them depends on memory, not a system. A cook switches oil suppliers or adds sesame seeds to a sauce because it tastes better, and nobody tells whoever is responsible for the binder. The document is out of date from day one of the change.
• The information is hard to reach at the moment of decision. A guest looks at the menu, wants to order, but to find out about allergens has to stop, ask, wait for the server, and sometimes wait again while the server checks with the kitchen. During a rush, that step just doesn't happen.
• Staff turnover. A new server doesn't have every dish memorized, and the binder is often illegible or gets misplaced between shifts.
• Language. A restaurant downtown or near an airport serves guests from all over the world. A binder written in Polish doesn't help a tourist who doesn't speak the language, and translating on the fly is guesswork.
• No record. If an incident happens, it's hard to prove the information was actually available to the guest at the time of ordering, rather than just existing somewhere in a binder.

This isn't about bad intentions from restaurant owners. It's a tooling problem: the tool can't keep pace with how fast a kitchen changes.

How a digital menu solves this

A digital menu (a QR code on the table, a page accessible from a phone) changes the mechanics, not just the format. Several things work differently than on paper.

Filters and icons on every dish. A guest can tap "gluten-free" or "nut-free" right away and see only the dishes that qualify. No reading a legend or counting asterisks: the system does it for them.

One place to update, visible instantly. When the kitchen changes a recipe, someone edits the dish in the admin panel, saves it, and the change shows up at every table within the same minute. No reprinting menus, no swapping out a binder.

Language versions with no extra work. Once allergen data is entered, it can be shown in Polish, English, or German without translating every change by hand.

A change history. A menu admin panel typically logs who changed a dish's data and when, which is useful if you ever need to prove the information was accurate on a given day.

A digital menu also connects well with other elements of the menu we've written about before, like how photos and video of dishes affect average check size: the guest sees the dish, its ingredients, and its allergens in one place, instead of piecing that picture together from several sources.

How to collect the data from your kitchen: a practical process

The filter system itself won't help if the underlying data is incomplete or outdated. In our experience, a simple process works well.

1. One person owns it. The head chef or shift manager, not "someone on the team." Without a clear owner, the data drifts out of date within a few weeks.
2. A product sheet for every ingredient. When a new supplier comes on board, check the label and record the allergens based on the actual ingredient list, not a guess.
3. Allergens tracked at the dish level, not just per ingredient. A sauce might contain mustard that isn't obvious from any single visible ingredient, so the whole recipe counts, marinades and add-ons included.
4. Cross-contamination. If fries are cooked in the same oil as breaded shrimp, that's a separate note worth including, even if the dish itself contains no crustaceans.
5. A regular review, not just when the menu changes. Set a fixed cadence, say once a month, when someone goes through the full dish list and confirms the allergen data still holds up.

Procedure for switching suppliers

Switching suppliers is the moment errors happen most often, because the product's composition changes while the menu entry stays the same.

• Before introducing a new product, check the label against all 14 allergens, not just the obvious one.
• Compare it to the old product: even the same type of sauce from a different manufacturer can use different additives (for example, gluten as a thickener instead of corn starch).
• Update the dish in the digital menu admin panel right away, ideally before the first service with the new product, not after.
• Let the kitchen and front-of-house team know about the change, so a server can answer a guest's question even before checking the menu.

Owner responsibility

Formal responsibility for allergen information at a venue falls on the business operating it, in practice the owner or manager, regardless of whether the error came from a cook's mistake or an outdated document. That's one more reason the allergen information system shouldn't rely on any one person's memory, but on a process that can be reproduced and checked.

It's also worth remembering that good practice goes beyond the bare legal minimum. Even where local rules allow verbal-only disclosure, clearly marking allergens on the menu builds trust and cuts down on mistakes before a conversation with a server even starts.

Frequently asked questions

Do I have to mark allergens directly next to the dish name?

The rules don't require one specific visual format, but they do require the information to be genuinely accessible to the guest before ordering. Marking it next to the dish name (an icon, an asterisk, a filter in a digital menu) is practical because it shortens the path to the information, but check with a lawyer on which format satisfies requirements in your location.

What if a dish has trace amounts of an allergen from a shared production line?

That's a separate category from a deliberate ingredient in a recipe, but many restaurants disclose it anyway, for example with a "may contain trace amounts" note. Base the decision on actual kitchen risk and check local health guidelines.

Is a paper menu with asterisks against the law?

Not by itself. The usual problem is a lack of updates, not the format. If a paper menu is properly maintained and updated with every recipe change, it can meet the requirements. In practice, a digital menu just makes it much easier to keep that up to date.

Who at the restaurant should have access to edit allergen data?

Ideally a limited group, such as the head chef and shift manager, to avoid unintended changes nobody else knows about. In a digital menu admin panel, it's worth setting this up as a separate role with a change history.

If you want to move allergen labeling from a binder into a system that updates in one place and shows guests filters right on the dish, see how it works in practice at DOPEST.menu. We help restaurants roll out digital menus complete with allergen data and language versions, so that information is right where the guest is actually looking for it.