Allergen and Dietary Labeling on Your Menu: The EU 14, Done Right

A guest points at the risotto and asks one question: "Does this have gluten?" In an EU restaurant, you are legally required to have an answer — and the same answer, every time, from every server, in every language you serve. Allergen information is not a nicety. Since Regulation (EU) 1169/2011, declaring the 14 major allergens in any food you sell is the law, and "I think so" is not a compliant reply.

Most kitchens handle this with a laminated binder behind the bar, a note in the reservation book, or the memory of whichever server picks up the table. All three fail the same way: the moment a recipe changes, the sauce supplier switches, or a new hire takes the floor, the answer drifts out of date and nobody notices until the wrong plate reaches an allergic guest. This is the one part of your menu where a wrong answer is not a bad review — it is a health risk and a liability. A digital menu fixes it by making the allergen data part of the dish, not part of someone's memory.

Why Paper Menus Fail at Allergen Labeling

A printed allergen sheet is accurate for exactly one day: the day it was printed. The kitchen swaps the frying oil, adds a splash of soy to the marinade, or runs out of the usual bread and subs in one with sesame — and the paper is now wrong, but still sitting on the shelf looking authoritative. Reprinting is slow and expensive, so in practice nobody does it mid-season. The gap between what the kitchen actually cooks and what the sheet says is where incidents happen.

Translation makes it worse. If you serve tourists, your allergen note has to be right in English, Bulgarian, Greek, or whatever your guests read — and a paper menu forces you to maintain that same list two or three times, by hand, forever. Update the Bulgarian and forget the English, and an English-reading guest gets stale, dangerous information. This translation drift is silent: nothing breaks, no error appears, the wrong plate just goes out. A single source of truth, tagged once and rendered in every language, is the only way to keep them from diverging.

The 14 EU Allergens You Must Declare

Regulation (EU) 1169/2011 lists 14 allergen groups that must be declared for any food you serve, including loose (non-prepacked) food in a restaurant. Learn them, because every dish on your menu needs to be checked against this list:

• •Cereals containing gluten — wheat, rye, barley, oats, spelt, kamut and their hybrids (bread, pasta, most sauces thickened with flour).
• •Crustaceans — prawns, shrimp, crab, lobster, langoustine.
• •Eggs — including mayonnaise, many pastas, glazes and batters.
• •Fish — including fish stock, anchovy in dressings, and Worcestershire sauce.
• •Peanuts — and oils, sauces and satay made from them.
• •Soybeans — soy sauce, tofu, edamame, many marinades and vegan substitutes.
• •Milk — butter, cheese, cream, yoghurt, and hidden dairy in bread and sauces.
• •Nuts — almond, hazelnut, walnut, cashew, pecan, Brazil, pistachio, macadamia.
• •Celery — including celeriac, celery salt, and many stocks and soups.
• •Mustard — mustard seed, powder, and prepared mustard in dressings.
• •Sesame seeds — tahini, hummus, seeded buns, halva.
• •Sulphur dioxide and sulphites (above 10 mg/kg or 10 mg/litre) — common in wine, dried fruit and some processed foods.
• •Lupin — lupin flour used in some breads and pastries.
• •Molluscs — mussels, clams, squid, octopus, snails, oyster sauce.

Rule of thumb: allergen info is a property of the recipe, not of the menu. Tag the dish once, at the source, and let every surface — QR menu, website, printout, every language — read from that single tag. If a fact lives in more than one place, it will eventually disagree with itself.

Tag Once, Show Everywhere

The whole point of a digital menu is that a fact entered once appears everywhere it is needed, correctly, without a second data entry. Allergens are the textbook case for this.

Tag each dish at the recipe level

When you set up a product, attach its allergens and dietary labels — vegan, vegetarian, gluten-free, and the relevant allergens from the 14 — as structured tags on the item itself, not as a sentence buried in the description. Because they are structured, the same tags render as clear icons or chips on your QR menu at the table, on your public ordering website, and anywhere else the dish appears. You maintain one record; the guest sees consistent information no matter where they look.

One tag, every language, no drift

This is where a digital menu decisively beats paper. A structured "contains gluten" tag is language-independent under the hood — the platform renders it as "съдържа глутен" for a Bulgarian guest and "περιέχει γλουτένη" for a Greek one, from the same single tag. You never re-enter the allergen list per language, so the English and the Greek versions can never fall out of sync. For how content stays coherent across languages, see the Multi-language feature page — the same mechanism that keeps dish names in sync keeps allergen labels in sync, and our multi-language restaurant menu guide covers the wider setup.

Let the labels answer before the server does

When allergens and dietary tags sit right on the dish, guests filter themselves. A vegan sees the vegan chips and orders confidently; a coeliac scans for the gluten-free mark before flagging a server. That is fewer "can you check with the kitchen?" interruptions during a rush, fewer relayed questions that get answered wrong, and a faster table. The label does the reassurance work so your staff can focus on service — and the guest with a genuine allergy gets a written, consistent answer instead of a hurried verbal one.

Keeping Allergen Info Accurate When Recipes Change

Compliance is not a one-time setup — it is a habit tied to your kitchen. The moment a recipe changes, the allergen tag must change with it. Build one rule into your prep routine: no ingredient swap goes live until the dish's tags are updated. Ran out of your usual buns and grabbed sesame-topped ones? The sesame tag goes on before the first burger leaves the pass. Switched to a stock that contains celery? Update it that morning. With a digital menu you make that change in one place and every surface — table QR, website, every language — reflects it within seconds, so there is never a stale paper sheet contradicting the kitchen.

The most reliable setup keeps allergen labels living inside the same menu your guests actually order from, so accuracy and ordering never drift apart. To manage those dish-level tags, see the Menu Management feature page; to put the same labelled menu on the table, see the QR Code Menus feature page, and our guide on how to create a QR code menu for your restaurant walks through going live. Handle allergen labeling as the compliance task it is, and you protect your guests, your staff, and your restaurant in one move.