How to List Allergens on a Menu

Allergen disclosure on restaurant menus is becoming a regulatory requirement, not just a best practice. In California, the ADDE Act (SB-68) requires chains with 20 or more US locations to identify the nine major allergens on menus by July 1, 2026.

This guide covers how to do that in practice: which allergens to include, how to format and place disclosures, what digital options are available, and how to keep the information accurate across locations and channels.

Listing allergens is not a formatting decision. It depends on accurate food data, consistent processes, and operational control from the supply chain through to the point of ordering.

Key Takeaways

• Allergen disclosures must be clear, written, and visible to the guest at the point of ordering. They should appear alongside each menu item, not in footnotes or separate documents.
• The nine major allergens that must be disclosed are: milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soy, and sesame. This includes derivatives.
• Symbols and QR codes can support allergen communication but should not replace written statements. Under SB-68, a written alternative must always be available.
• Menu accuracy depends on upstream data accuracy. If your recipes, supplier specs, or ingredient records are outdated, your menu disclosures are unreliable.
• Every channel where a guest can view your menu needs to reflect the same allergen data: in-venue, website, and third-party delivery platforms.
• Multi-location operators need centralized allergen data, standardized recipes, and controlled update workflows to keep disclosures consistent across every site.
• Allergen disclosure is not a one-time task. It must be revisited every time a recipe, supplier, or menu item changes.

What does it mean to list allergens on a menu?

Listing allergens on a menu means identifying which of the recognized major allergens are present in each menu item and making that information visible to the guest before they order. It is not a general disclaimer at the bottom of the page. It is item-level disclosure.

In practice, this means every dish, side, sauce, drink, and dessert on your menu should indicate which allergens it contains. That includes components a guest might not think to ask about: a shared cooking oil, a garnish, a marinade, or a pre-made base ingredient.

The disclosure is customer-facing. Internal records, recipe files, and kitchen documentation support accuracy, but they do not replace the need to communicate allergen information directly to the guest at the point of ordering.

Operators are expected to disclose what they know or should reasonably know based on their recipes, ingredients, and supplier specifications. That means maintaining accurate, up-to-date food data is not a separate task from menu labeling. It is the foundation of it.

Which allergens need to be identified?

Under federal food labeling law and California’s ADDE Act (SB-68), the nine major allergens that must be disclosed are: milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soy, and sesame.

These include derivatives. Soy sauce contains soy. Casein is a milk protein. A flour-based roux contains wheat. If a derivative is present in a recipe, the parent allergen must be disclosed. For a deeper look at where allergens are less obvious, see the guide to hidden allergens and derivatives your food business must track.

There are limited exemptions. Highly refined oils (such as soybean oil or peanut oil) are generally exempt because the refining process removes the allergenic protein. However, cold-pressed or expeller-pressed oils are not exempt and must be disclosed.

How should allergens be shown on a menu?

The format you choose matters. Allergen information that is technically present but difficult to find, inconsistent, or unclear does not serve the guest and will not hold up under scrutiny.

Written allergen statements per item

The most reliable format is a written statement alongside each menu item identifying which allergens it contains. For example: “Contains: milk, wheat, soy.”

This should appear next to the item name or directly below the description. It should not be buried in footnotes, printed in a smaller font than the rest of the menu, or collected into a separate section that the guest has to go looking for. If the information is not legible at a glance, it is not doing its job.

Use language guests understand. ‘Milk’ rather than ‘casein.’ ‘Wheat’ rather than ‘gluten-containing cereals.

For a detailed walkthrough of how to format these disclosures under California’s requirements, see the step-by-step guide to allergens on menus in California.

Consistency across the menu

Every item on the menu should follow the same disclosure format. If some items show “Contains: milk, wheat” and others use a different structure, abbreviate the allergen names, or skip the declaration entirely, the guest cannot trust any of them. Consistency signals that the information is managed, not improvised.

This applies to every section of the menu: starters, mains, sides, desserts, drinks, kids’ items, and specials. If an item is on the menu, its allergens should be disclosed in the same format as everything else.

Why symbols alone are not sufficient

Symbols can support allergen communication but should not replace written statements. Not every guest will recognize a symbol for crustacean shellfish or tree nuts. Symbols require a clearly visible legend, and even with one, they are easier to overlook than plain text.

The strongest approach is written allergen names as the primary disclosure, with symbols as a secondary visual aid for guests who are scanning quickly. For a closer look at the trade-offs between icons and written text, see the article on icons vs words for ADDE Act allergen disclosure.

Can restaurants use symbols, QR codes, or digital menus?

Yes, but with limits. Symbols, QR codes, and digital menus can all play a role in allergen communication. None of them should be the only method.

Symbols

See the guidance on symbols in the section above. The same principle applies: use them as a secondary layer, not a primary disclosure method.

For more on this, see the comparison of icons vs words for ADDE Act allergen disclosure.

QR codes and digital menus

QR codes linking to digital allergen information are increasingly common, and they offer real advantages: they can be updated in real time, they reduce reprinting costs, and they allow operators to display more detail than a physical menu can hold.

However, digital access comes with requirements. The destination must be accessible on any device, load reliably, and be easy for the guest to navigate. If the QR code links to a slow page, a PDF that is difficult to read on mobile, or a system that requires an app download, the disclosure is not serving its purpose.

For a detailed comparison of digital and print approaches under California’s requirements, see the article on digital vs print allergen disclosure.

A written alternative must always be available

Under SB-68, digital-only allergen disclosure is not compliant. A written alternative must be available for guests who cannot or choose not to use a digital format. This could be a printed menu with allergen statements, a physical allergen chart available on request, or a booklet that staff can provide.

This is not just a regulatory requirement. It is a practical one. Not every guest will have a charged phone, a reliable connection, or the willingness to scan a code. The written option ensures that allergen information is always accessible regardless of the situation.

What makes allergen menu information accurate?

A clearly formatted menu disclosure is only as reliable as the data behind it. If the allergen information in your recipes is wrong, outdated, or incomplete, the menu will be too. Accuracy is not a design problem. It is a data problem.

The data flow

Allergen accuracy starts at the supply chain and moves through every stage before it reaches the guest:

Supplier specification → ingredient record → recipe → menu → customer.

A breakdown at any point in that chain means the guest receives inaccurate information. A supplier changes a product formulation. An ingredient record is not updated. A recipe uses a compound component with undisclosed allergens. The menu is never revised. Each of these is a separate failure point, and in most operations, they are managed by different people using different systems.

Hidden allergens in compound ingredients

Not every allergen is obvious from a product name. A pre-made sauce may contain soy. A seasoning blend may include wheat. A stock base may contain fish derivatives. If your recipes use compound ingredients, the allergen data for those components must be broken down to the individual ingredient level. Relying on product names or assumptions is where inaccuracies enter the system. For more on where these risks occur, see the guide to hidden allergens and derivatives your food business must track.

Multi-component and customizable dishes

Combo meals, build-your-own options, and dishes with selectable sides or toppings create additional complexity. Each possible combination carries its own allergen profile. If a guest can swap a side or add a topping, the allergen implications of every option need to be documented and accessible at the point of ordering.

Supplier and recipe changes

Allergen data is not static. Every time a supplier substitutes a product, reformulates an ingredient, or changes a source, the allergen profile of any recipe using that ingredient can change. The same applies when your own team modifies a recipe, introduces a new dish, or updates a shared component used across multiple items.

If these changes do not trigger an automatic review of the affected menu items, the gap between your actual allergen data and your published allergen data grows with every update. Setting up automated supplier alerts is one way to catch these changes before they reach the guest.

Why centralized data matters

When allergen information is managed in spreadsheets, emails, or local files at individual locations, version control becomes impossible at scale. A centralized allergen database that connects supplier data, recipes, and menus in one system ensures that a change at any point in the chain flows through to every downstream output. Without that connection, menu accuracy depends on someone remembering to update a document, and that is not a system.

Common mistakes when listing allergens on menus

Most allergen disclosure failures are not dramatic. They are small, repeated oversights that accumulate until the information a guest relies on is no longer accurate.

Using symbols without a clear legend. Allergen symbols are helpful as a visual aid, but if the legend is missing, too small, or placed on a different page, guests will misread or overlook them. Symbols should always sit alongside written allergen names, not replace them.

Missing allergens in sauces, dressings, or garnishes. A dish may be free from major allergens in its core ingredients but contain milk in the dressing, soy in the sauce, or sesame in the garnish. Every component that reaches the plate must be accounted for in the disclosure, not just the main protein or base.

Not disclosing allergens across all components of a dish. A burger may list wheat in the bun but miss the egg in the aioli or the milk in the cheese. Combo meals, platters, and dishes with multiple elements need allergen data for every part, not just the item name on the menu.

Inconsistent information across channels. The allergen data on your in-store menu, your website, and your listing on third-party delivery platforms should match. If a guest sees one allergen profile in-store and a different one on a delivery app, the discrepancy creates confusion and liability. The responsibility for accuracy on every channel sits with the operator.

Outdated menus after recipe or supplier changes. A recipe changes. A supplier substitutes an ingredient. The allergen profile of one or more dishes shifts. If the menu is not updated at the same time, guests are making ordering decisions based on information that is no longer correct.

No version control or change tracking. If you cannot show when your allergen data was last updated, who made the change, and what it replaced, you have no way to evidence accuracy during an audit. Spreadsheets are particularly weak here because they offer no audit trail, no version history, and no way to confirm that every location is using the current version.

Treating allergen disclosure as a one-time task. Setting up allergen information when a menu launches and then never reviewing it is one of the most common sources of inaccurate data. Allergen disclosure is an ongoing process. It needs to be revisited every time a recipe, supplier, or menu item changes.

Not accounting for customizable items. If a guest can modify a dish, add a topping, swap a side, or build their own meal, the allergen implications of every possible combination need to be documented. A “build your own” option without allergen data for each component leaves the guest guessing.

How multi-location restaurants keep allergen menus consistent

The biggest risk for multi-unit operators is not getting allergen information wrong at every location. It is getting it right at some and wrong at others. When one site updates its menu data and another does not, or when a local manager substitutes an ingredient without updating the allergen record, the guest experience becomes unpredictable across the brand.

Centralized food data

Allergen accuracy across multiple locations starts with a single source of truth. When recipe and allergen data is held centrally, every location pulls from the same dataset. A change made once flows to every site. When data is held locally in spreadsheets, printed sheets, or individual files, every location is effectively maintaining its own version. That is where inconsistencies enter.

Standardized recipes

If locations are free to adjust recipes, swap ingredients, or source locally without a formal review process, the allergen profile of a dish can differ from site to site even though the menu item name is the same. Standardized recipes with defined ingredients, suppliers, and preparation methods are the baseline for consistent allergen disclosure. Any deviation should trigger an allergen review before the modified dish is served.

Controlled update workflows

When a recipe changes, a new item launches, or a supplier substitutes an ingredient, the update needs to follow a defined path: allergen data is reviewed, the menu is updated across all channels, and the relevant locations are notified. If any of those steps depend on someone remembering to act rather than a system prompting them, the update will eventually be missed. A multi-site allergen governance framework defines who is responsible for each step and how changes are approved and distributed.

Version control and change logs

If an auditor asks when your allergen data was last updated for a specific dish, you need to be able to answer with a date, a name, and the detail of what changed. A digital audit trail that timestamps every change to recipe, ingredient, and allergen data makes this possible. Without it, you are relying on memory and file dates, neither of which hold up under scrutiny.

Regular audits

Consistency does not maintain itself. Schedule regular checks to verify that the allergen information displayed at each location, on your website, and on third-party delivery platforms matches the current central record. Pay particular attention to app menus, which often lag behind in-store updates because the process for updating them sits outside the operator’s usual workflow.

How SB-68 affects allergen menu labeling

California’s ADDE Act (SB-68) takes effect on July 1, 2026. It requires restaurant chains with 20 or more US locations to disclose the nine major allergens on menus. The information must be written, accessible to the guest at the point of ordering, and accurate.

This is not a voluntary best practice. It is a legal requirement with fines ranging from $500 to $2,500 per violation. Repeat offenses can put permits at risk.

If you are unsure whether your operation falls in scope, see the breakdown of who the 20-plus location rule applies to. For a step-by-step preparation timeline, the SB-68 compliance roadmap covers what to prioritize and when.

The law raises the standard for execution. Disclosure on menus only protects guests if the data behind it is accurate, the format is clear, and the information is consistent across every location and channel. Everything covered in this guide, from formatting and placement to centralized data and version control, feeds directly into meeting that standard.

Frequently Asked Questions

Do I need to list allergens for every menu item?

Yes. Every item a guest can order should have its allergens identified, including sides, desserts, drinks, sauces, and kids’ meals. If it is on the menu, it needs a disclosure.

Can I use allergen symbols instead of writing them out?

Symbols can support allergen communication but should not be the only method. They require a visible legend, and not every guest will interpret them correctly. Written allergen names alongside each item are the most reliable baseline. For a full comparison, see the article on icons vs words for ADDE Act allergen disclosure.

Can I rely on a QR code for allergen information?

QR codes are a useful tool but cannot be the sole method of disclosure. Under SB-68, a written alternative must be available. Not every guest will have a charged phone or a reliable connection. Use QR codes as a supplement to printed or on-menu allergen statements, not a replacement. See the comparison of digital vs print allergen disclosure for more detail.

What happens if allergen information is wrong?

Inaccurate allergen information can result in a guest having an allergic reaction, which creates both a safety incident and a liability exposure. Under SB-68, fines range from $500 to $2,500 per violation, and repeat offenses can put permits at risk. Beyond enforcement, a single allergen incident can cause lasting reputational damage.

How often should allergen information be updated?

Every time a recipe changes, a supplier substitutes an ingredient, or a new menu item launches. Allergen disclosure is not a one-time setup. It is an ongoing process that should be built into your menu change workflow, not treated as a separate task.

Do allergen disclosures apply to specials and limited-time offers? 

Yes. Specials, seasonal items, LTOs, and catering menus carry the same allergen disclosure obligations as permanent menu items. A dish that is only available for two weeks still needs accurate allergen data from the day it launches. This is one of the most common operational gaps, particularly when LTOs are developed quickly and bypass the standard review process.

Who is responsible for allergen accuracy on third-party delivery apps? 

The operator. If your allergen or nutritional information is outdated or incorrect on a delivery platform, the compliance gap sits with your business, not the app. Treat every channel where a guest can view your menu as an extension of your in-venue disclosure. For a deeper look at how this works in practice, see the article on third-party menus and delivery apps.

Related Posts

Restaurant Allergen Disclosure Requirements

Preventing Allergen Cross-Contamination in Restaurants

Restaurant Allergen Compliance Guide

Cross-Contact vs Cross-Contamination