Restaurant Allergen Translation Guide: Communicating Food Allergens in Multiple Languages

For a guest with a food allergy, a menu that lists allergens only in the local language isn't just unhelpful — it's a safety risk. A tourist who speaks no Italian may be able to guess that "pasta al pomodoro" is tomato pasta. But "contiene glutine, latte, uova" is harder to parse when you're new to the language and genuinely need that information.

Allergen communication is where multilingual menus stop being a hospitality nicety and become a genuine duty of care. This guide covers what you're legally required to communicate, what good multilingual allergen labelling looks like in practice, and how to maintain it consistently as your menu changes.

Translating a dish description is about hospitality. Translating allergen information is about safety. The stakes are different.

A slightly imprecise translation of "house-made pasta" — say, one that calls it "homemade" instead — causes no harm. An imprecise translation of "contains peanuts" — one that is vague, omitted, or mistranslated — can cause anaphylaxis.

This distinction has a practical implication: allergen translation requires a higher standard of review than the rest of your menu. It is the one area where you should not rely entirely on automated translation without a verification step.

European Union

The EU Food Information Regulation (EU 1169/2011) requires all restaurants to provide information about 14 major allergens for every dish that contains them. The 14 regulated allergens are:

1. Gluten (wheat, rye, barley, oats, spelt, and related grains)
2. Crustaceans (prawns, crabs, lobster, crayfish)
3. Eggs
4. Fish
5. Peanuts
6. Soybeans
7. Milk (including lactose)
8. Nuts (almonds, hazelnuts, walnuts, cashews, pecans, Brazil nuts, pistachios, macadamia/Queensland nuts)
9. Celery
10. Mustard
11. Sesame seeds
12. Sulphur dioxide and sulphites (above 10mg/kg or 10mg/litre)
13. Lupin
14. Molluscs (clams, mussels, oysters, scallops, snails, squid)

The regulation requires that allergen information be available, but does not mandate a specific format. This means restaurants can list allergens in writing on the menu, provide a separate allergen sheet on request, or display them digitally — as long as the information is accurate, accessible, and the guest can easily obtain it.

The regulation does not explicitly require allergen information in multiple languages. However, if a guest requests this information and cannot understand the response due to a language barrier, the practical and legal responsibility to serve that guest safely still applies.

United Kingdom

Post-Brexit, the UK maintains broadly equivalent allergen labelling requirements under UK Food Information Regulations. The same 14 allergens apply. In 2021, "Natasha's Law" extended allergen labelling requirements to pre-packaged foods, which may affect some catering contexts.

United States

The US Food Allergen Labeling and Consumer Protection Act (FALCPA) covers packaged food. Restaurant requirements vary by state, but most states require that guests can obtain allergen information on request. The FDA recognises 9 major allergens: milk, eggs, fish, shellfish, tree nuts, peanuts, wheat, soybeans, and sesame (sesame was added in 2023 under FASTER Act).

There is no federal requirement for allergen information in multiple languages, but the legal principle of duty of care still applies to serving guests with known allergies.

Australia and New Zealand

Australia and New Zealand align with FSANZ Standard 1.2.3, requiring allergen declarations for 11 major allergens. Translation requirements follow the same practical principle: the restaurant has a duty to provide accurate information, regardless of language.

The practical takeaway: regardless of jurisdiction, if a guest tells you they have a food allergy and your staff cannot communicate allergen information clearly, the restaurant bears responsibility for any resulting harm. A multilingual menu that clearly labels allergens is one of the most effective ways to prevent this scenario.

Use standardised terminology, not colloquial translations

Allergen terminology varies between languages, and sometimes between regions of the same language. A few common pitfalls:

• "Gluten-free" in French can be rendered as "sans gluten" or "exempt de gluten" — the first is standard, the second is understood but uncommon. Use "sans gluten".
• "Tree nuts" in German: "Schalenfrüchte" is the regulatory term; "Nüsse" (nuts) is more casual and less precise.
• "Shellfish" covers both crustaceans (Krebstiere in German, crustacés in French) and molluscs (Weichtiere, mollusques) — two distinct allergen categories in EU regulation. Avoid the catch-all "seafood" in translations.

MenuTap's translations are tuned for culinary and hospitality contexts, but allergens are worth a dedicated review pass in any language spoken by a significant portion of your guests.

Be specific about which allergens are present

"May contain traces of nuts" is weaker than "contains cashews and walnuts." If you know the specific allergen (and you should, if you know your recipes), name it.

This specificity also translates better — "almonds" (amandes, Mandeln, almendras, миндаль) is unambiguous across languages in a way that "tree nuts" is not.

Distinguish between "contains" and "may contain traces"

These have different implications for guests with severe allergies:

• "Contains" — the allergen is a direct ingredient.
• "May contain traces of" or "prepared in a kitchen that also handles" — cross-contamination risk.

Guests with severe allergies, particularly nut allergies, often need this distinction to make safe choices. Make sure your translated text preserves this distinction and doesn't collapse both statements into a single generic warning.

Positioning matters

Allergen information works best when it appears:

• Directly on the dish entry (not just in a separate section or sheet)
• Consistently formatted across all dishes
• Visible at normal reading size (not footnote-sized)

On a digital QR menu, you can display allergens inline with each dish. This is generally more useful than a separate allergen list because guests see the information exactly when they need it — while they're deciding what to order.

If your kitchen handles ingredients that are major allergens — nuts, gluten, shellfish — every dish you serve carries some cross-contamination risk. How you communicate this risk in multiple languages is genuinely difficult, because:

1. The standard phrasing varies by language and culture ("may contain traces" is UK English convention; other languages use different formulations)
2. Guests' interpretation of risk language varies — some guests with mild intolerances are comfortable with trace warnings; guests with severe anaphylactic allergies may not be
3. Automated translation can soften or misrepresent risk language

A practical approach: keep your cross-contamination warning consistent in your primary language, have it translated once by a bilingual speaker or specialist, and then ensure that exact phrase is used consistently across your menu rather than re-translating per item.

When you set up your menu in MenuTap, allergen information can be included directly in your dish descriptions or as a dedicated field per item. A few best practices:

Write allergen information clearly in your source language. The cleaner and more explicit the source text, the more accurate the translation. "Contains: wheat (gluten), milk, eggs" translates better than "has dairy and stuff like that."

Use a consistent format for every dish. If you list allergens as a comma-separated line at the end of each description ("Contains: gluten, milk"), do this for every dish. Inconsistency creates uncertainty — guests may not know whether a missing allergen line means no allergens or just incomplete information.

Review allergen fields in translated versions before publishing. For each language you activate, look specifically at the allergen information on a sample of dishes. If the translated allergen text looks significantly different in length or format from the original, investigate before publishing.

Update allergen information immediately when recipes change. If an ingredient substitution introduces a new allergen, update the menu that day — in all languages simultaneously. This is one of the strongest practical advantages of digital menus: a single update propagates everywhere at once.

Before publishing or updating a multilingual menu:

• Every dish with a regulated allergen lists that allergen explicitly (not just in the description, but in a clearly formatted allergen field or line)
• "Contains" and "may contain traces" are distinguished consistently
• Specific allergen names are used (almond, not "nuts"; cow's milk, not "dairy")
• Cross-contamination language has been reviewed by a native speaker in each key language
• Allergen information in translated versions matches the source content in substance
• A process exists to update allergen information the same day a recipe changes

Even with a well-translated menu, some guests with serious allergies will want to speak to staff. This is reasonable and should be welcomed.

Train your team on a basic multilingual script for allergen conversations:

• "Do you have a food allergy?" — Avez-vous une allergie alimentaire? / Haben Sie eine Lebensmittelallergie? / ¿Tiene alguna alergia alimentaria? / Hai allergie alimentari?
• "Please speak with our manager" — Veuillez parler avec notre responsable. / Bitte sprechen Sie mit unserem Manager. / Por favor, hable con nuestro responsable. / Per favore, parli con il nostro responsabile.

These phrases don't require fluency — they acknowledge the concern and direct the guest to someone who can help. The multilingual menu handles information delivery; staff training handles the conversation.

If your menu doesn't currently list allergens in a structured, consistent way, start there before worrying about translation. A clear allergen list in one language, consistently applied across every dish, is more useful to guests than an inconsistent one in five languages.

Once your allergen information is solid in your primary language, MenuTap can translate it alongside the rest of your menu — with all language versions updating in sync whenever you make changes.

Questions about allergen labelling for your specific menu? Email support@menutap.biz — or visit our Getting Started Guide to see how the setup process works.

This guide provides general information and is not legal advice. Consult local regulations and a qualified food safety professional for compliance requirements specific to your jurisdiction.

Last Updated: June 2026
For more restaurant guides, visit our Learning Center