Allergen Labelling for Restaurants: EU Rules

EU law requires every restaurant to make allergen information for 14 listed allergens available for every dish it serves. That means a documented allergen assessment per dish, information guests can actually find — written or clearly signposted — and staff trained to answer accurately. This guide walks through the rules, the 14 allergens in plain language, the matrix method inspectors expect to see, and the national differences across the Nordics.

For a guest with a serious food allergy, your menu is not marketing — it's a safety document. They read it the way a pilot reads a checklist: carefully, completely, and with real consequences if something is wrong. EU law treats it that way too. Since December 2014, Regulation (EU) 1169/2011 — the Food Information to Consumers Regulation — has required allergen information for 14 listed allergens on non-prepacked food, which is everything a restaurant serves. The obligation is now more than a decade old, enforcement has matured, and guest expectations have moved further still: allergy-aware diners research restaurants online before booking, and they reward the ones that make allergen information easy to find. This guide explains what the rules actually require, how to comply without drowning in paperwork, and where the Nordics differ from the EU baseline.

What the EU rules actually say

The legal core is short enough to state plainly. Regulation (EU) No 1169/2011, Article 44, says that for food sold non-prepacked — food that isn't in a sealed package with a label, which covers every plate that leaves your kitchen — the indication of allergens listed in Annex II is mandatory. The allergens are the only particular that is mandatory for loose food: you don't have to declare calories, origin, or nutrition on a restaurant dish, but you must make the allergen information available.

Uniform obligation, national delivery

Here's the subtlety that trips people up. The obligation is identical across the EU — every restaurant, every member state, same 14 allergens. But the same article lets each member state set its own rules on how the information is provided: its form, its expression, its presentation. So the entitlement is uniform — a guest can always find out — while the delivery is national. In some countries the information must effectively be written; in others a clearly signposted verbal answer from trained staff is acceptable, backed by written documentation. The section on Nordic differences below covers Finland, Sweden and Norway specifically.

What "available" means in practice

Three principles run through every national implementation:

• Accurate. The information must reflect what's actually in the dish, from current supplier specifications — not from the chef's memory of last year's recipe.
• Accessible. The guest must be able to find it without an interrogation. A matrix locked in the office that staff "can go and check" fails this test in spirit, even where the letter of the law is vaguer.
• Verifiable. Whatever you tell guests must be traceable to written records — the allergen matrix, recipe sheets, supplier specs. If a guest is harmed and you can't show your workings, the verbal assurance counts for nothing.

The 14 allergens, explained dish by dish

Annex II of the regulation lists 14 allergens (and products thereof). Memorise this list — it's the entire scope of the obligation, and several entries hide where you'd least expect them.

1. Cereals containing gluten

Wheat (including spelt and khorasan), rye, barley, oats, and their hybridised strains. Note: it is not "gluten" as an abstract substance — it's the cereals. Oats are explicitly in the list, which surprises people who treat oats as the safe substitute. "Gluten-free" oats are simply oats grown and handled to avoid contamination; they don't leave the regulatory category.

2. Crustaceans

Prawns, shrimp, crab, lobster, crayfish, langoustine. Watch for shrimp paste and dried shrimp in Asian-influenced dishes — potent, and easy to forget in a sauce.

3. Eggs

Beyond the obvious: mayonnaise, fresh pasta, many desserts, some breads and batters, hollandaise and béarnaise. Egg washes on pastry count.

4. Fish

Fish sauce, Worcestershire sauce, anchovy in dressings (Caesar salad's quiet passenger), some Asian stocks. Guests who say "fish allergy" often mean finned fish specifically, but your declaration covers all of it.

5. Peanuts

Peanut oil (refined peanut oil is generally considered safe by allergists, but declare it anyway — your job is information, not medical judgement), satay sauces, some desserts and snacks.

6. Soybeans

Soy sauce, tofu, miso, edamame, and soy lecithin (E322) in processed ingredients. Soy is one of the most widespread "invisible" allergens in bought-in sauces and marinades.

7. Milk

Including lactose. Butter, cream, cheese, yoghurt — and the less obvious: milk powder in bread, whey in processed foods, sodium caseinate as an additive. "Dairy-free" claims on bought-in products need verifying against the spec, not the front of the pack.

8. Nuts

Tree nuts: almonds, hazelnuts, walnuts, cashews, pecans, Brazil nuts, pistachios, macadamias. Pesto (pine nuts — and many commercial pestos use cashew), frangipane, nut oils, some breads and salads.

9. Celery

Fresh celery, celeriac, celery salt, and celery in stock cubes, spice mixes and soups. One of the most commonly missed entries — it hides in base preparations rather than finished dishes.

10. Mustard

Mustard seeds, prepared mustard, and mustard powder in dressings, marinades and charcuterie accompaniments.

11. Sesame seeds

Seeds, sesame oil, tahini, hummus, and sesame on bread — including the dusting on a bought-in bun that nobody on the line thinks about.

12. Sulphur dioxide and sulphites

Above 10 mg/kg or 10 mg/litre. Wine and dried fruit are the classic carriers, plus some processed potatoes and preserved ingredients. Worth tracking because it appears in drinks service as well as food.

13. Lupin

A legume related to peanuts, used in some flours, breads, pastries and pasta — particularly in products from continental European suppliers. Unfamiliar to many kitchen teams, which is exactly why it needs to be on the radar.

14. Molluscs

Mussels, oysters, clams, scallops, squid, octopus, snails. Often declared casually as "shellfish" alongside crustaceans — but the regulation lists them separately, and so should you.

How to display allergen information

The law fixes what you must communicate; you have real choices about how. Each method has a place.

What the evidence says guests want

Surveys of allergy-affected diners consistently rank one thing above all other trust signals: allergens clearly marked next to every menu item — ahead of a website policy page, ahead of staff reassurance, ahead of third-party certification. And it moves behaviour: large majorities say they'd eat out more often at restaurants with clear, easy-to-find allergen information. The written per-dish approach isn't just the safest compliance posture; it's the one guests actually reward.

Language parity

Whatever method you choose, the allergen information must be understandable in every language you serve the menu in. An English menu with the allergen key only in Finnish, or a Swedish menu where the symbols are explained only in Norwegian, is a gap. On digital menus this is a translation task; on paper it means the key appears in each language version.

Build your allergen matrix

The allergen matrix is the single document your whole compliance rests on: a grid with one row per dish and one column per allergen, marked where the dish contains the allergen. Inspectors ask for it. Staff answer from it. Your menu displays derive from it. Build it once, properly, and everything downstream gets easier.

How to build it

1. List every dish. Every menu item, every variant, every side, every dessert — plus the children's menu, the lunch menu, and the drinks that carry allergens (yes, the mulled wine has sulphites).
2. Work from supplier specifications, not memory. For each dish, break it into ingredients and check each ingredient's spec sheet for the 14 allergens. Bought-in sauces, stocks, breads and desserts are where the surprises live — a stock cube can carry celery, a bought-in bun can carry sesame, a dessert can carry lupin flour.
3. Mark deliberately. A clear yes/no per cell. No blanks, no question marks — an uncertain cell is a task to resolve, not a shrug to publish.
4. Date and sign it. Every version gets a date and the name of who prepared it. When the menu changes, you create a new dated version. This is your evidence trail.
5. Keep it where staff can reach it. Laminated in the kitchen, a copy at the pass, and the same data in whatever your servers consult. A matrix in the manager's office helps nobody during service.

Keeping it alive

A matrix is a living document or it's a liability. The triggers for a review: any recipe change, any supplier change, any new bought-in product, any new dish — and a scheduled full review at least twice a year. The most dangerous moment is the quiet substitution: the supplier swaps a brand, the new version contains mustard where the old one didn't, and nobody updates the sheet. Make the rule simple — no new product enters the kitchen without its spec sheet going to whoever maintains the matrix.

Cross-contact: what the label doesn't cover

The 14-allergen declaration covers what's in the dish by recipe. Cross-contact — allergens getting into food unintentionally during storage, preparation or service — is the shadow side, and it's where most real-world incidents happen.

Where cross-contact happens

• Shared fryers. The classic: chips fried in oil that also cooked breaded fish. If you can't dedicate equipment, you must be honest about it.
• Shared surfaces and boards. The board that had the bread, the counter where the pastry was rolled.
• Shared utensils and cloths. Tongs, spoons, the wipe-down cloth moving allergens around the pass.
• Storage. Open flour above ready-to-eat food, nut containers without lids, decanted ingredients without labels.
• Garnishes and finishing. The nut sprinkle added at the pass, the bread served alongside "on the house".

What to do about it

Separate where you can: dedicated boards, utensils and storage for allergen-free preparation; fry in dedicated oil or be explicit that you don't. Clean down between tasks when separation isn't possible. Label decanted ingredients with the product name and its allergens. And train the specific phrase every server needs: "I can tell you what's in the dish by recipe, and I can tell you about our kitchen practices — would you like me to check with the kitchen on cross-contact for your allergy?" That sentence, delivered calmly, is worth more than any poster.

"May contain" — use it right

Precautionary allergen labelling ("may contain nuts", "made in a kitchen that handles gluten") has a legitimate, narrow role: warning about a genuine, assessed cross-contact risk you can't eliminate. What it is not: a substitute for working out what's in the dish, a blanket disclaimer to avoid the matrix, or a way to make everything "may contain everything" so nothing needs declaring. Overused precautionary labels teach allergic guests to ignore them — which helps nobody. Declare what's in the dish; use "may contain" sparingly, honestly, and only where the risk assessment supports it.

Staff training and verbal answers

Even with perfect written information, guests will ask staff. The answer has to be right, because a wrong answer here is the one that ends in an ambulance.

What every server must know

• The 14 allergens by name — not "the usual ones", all fourteen.
• Where the matrix lives and how to read it in under thirty seconds.
• The house line for uncertainty: never guess, always check. "Let me verify that with the kitchen" is a correct answer; a confident guess is a dangerous one.
• That recipes change — the answer that was right last month needs re-checking after a supplier swap.

What the kitchen must know

The matrix is built from their recipes, so they own its accuracy. Any substitution — a different brand, a tweaked recipe, a special — gets communicated to whoever updates the matrix before it goes out, not after. Make this a non-negotiable part of the ordering and prep routine, not a favour.

Training that sticks

Annual formal training as a minimum, plus a five-minute refresher whenever the menu changes significantly. New starters get allergen training in their first week — before their first solo service, not after. Keep a simple training log: who, when, what was covered. It takes minutes and it's the first thing that demonstrates due diligence if anything goes wrong. And test it the way an inspector would: walk up to a server mid-shift and ask about the allergens in three dishes. The answer tells you everything about your real compliance level.

Why digital menus make this easier

Allergen compliance on paper is a reprint cycle; on a digital menu it's an edit. That single difference changes the economics of staying correct.

Updates without the print run

Supplier swaps a product, the allergen profile shifts, you update the matrix and the menu page in the same sitting — minutes, not weeks. The paper-menu restaurant faces the same change and a choice: reprint now (expensive) or "update it next time" (non-compliant in between). Digital removes the excuse.

Filters guests can use themselves

A digital menu can let a guest filter by "nut-free" or "gluten-free" and see only safe dishes — no flagging down a server, no anxious negotiation. For the guest, it's dignity; for you, it's fewer interruptions and a documented, consistent answer every time. Our digital menu guide covers the full setup.

One source of truth

The failure mode of paper allergen info is version drift: the menu says one thing, the matrix another, the website a third. A digital menu fed from the same data as the matrix collapses the three into one. Change it once, and the guest-facing information matches the kitchen's documentation by construction.

National differences: Finland, Sweden, Norway

The EU obligation is the same everywhere, but the three Nordic countries implement the "how" slightly differently. If you operate in one of them, these are the local specifics to know.

Finland

Finland applies the EU regulation directly, with national food legislation and supervision carried out by municipal food control authorities — the local inspectors who visit your premises. National guidance comes from the Finnish Food Authority (Ruokavirasto). In practice, Finnish inspectors expect to see the written documentation: the allergen matrix or equivalent recipe-based records, available and current. Finland's two national languages matter here too — allergen information should be understandable to guests in the language they're reading the menu in, so a Finnish menu needs Finnish allergen information and an English menu needs it in English.

Sweden

Sweden's national rules, administered by the Swedish Food Agency (Livsmedelsverket), allow allergen information to be provided verbally — but only with a clear written sign telling guests they can ask, and only with written documentation behind the answer. In practice, Swedish guidance has been moving the same direction as everywhere else: written information is the safer and increasingly expected standard, and many Swedish restaurants now mark allergens directly on the menu regardless of the verbal option.

Norway

Norway applies the same EU rules through the EEA Agreement, supervised by the Norwegian Food Safety Authority (Mattilsynet). The 14-allergen list and the documentation expectations mirror the EU baseline. As in Finland and Sweden, tourist-facing restaurants should treat multilingual allergen information — at minimum Norwegian and English — as the practical standard.

What happens if you get it wrong

Enforcement in the Nordics is carried out by food inspectors during routine visits and in response to complaints or incidents. Understanding the escalation helps you calibrate the effort.

The inspection

An inspector checking allergen compliance will typically ask three things: show me your allergen documentation (the matrix or equivalent), show me how guests receive the information (menu, signs, digital), and ask a staff member about the allergens in a dish. Missing or outdated documentation, information guests can't find, or a server who guesses — any of these draws a remark and a deadline to fix it.

Escalation

Unresolved remarks become formal orders: fix this by this date. Persistent non-compliance can bring administrative fines under national food law, and in serious cases restrictions on operations. These are the regulatory consequences — but they're not the ones that keep owners up at night.

The consequences that actually hurt

A guest having an allergic reaction in your dining room is the real risk: the medical emergency, the investigation, the question of whether your documentation was accurate and your staff answered correctly. Beyond that, the civil liability — and the reputational damage in an age where the incident will be on social media before the ambulance leaves. Against that, the cost of compliance — a spreadsheet, some training time, accurate menus — is trivially small. This is one of those rare areas where the legally required thing and the commercially smart thing are the same thing.

Your 30-day compliance action plan

If your allergen setup is currently "the chef knows", here's how to get to compliant in a month without closing the kitchen.

Week 1: Gather the facts

• List every dish, side, dessert and drink on every menu you serve.
• Pull the specification sheets for every bought-in product — sauces, stocks, breads, desserts, marinades. Call suppliers for any missing specs.
• Photograph or copy the current recipes as actually cooked, not as written three years ago.

Week 2: Build the matrix

• One row per dish, one column per allergen. Work from specs, mark every cell, date and sign the document.
• Flag every uncertain cell and resolve it — call the supplier, check the recipe, taste nothing, guess nothing.
• Decide your guest-facing method: per-dish notes, symbols with a key, a separate chart, or digital filters — or a combination.

Week 3: Publish and train

• Update the menus — printed, website, QR codes — from the matrix, in every language you serve.
• Brief all servers: the 14 allergens, where the matrix lives, the never-guess rule. Log the training.
• Walk the kitchen: storage labelling, separation practices, the substitution rule (no new product without a spec sheet to the matrix keeper).

Week 4: Verify

• Mystery-shop your own restaurant: ask three servers about allergens in three dishes each. Fix what fails.
• Check the website menu matches the printed menu matches the matrix — no version drift.
• Put the recurring reviews on the calendar: matrix review with every menu change, full audit twice a year, refresher training with every significant menu update.

Frequently asked questions