How to Add Allergen Information to a Restaurant Menu

Clear allergen information starts in the kitchen

When a guest asks whether a dish contains nuts, milk, gluten, or another allergen, the answer cannot depend on who happens to be working the shift. It needs to come from a checked recipe and reach the guest in a form they can understand.

Allergen information is therefore both a guest-experience concern and an operational routine. The menu should make the information easy to find, while the restaurant keeps the underlying details current when recipes, suppliers, or preparation methods change.

If you are still deciding how to structure your digital menu, start with Digital Menu for Restaurants: How It Works, Benefits, and Why to Adopt It. This guide focuses on one important part of the menu: helping guests identify relevant allergens without having to guess.

1. Treat allergen information as operational data

Do not try to infer allergens from a dish name. “House sauce,” “vegetable fritters,” and “chocolate dessert” can all contain ingredients a guest needs to avoid. Check the complete recipe, including:

• sauces, marinades, dressings, and garnishes,
• stocks, seasoning blends, and cooking fats,
• bread, pasta, pastry, and other bought-in components,
• substitutions and optional toppings,
• supplier label changes, and
• shared equipment or preparation surfaces that create a cross-contact risk.

The goal is not to promise that a dish is safe for every person. The goal is to give accurate information about the ingredients and preparation conditions the restaurant has reviewed. That distinction matters: a menu label is useful only when it reflects what the kitchen is actually serving.

2. Start with the list and rules that apply to your location

In the European Union, Regulation (EU) No 1169/2011 identifies 14 substances or products that cause allergies or intolerances. The European Commission says allergen information is mandatory for non-prepacked food, including food served in restaurants and cafés, while national measures can define how that information is provided. Read the Commission's mandatory food information guidance and confirm the details that apply in your country.

The 14 EU categories are:

• cereals containing gluten,
• crustaceans,
• eggs,
• fish,
• peanuts,
• soybeans,
• milk,
• nuts,
• celery,
• mustard,
• sesame,
• sulphur dioxide and sulphites above the applicable threshold,
• lupin, and
• molluscs.

This list is a useful starting point, not a substitute for local guidance. Restaurants outside the EU may have different legal categories, thresholds, or presentation requirements. If you operate in more than one country, document the rule set used for each menu rather than assuming one legend covers every location.

3. Build a review sheet for every dish

Before adding symbols or notes to the public menu, create one internal record per item. A simple table can include:

| Menu item | Relevant ingredients | Allergens to declare | Preparation note | Last reviewed | | --- | --- | --- | --- | --- | | Roast chicken | Chicken, butter, stock, mustard glaze | Milk, celery, mustard | Glaze added during service | 17 Aug 2026 | | Vegetable curry | Coconut milk, soy sauce, sesame garnish | Soy, sesame | Garnish is optional but available | 17 Aug 2026 |

Use supplier labels and the current recipe as your sources. Record the date and the person who checked the item. When a supplier changes a sauce or a chef changes a garnish, the review sheet gives the team somewhere specific to update instead of relying on memory.

This also helps with keeping your restaurant menu accurate across every channel. The public QR menu, printed menu, website, and staff reference should all come from the same reviewed information.

4. Put the answer close to the ordering decision

Guests should not have to open several pages or wait for a staff member to decode unexplained icons. Choose a presentation that fits the menu and use it consistently:

• a short allergen note below each relevant item,
• familiar text labels with a clear legend,
• a linked allergen guide that keeps the item name visible, or
• a combination of item notes and a staff-supported reference.

For example:

Roast chicken
Roast chicken, rosemary potatoes, and mustard glaze. €18
Contains: milk, celery, mustard.

If you use icons, show the written name as well. Icons can be hard to interpret, translate, or read with assistive technology. Do not put the only copy of the information inside a food photograph or a scanned PDF. Text is easier to resize, search, translate, and maintain. Digital Menus and Accessibility: Making Ordering Easier for Everyone covers the broader usability principles.

In the EU, allergen information for non-prepacked food may be communicated verbally under national rules, but the European Commission notes that there must be a clear indication of how guests can obtain it and that written information must be available on request. A digital menu can support that process; it does not remove the need for a trained team and a reliable reference.

5. Use precise language instead of broad promises

Good allergen wording tells the guest what the restaurant knows. It does not turn a complex kitchen into a guarantee.

Prefer specific notes such as:

• “Contains milk: the sauce is made with butter.”
• “Contains wheat: served with wheat pasta.”
• “Contains soy: the dressing uses soy sauce.”
• “Ask the team about substitutions; preparation depends on current ingredients.”

Be careful with claims such as “allergy-friendly,” “safe,” or “free from.” They may imply controls the kitchen does not have. A dish without a listed ingredient can still involve shared equipment or a changed supplier product.

The European Commission's allergen guidance also distinguishes precautionary statements about unintentional presence from basic ingredient information. A blanket “may contain” warning should not replace good preparation controls or a dish-by-dish review. If cross-contact is a concern, assess it with the person responsible for food safety and follow the rules that apply locally.

6. Connect menu changes to the pre-service routine

Allergen information goes stale for the same reasons prices and descriptions do. Build it into the change routine rather than treating it as a one-time publishing task:

1. Compare the day's recipe and supplier products with the review sheet.
2. Flag any changed ingredient, garnish, sauce, or preparation surface.
3. Update the internal record and the public menu before service.
4. Brief the front-of-house team on the change and likely questions.
5. Test the public QR link on a phone.

Seasonal specials deserve the same review as permanent items. When a special is removed, remove its allergen note too. When a dish returns, do not restore an old label without checking the current recipe.

How to Use a Digital Menu for Seasonal Specials and Limited-Time Offers explains the publishing side of temporary items. The same discipline applies to the ingredient information attached to them.

7. Keep translations and dietary labels aligned

An allergen note that is correct in one language but vague in another is still a source of confusion. When a dish changes, review its English, Portuguese, and other published versions together. Translate the allergen name and the explanation, not just the dish title.

Avoid using a translation model as the final reviewer for ingredient or allergen information. AI can help produce a first draft, but the kitchen or food-safety owner must confirm the result against the recipe and local terminology. How to Attract Tourists with a Multilingual Restaurant Menu covers the wider process for serving guests in more than one language.

Keep voluntary labels separate from allergen declarations. “Vegan,” “vegetarian,” “spicy,” and “gluten-free” can answer useful questions, but each claim needs its own definition and review. Do not use a vegan label as a shortcut for “contains no allergens,” because those are different questions.

8. Test the guest path and the staff answer

Before publishing, ask someone who did not write the menu to complete a few tasks on a phone:

1. Find the allergen information for one main dish.
2. Explain what a symbol or “contains” note means.
3. Find the restaurant's instruction for asking about an item not fully covered.
4. Switch to another language and check whether the information is still clear.
5. Ask a staff member the same question and compare the answer with the menu.

If the guest has to zoom into an image, return to the home page, or ask where the legend is, improve the path. If the staff answer differs from the menu, pause publication until the recipe, reference, and wording agree.

A practical allergen-information checklist

Before the next service, check that:

1. Every current dish has been reviewed against its recipe and supplier labels.
2. Relevant allergens are named in words, not only represented by unexplained icons.
3. Cross-contact questions have an owner and a documented local process.
4. The public menu explains how guests can ask for more information.
5. Changes to specials, sauces, garnishes, and substitutions trigger a recheck.
6. Translations and dietary labels match the reviewed source.
7. The QR menu works on a phone and keeps the information easy to find.
8. The front-of-house team knows where the current reference lives.

Accurate allergen information is not a decorative badge added at the end of menu design. It is a small information system connecting recipes, suppliers, kitchen practice, staff answers, and the menu a guest actually opens.

Make the safer answer easier to find

Start with the recipes your guests ask about most often. Review the ingredients with the kitchen, choose a clear notation, test it on a phone, and give the team one current reference to use during service.

Menuit helps restaurants keep a live, mobile-friendly menu that is easier to update when dishes, ingredients, prices, and translations change. Use it as the publishing layer for reviewed information, and keep the restaurant's food-safety process responsible for the facts behind every label.