Restaurant Allergen Labelling on a Digital Menu: What to Show and Where

The icon is correct. The order is still wrong.

A guest filters out tree nuts and opens a roast vegetable salad. The base recipe has no tree nut assigned, so the item remains on screen. She changes the dressing to cashew pesto. The option appears in the item name, but the allergen declaration does not change. At order review, the screen says only "Roast vegetable salad, pesto."

Every piece of information shown for the default salad may be technically correct. The final order is not described correctly. The failure is in the data model: the dressing changed, but the declaration remained tied to the base recipe.

A useful digital menu has to answer two questions at the point where they matter:

1. Which regulated allergens are present in this exact version of the item?
2. Can the guest find that answer before choosing or buying it?

The first is a kitchen and supplier-data problem. The second is an information-design problem. A QR code solves neither by itself.

This guide explains what restaurants should show, where it should appear, how to handle options and cross-contact, and how the baseline differs between the European Union, the United Kingdom, and the United States. It is an operating guide, not legal advice. Allergen rules and enforcement differ by jurisdiction, so the final setup should be checked against the law and official guidance where the restaurant trades.

The short version is simple. Attach named allergens to the item, update them with every recipe-changing choice, repeat the final result before an order is placed, treat filters as shortcuts rather than guarantees, keep cross-contact separate, and maintain a current alternative when the digital route is unavailable. The law where the restaurant trades determines the exact form.

Start with the rule where you trade

There is no universal allergen list for a global digital menu. Even where two countries recognise many of the same foods, the legal categories, wording, presentation rules, and enforcement route may differ.

The numbers look simple. The underlying lists do not map neatly from one market to another. Celery, mustard, lupin, and molluscs are separate categories in the EU and UK lists but are not separate federal major-allergen categories in the United States. Sesame is now one of the nine US major allergens. A numbered legend copied from one market into another can therefore be both tidy and wrong.

European Union: one duty, national presentation rules

Regulation (EU) No 1169/2011 requires information about substances or products in Annex II that are used in the manufacture or preparation of a food and remain present in the finished product, subject to the regulation's stated exceptions. For non-prepacked food, including a restaurant dish, Article 44 makes allergen information mandatory while allowing member states to set national rules on how it is provided and presented.

The 14 groups cover:

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

Those group names are not permission to become vague. The relevant cereal or nut often needs to be identified by name under the applicable rules and guidance. "Contains gluten and nuts" is less useful than "Contains: wheat, milk, cashew," and may not satisfy the naming requirement that applies to the food.

Article 44 is also why an EU-wide template cannot settle the presentation question. Germany, for example, expressly permits certain electronic information routes under its national implementation rules, with conditions on visibility, legibility, access, timing, and on-site signposting. Restaurants trading there can use the more detailed German guide to allergen labelling in digital menus. A setup reviewed for Germany should not simply be copied into another member state without checking that country's rules.

United Kingdom: written information supported by conversation

Across the UK, information is required for listed substances or products used as ingredients or processing aids and still present in the finished food, subject to statutory exceptions. FSA best-practice guidance for England, Wales, and Northern Ireland recommends written information supported by a conversation with staff. Scottish businesses should follow Food Standards Scotland guidance. Where information is provided orally under the applicable rules, guests need clear signposting that tells them how to obtain it, and the business needs accurate information behind the conversation.

For distance sales, mandatory allergen information must be available free of charge before the purchase is concluded and again at delivery. It may be provided orally or in writing; FSA best practice recommends written information at both stages. A confirmation email sent only after payment misses the first moment.

Do not use "Natasha's Law" as shorthand for every restaurant meal. The term commonly refers to the PPDS labelling changes in force across all four UK nations. PPDS is food packaged by the same business before being offered for sale from the same site or a qualifying linked mobile or temporary outlet. Its package or attached label must show the food name and a full ingredients list, with regulated allergens emphasised each time they appear. Food packed after an order is placed is not PPDS. The PPDS full-ingredients requirement does not apply to distance sales, although the distance-selling allergen duty remains. A restaurant that sells PPDS food and dishes cooked to order needs to classify each route correctly.

United States: nine federal majors, local adoption matters

The federal list contains nine major food allergens: milk, egg, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans, and sesame. Sesame became the ninth under the FASTER Act, effective from 1 January 2023.

The FDA's current model is the 2026 Food Code. It calls for written notification of major food allergens used as ingredients in unpackaged food served or sold to consumers. The Food Code is not a nationwide restaurant-menu law. It becomes enforceable where the relevant jurisdiction adopts it, potentially with amendments. A restaurant should check the code actually in force at its address.

The practical lesson is not to build three menus from scratch. It is to maintain one verified recipe record, then map and present that record according to the law of each market in which it is sold.

What the menu should show

1. Named allergens from the current recipe

The guest needs a declaration attached to the item, not a detached catalogue of substances used somewhere in the kitchen.

Use direct wording:

Contains: wheat, egg, mustard

That line is faster to understand than 1, 3, 10, particularly on a phone. If local practice permits numbers, letters, or icons, keep the legend immediately available and use the same code everywhere. Do not make a guest leave the item, scroll to the bottom of a long page, memorise three symbols, and then find the dish again.

The declaration has to include allergens inside compound ingredients. A stock may bring celery into a soup. Mayonnaise may bring egg into a sauce. Miso may bring soy into a glaze. Pesto may contain a named nut and milk. The menu item is only as accurate as the ingredient specification beneath it.

2. The allergens in the selected version

A menu should describe what the guest is about to receive, not only the default recipe in the database.

That includes:

• dressings and sauces,
• breads and alternative buns,
• cheese and other add-ons,
• marinades,
• sides included with the dish,
• garnishes,
• substitutions made during service, and
• components selected as part of a set menu.

If an option changes the allergen result, the information must change with it. Where the technology cannot combine option data reliably, the clearer publishing fallback is to list the versions as separate items. "Burger with brioche" and "Burger with sesame gluten-free bun" are longer than one configurable burger, but they are clearer than a single declaration that fits neither.

3. Ingredient allergens and cross-contact as separate facts

An allergen deliberately present in the recipe is not the same as a possible unintended transfer from shared equipment or preparation.

Keep the distinction visible:

Contains: wheat, egg, mustard

Cross-contact information, illustrative: May contain cashew because this dressing uses a shared blender and the restaurant's assessment found a residual risk after cleaning.

The second statement must reflect an actual assessment. A blanket "may contain all allergens" disclaimer is not a substitute for tracing ingredients, controlling the kitchen, or declaring the allergens intentionally used. It also leaves an allergic guest with no usable distinction between dishes.

Precautionary wording is regulated or guided differently across markets. Use it only after the locally required or recommended assessment identifies a specific residual risk. The restaurant should use the terminology expected by its authority and base it on the real process: shared fryer, shared grill, airborne flour, common utensils, supplier warning, or another identified route. "We cannot guarantee" may describe a limit, but it does not tell the guest what the limit is.

4. Dietary labels as a different layer

Vegan, vegetarian, halal, and kosher labels describe diets, ingredients, or preparation standards. They are not allergen declarations.

A vegan recipe may avoid milk and egg as ingredients while still being prepared in an environment where cross-contact is possible. "Gluten-free" and "wheat-free" answer different questions. "Nut-free" is especially imprecise because peanuts and tree nuts are separate legal categories in several systems, and the treatment of individual nuts varies.

Keep the labels separate on screen:

Dietary: Vegan recipe

Contains: Sesame

Cross-contact information: Cooked on a grill also used for wheat-containing bread

Separate fields prevent a dietary badge from being mistaken for allergen information.

5. A current answer, not an annual answer

Allergen information expires whenever the recipe beneath it changes. The trigger may be a new supplier, a substituted stock, a seasonal garnish, a different bread, a reformulated branded sauce, or a fryer reassigned for one service.

The menu therefore needs an owner and a change rule. A January review date does not validate a product substituted in October. Review the changed item before serving it.

Where guests should see it

Legal presentation requirements vary. The following is a strong operational standard because it keeps the information attached to the decision instead of asking the guest to search for it.

On the item list

The category view is where the first decision happens. A concise line such as Contains: milk, wheat lets the guest scan several options without opening each one. If the list would become unworkably dense, use a clearly named control such as Allergen information, attached to that item and reachable in one tap.

Do not hide essential information behind hover. Phones do not have hover, and keyboard or screen-reader users should not need to discover an invisible interaction.

In the item detail

The detail view can carry more context: the full named declaration, the selected components, and a separately worded cross-contact note. It is also the right place to clarify a less familiar ingredient, provided the explanation does not replace the regulated name.

An image is not the declaration. A guest cannot be expected to recognise sesame in a bun, milk in a purée, or cashew in a pale sauce from a photograph.

Beside every option that changes the answer

The option selector is not a technical appendix. It creates the final recipe.

Show the allergen effect beside the choice:

Then show the combined declaration before the guest confirms the item. If an option removes one component and adds another, recalculate rather than accumulating every allergen that any version could contain.

If the same blender is used for the cashew pesto and other dressings, cleaning and production controls need a separate cross-contact assessment. That residual risk does not turn cashew into an intentional ingredient in every dressing, and it does not justify leaving cashew off the pesto.

In the filter, with its limits

An allergen filter can reduce a long menu to a manageable shortlist. It cannot decide that a dish is safe.

A useful filter:

• names the allergens rather than showing unexplained icons,
• makes selected exclusions persist while the guest browses,
• removes only items whose assigned data matches those selections,
• updates when recipe-dependent options are included in the filtering model, and
• explains that cross-contact and unrecorded changes require confirmation.

The message after filtering matters. No items match your current filter is accurate. These items are safe for you is a guarantee the interface cannot make.

The filter is especially vulnerable to false reassurance. One missing tag leaves a dish visible. One supplier substitution makes yesterday's result stale. One option can introduce the very allergen the guest filtered out. Keep the named declaration on every item even when a filter exists.

At order review

If the menu accepts orders, repeat the final allergen declaration beside the selected item before the guest pays or submits the order. This is the last useful place to catch a dressing, bun, side, or add-on that changed the result.

Do not reduce the review to Salad x1. It should preserve the choices that matter:

Roast vegetable salad
Cashew pesto, no seeded crunch
Contains: milk, cashew

An allergy note entered by the guest is not a replacement for this information. Notes can start a conversation, but kitchens should not depend on free text to repair inaccurate menu data.

At the table and at the counter

The physical QR material should explain what the code opens. A simple line is enough:

Scan for the current menu and allergen information. Ask us for help or a printed alternative.

That wording gives the code a purpose and provides a route for the guest who cannot scan. Test the path from a real table on mobile data, while signed out of the menu editor. The broader guide to QR code menu mistakes restaurant owners should avoid covers glare, code placement, loading, and printed fallbacks.

In delivery and collection flows

Keep the restaurant's site and third-party listings synchronised. Check the local rules governing when information must be given. Where disclosure is required before purchase and again at delivery, build both stages into the flow through reliable channels such as the ordering page and a label or documentation attached to the order. Do not assume a courier, confirmation email, or kitchen ticket automatically completes that duty.

Build the record from the kitchen outwards

The digital menu should publish an approved answer. It should not be the place where the restaurant guesses one.

Step 1: Write the recipe that is actually served

Start with the current kitchen recipe, including garnishes, oils, stocks, marinades, sauces, sides, and finishing ingredients. "Tomato soup" is not a recipe. "Tomatoes, vegetable stock brand and product code, cream, basil oil, croutons" is closer to one.

Record quantities only where the kitchen needs them, but record every component that matters to the allergen assessment. Include processing aids where the applicable law requires them.

Step 2: Collect current supplier information

Use packaging, technical specifications, and written supplier information for the exact product. Do not copy an allergen line from a retailer's similar product or from last year's catalogue.

For each bought-in component, keep:

• supplier and exact product,
• specification or label version,
• date checked,
• allergens declared as ingredients,
• any supplier cross-contact statement, and
• the menu components in which it is used.

This turns a supplier change into a traceable review instead of a conversation based on memory.

Step 3: Open every compound ingredient

The short ingredient is often where the hidden allergen lives. Check the stock, spice blend, curry paste, chocolate, bread, vegan substitute, dressing, glaze, and sauce. A kitchen-made component needs its own recipe record; a bought-in component needs its current specification.

Do not infer absence from the product name. "Plant-based" does not identify every allergen. "Dark chocolate" does not settle milk risk. "House sauce" tells the guest nothing and can hide a change even from the team.

Step 4: Map the recipe to the correct legal categories

Once the actual ingredients are known, map them to the allergen framework for the market. Keep specific source data underneath the category. Cashew can be displayed as the required named nut where applicable; reducing the record to a generic nuts field throws useful information away.

For groups that differ by jurisdiction, preserve the ingredient identity rather than translating one legal code into another. A database that stores only EU allergen 10 will be harder to adapt than one that stores mustard and maps it to the relevant presentation rule.

Step 5: Model options as recipe changes

Model each modifier as an addition to or removal from the base recipe, note any preparation change, then test every combination the kitchen actually sells. If there are too many combinations to verify, the menu may be offering more configuration than the kitchen can document reliably.

Step 6: Assess cross-contact separately

Walk through receiving, storage, preparation, cooking, plating, and service. Shared scoops, grills, oil, chopping boards, cloths, blenders, flour in the air, and last-minute substitutions can matter. The statement on the menu should follow this assessment, not precede it.

Document the controls in place and any residual shared routes. Do not claim that the assessment eliminates risk.

Step 7: Use a second-person check

The person who entered the data should not be the only person who approves it.

Compare, side by side:

• the kitchen recipe,
• supplier specifications,
• the item and every option in the editor,
• the guest view on a phone, and
• the order review, if ordering is enabled.

Select one allergen filter at a time. Then select several together. Open a visible item and change every dressing, bun, side, and add-on. The test is complete only when the final screen still tells the truth.

Step 8: Define change triggers

An allergen review should happen when:

• a supplier or product changes,
• a supplier reformulates a product,
• the kitchen changes a recipe or garnish,
• a special becomes a regular item,
• an option is added or removed,
• preparation equipment or fryer use changes,
• food moves to another production site, or
• an error or guest query reveals a gap.

Assign one role to approve the update and one route for the kitchen to report it. The person who knows the fact has to be able to start the correction before the next order.

A PDF import can copy text. It cannot approve a recipe.

Importing an existing menu is useful for names, descriptions, categories, and prices. It is not an allergen audit.

A PDF may contain old footnote numbers, an incomplete legend, or a declaration that applies only to the default version. Optical character recognition can misread a small superscript. An AI tool may infer milk from "cream sauce" and still miss milk in a bought-in bread, or infer that a vegan dish is allergen-free when it contains sesame.

Use imported content as a draft. Reconnect every item to the kitchen record before publishing. The guide to replacing a PDF with a structured digital menu explains why the source document and the guest experience should be treated as separate things.

No automated system should silently convert likely ingredients into approved allergen declarations. Suggestions can help a trained reviewer find questions. They should not become facts without verification.

Translate the verified data, not the guess

Allergen names are well suited to structured translation because the underlying fact should not change with the language. The workflow still matters:

1. verify the recipe in the restaurant's working language,
2. assign the correct allergen identity,
3. translate the standardised display term, and
4. review the guest journey in each important language.

Do not ask a translator to reconstruct allergens from a poetic dish description. Do not translate a number from one national legend into the same number in another. Keep the legally required language available, then add languages that help guests understand it.

Machine translation deserves particular review around cereals, individual nuts, shellfish, sulphites, cross-contact, and dietary claims. The article on creating a multilingual restaurant menu without managing separate translations explains how to preserve one source menu while reviewing the words that carry the greatest risk.

Make the information readable by more than one kind of guest

Colour can support an allergen label, but it cannot carry the meaning alone. A red dot and a green dot are useless to a guest who cannot distinguish them, and an icon without a text alternative may disappear for someone using a screen reader.

A usable implementation should:

• show allergen names in text,
• provide equivalent text for every allergen symbol,
• give icon-only controls an accessible name and hide decorative duplicate icons from assistive technology,
• keep the item name, price, and declaration in a logical reading order,
• work with keyboard navigation and screen readers,
• remain readable when text is enlarged,
• avoid placing essential information inside an image, and
• keep the route available without hover, precise tapping, or colour recognition.

Plain language helps everyone. Contains: milk, wheat, sesame is both an accessibility choice and an editorial one.

Keep an alternative for a dead phone, weak signal, platform outage, or guest who cannot use the digital route. That alternative must come from the same current source. A six-month-old binder is not a fallback; it conflicts with the live menu.

What QR Menu Supreme can and cannot do

QR Menu Supreme currently provides 14 broad, item-level labels modelled on Annex II. Its Gluten and Nuts labels do not identify the specific cereal or nut, so where the applicable rules require names such as wheat or cashew, the labels alone are insufficient. The guest menu can show the assigned names with the item and can provide an optional filter that hides dishes carrying any label the guest selected.

Current structured allergen support stores one label set per item. It does not calculate modifier-specific allergens, provide a dedicated cross-contact field, repeat a recalculated declaration in the Max order summary, or display a limitation beside the guest filter. Until those functions are supported, add required specificity to verified item text, list recipe variants separately, and provide missing information through another verified route.

The software does not inspect a recipe, read a supplier specification, assess a shared fryer, or certify that a visible dish is suitable for a particular guest. Businesses outside the EU also need to confirm that the available categories and presentation meet the rules where they trade. Use the platform to publish facts the restaurant has approved; keep approval with the people who know the recipe and process.

Pre-publication checklist

Recipe and evidence

• Every item is linked to a current, approved recipe
• Compound ingredients have been checked to their relevant sub-ingredients
• Supplier products and specification dates are recorded
• Specific cereals, nuts, fish, or shellfish are named where required
• Recipe allergens and assessed cross-contact are recorded separately
• Dietary claims are not being used as allergen declarations

Digital journey

• Named allergen information is attached to each item
• Icons and numbers have an immediate text meaning
• Every dressing, bun, side, garnish, and add-on has been tested
• The declaration updates to match the selected version
• Filtered results do not claim that visible dishes are safe
• Order review repeats the final declaration before purchase
• The flow works with enlarged text, keyboard controls, and a screen reader

Service and maintenance

• The table or counter sign explains how to reach allergen information
• Staff know where the verified source record is kept
• A current non-digital alternative is available
• One role owns approvals and another person verifies the guest view
• Supplier, recipe, option, and process changes trigger a review
• Delivery and collection channels show the same current answer

If the restaurant is still building the rest of the guest journey, the step-by-step guide to creating a QR code menu covers structure, code placement, phone testing, and staff briefing.

Frequently asked questions

Where should allergen information appear on a digital menu?

Attach a clearly named allergen route to each item. Show a short declaration in the list when space permits and the full declaration in the item detail. Update it beside choices that change the recipe and repeat the final result at order review. A filter is supplementary, and local presentation rules still apply.

Are allergen icons enough?

Not on their own. Pair every symbol with a visible allergen name or an immediately available key. Icon-only controls need an accessible name; decorative icons that duplicate visible text should be hidden from assistive technology. Plain wording such as "Contains: milk, wheat, sesame" is usually faster to understand.

Does an allergen filter mean a dish is safe for someone with an allergy?

No. A filter can only act on the allergen data assigned to each item. It may not account for missing records, recipe changes, selected options, substitutions, or cross-contact. Treat it as a way to narrow the menu, not as a safety guarantee.

How should modifiers and substitutions change allergen information?

The declaration should follow the exact choice. If cheddar adds milk or a cashew pesto replaces a mustard dressing, the menu should show the result before the guest confirms the item and again at order review. If the system cannot calculate that reliably, list the versions separately.

Does a "may contain" statement replace an ingredient allergen declaration?

No. A precautionary statement concerns an assessed risk of unintended cross-contact. It does not replace any legally required declaration of allergenic ingredients or processing aids that remain in the finished food; statutory exceptions still apply. It should not be added as a blanket disclaimer without a real risk assessment.

Conclusion

Allergen labelling is not finished when fourteen boxes have been added to an editor.

A declaration remains current only while it matches the food, the selected options, and the information shown before ordering. It also needs a current fallback when the phone or network does not cooperate. The hard work happens upstream: approved recipes, exact supplier products, documented options, cross-contact assessment, and a change process that survives a busy service.

Start with ten frequently ordered dishes. Open every compound ingredient. Enter the verified allergens, then scan the menu as a guest and change every available option. Filter the list, open an item, review the final order, and compare the screen with the recipe in the kitchen.

If those ten dishes remain accurate from first view to final selection, the restaurant has a method worth extending. If they do not, adding the rest of the menu will only distribute the uncertainty more efficiently.

Build a structured QR menu and test the guest view with QR Menu Supreme. Enter one real dish, assign only the allergens the kitchen has verified, scan it from a table, and check what a guest sees before adding the next one.

Sources and editorial note

Legal and guidance sources checked for this draft:

• Regulation (EU) No 1169/2011, consolidated text as of 1 April 2025, especially Articles 9, 21, and 44 and Annex II.
• European Commission notice on the provision of information on substances or products causing allergies or intolerances.
• Food Standards Agency, allergen information for non-prepacked foods: best-practice approach.
• Food Standards Agency, technical guidance for businesses providing non-prepacked food.
• Food Standards Agency, selling food for delivery.
• Food Standards Scotland, allergen labelling guidance.
• US Food and Drug Administration, Food Code 2026.
• US Food and Drug Administration, FASTER Act and sesame as the ninth major food allergen.
• W3C, WCAG 2.2 guidance on use of colour and non-text content.

Editorial note: Source review date: 11 October 2026. This article provides general operational information, not legal or medical advice. Rules, official guidance, local adoption, product formulations, and software features can change. Check the requirements in the restaurant's jurisdiction and use qualified advice for a specific operation.