How do you prevent translation errors from turning your multilingual menu into a legal liability? EU legislation demands accurate allergen information in each guest's language, yet restaurant owners constantly struggle with inconsistent translations and outdated information. Recipe changes compound the problem when allergen updates don't reach every menu version.
The 14 mandatory allergens per language
EU Regulation 1169/2011 requires allergen information in your guests' native language. You must correctly name identical allergens across every language version.
💡 Example allergens in 3 languages:
- Dutch: Gluten, Schaaldieren, Eieren, Vis
- English: Gluten, Crustaceans, Eggs, Fish
- German: Gluten, Krebstiere, Eier, Fisch
One translation error can cause legal problems.
Register allergens per ingredient
The most efficient approach involves recording allergens at ingredient level rather than per dish. This way, you'll enter allergen information once per ingredient.
- Wheat flour → Gluten (all languages)
- Butter → Milk/lactose (all languages)
- Eggs → Eggs (all languages)
- Parmesan cheese → Milk/lactose (all languages)
Recipe compilation automatically combines all ingredient allergens.
Common translation errors
⚠️ Watch out:
"Noten" in Dutch isn't equivalent to "nuts" in English. English distinguishes between "tree nuts" and "peanuts". Always use official EU designations.
Common translation mistakes:
- Wrong: "Dairy" → Correct: "Milk (including lactose)"
- Wrong: "Shellfish" → Correct: "Crustaceans"
- Wrong: "Nuts" → Correct: "Tree nuts" (mention peanuts separately)
Monitor consistency between menus
The biggest risk stems from inconsistency. Your Dutch menu gets updated, but the English version doesn't. Or your chef modifies recipes without updating allergen information.
💡 Example problem:
Your carbonara recipe changes from cream to crème fraîche. Both contain milk/lactose, so allergen-wise nothing changes.
But suppose you add pine nuts as garnish. Then "Nuts" must appear on all menu versions.
Without proper systems, you'll easily forget this in one language.
Digital system vs. manual translations
After managing kitchen operations for nearly a decade, I've seen countless restaurants struggle with separate Word documents per language. This approach creates errors and outdated information. Digital systems where you register allergens per ingredient prevent these issues.
- Modify ingredients → automatically updates across all languages
- Add new dishes → allergens calculate automatically
- Adjust recipes → allergen information updates immediately
Tools like KitchenNmbrs allow allergen registration per ingredient across multiple languages, maintaining menu consistency.
What to do if you're uncertain
Uncertain whether an ingredient contains specific allergens? Include it anyway. Better to err on the side of caution than risk allergic reactions.
⚠️ Watch out:
Suppliers can change recipes without notification. Regularly check product labels and update allergen information accordingly.
How do you set up multilingual allergen information? (step by step)
Create a list of all your ingredients
Collect all ingredients you use and note per ingredient which of the 14 EU allergens it contains. Start with your 20 most used ingredients.
Translate allergens into all required languages
Use the official EU designations for each allergen in every language. Have this checked by a native speaker or professional translator to prevent errors.
Automatically link allergens to dishes
Use a system where allergens from ingredients are automatically combined into allergen information per dish. This prevents you from having to manually update each dish.
Test your system with a recipe change
Modify one recipe by adding or removing an ingredient. Check whether the allergen information in all languages is automatically updated.
Train your staff in all languages
Make sure your team knows how to look up and explain allergen information to guests in different languages. Create a cheatsheet with the most important allergens.
✨ Pro tip
Create numbered allergen codes that work across all languages within 30 days of menu launch. For example: 1=Gluten, 2=Eggs, 3=Milk. You'll only translate the legend once, not every individual dish.
Calculate this yourself?
In the KitchenNmbrs app you can do this in just a few clicks. 7 days free, no credit card.
Was this article helpful?
Frequently asked questions
Do I need to mention allergens if they might be present due to cross-contamination?
Yes, if there's genuine cross-contamination risk, you must mention it. Use phrasing like "may contain traces of" in all languages. This protects both guests and your legal standing.
Can I use Google Translate for allergen information?
Never use automatic translations for allergen information. One error can be life-threatening. Always use official EU designations and have native speakers verify translations.
What if a guest asks about allergens that aren't on my list?
Be honest and admit uncertainty. Check ingredient labels or contact suppliers directly. Don't take risks - advise against the dish if you're unsure.
⚠️ EU Regulation 1169/2011 — Allergen Information — https://eur-lex.europa.eu/eli/reg/2011/1169/oj
The allergen information on this page is based on EU Regulation 1169/2011. Recipes and ingredients may vary by supplier. Always verify current allergen information with your supplier and communicate this correctly to your guests. KitchenNmbrs is not liable for allergic reactions.
In the UK, the FSA enforces allergen regulations under the Food Information Regulations 2014.
📚 Sources consulted
- EU Verordening 852/2004 — Levensmiddelenhygiëne (2004) — Official source
- EU Verordening 853/2004 — Hygiënevoorschriften voor levensmiddelen van dierlijke oorsprong (2004) — Official source
- EU Verordening 1169/2011 — Voedselinformatie aan consumenten (2011) — Official source
- NVWA — Hygiënecode voor de horeca (2024) — Official source
- NVWA — Allergenen in voedsel (2024) — Official source
- Codex Alimentarius — International Food Standards (2024) — Official source
- FSA — Safer food, better business (HACCP) (2024) — Official source
- BVL — Lebensmittelhygiene (HACCP) (2024) — Official source
- Warenwetbesluit Bereiding en behandeling van levensmiddelen (2024) — Official source
- WHO — Foodborne diseases estimates (2024) — Official source
Food Standards Agency (FSA) — https://www.food.gov.uk
The HACCP standards shown in this application are for informational purposes only. KitchenNmbrs does not guarantee that displayed values are current or complete. Always consult the FSA or your local authority for the latest regulations.
Written by
Jeffrey Smit
Founder & CEO of KitchenNmbrs
Jeffrey Smit built KitchenNmbrs from 8 years of hands-on experience as kitchen manager at 1NUL8 Group in Rotterdam. His mission: give every restaurant owner control over food cost.
Allergen registration that's truly compliant
EU legislation requires allergen documentation for every dish. KitchenNmbrs automatically generates allergen matrices based on your ingredients. Try it free for 14 days.
Start free trial →