Allergen labeling for restaurants: what's actually required, and how to make it painless

Getting allergen information wrong isn't just a legal exposure — it's one of the fastest ways to lose a guest's trust permanently, or worse. Getting it right doesn't have to mean a cluttered menu covered in tiny icons. It mostly means being consistent, and building the habit into how you already update the menu rather than treating it as a separate task.

This is a practical overview, not legal advice. Requirements are enforced locally — for Swedish restaurants, that's ultimately Livsmedelsverket and your municipality's food control. Check current requirements for your business before treating anything here as final.

The 14 allergens EU rules are built around

EU food information rules (Regulation 1169/2011) list 14 substances that food businesses — including restaurants — need to be able to disclose when used as ingredients: cereals containing gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, tree nuts (almonds, hazelnuts, walnuts, cashews, pecans, brazil nuts, pistachios, macadamia), celery, mustard, sesame, sulphur dioxide/sulphites, lupin, and molluscs.

For food that isn't prepacked — which covers most of what a restaurant serves — the rules give some flexibility in how that information reaches the guest. It can be written directly on the menu, or it can be communicated by staff on request, provided accurate information is genuinely available and whoever's asked actually knows the answer. Both are valid; what matters is that the information is accurate and someone can always get it.

Where restaurants actually get caught out

It's rarely the big, obvious allergens that cause problems — most kitchens are careful about the peanut and shellfish dishes. The failures tend to be quieter:

• A recipe changes but the label doesn't. A sauce switches suppliers, or a garnish gets swapped, and the allergen note written six months ago is now wrong.
• The "ask staff" system relies on staff who weren't there for the training. If your allergen information lives entirely in one person's head, it stops existing the day they're off sick.
• Inconsistent marking. One week nuts are flagged with an icon, the next week only mentioned in the description, the week after not mentioned at all — inconsistency reads as carelessness even when every individual dish is technically fine.

Making it consistent, not just correct

The fix is less about knowing the rules and more about process:

• Pick one system and keep it identical every week. Icons, letters, a footnote key — whichever you choose, use it the same way on every dish, every time, so guests learn to trust it without having to ask.
• Update the allergen note the moment the recipe changes, not at the next scheduled menu review. If ingredients and prices get updated together in the same place, this stops being a separate task you forget.
• Keep a written reference even if the menu itself says "ask staff." Staff turnover is constant in this industry; a person's memory isn't documentation.
• Don't hedge with catch-all disclaimers instead of real information. "May contain traces of anything" on every dish protects nobody and tells a guest with a real allergy nothing useful.

Where this fits in Menju

If you're building dishes with tags in Menju, the same tagging system works well for allergen labels — it keeps the marking structurally attached to the dish rather than living in a separate document, so it travels with the dish when you copy last week's menu into this week's. The Used tags panel in your analytics is also a quick way to spot inconsistency — if a dish that should carry an allergen tag doesn't show up there, that's worth a second look.

Next steps

Allergen labeling works best as part of a menu that's already easy to keep current — see why a digital menu pays off for the broader case, or 5 quick tips for a clearer menu for more on keeping the whole menu easy to trust at a glance.