Allergen Disclosure Basics Every Restaurant Owner Should Know

If your restaurant has never had a formal approach to allergen disclosure, you are not alone, and the good news is that getting to a reasonable baseline does not require a legal review or a specialist consultant. It requires a clear list, a consistent process, and a willingness to keep it updated.

The allergens worth starting with

Most disclosure frameworks, wherever you operate, converge on a similar core list: peanuts, tree nuts, shellfish, fish, dairy, eggs, wheat or gluten, soy, and increasingly sesame. Sulphites show up often enough in wine and dried goods to be worth including as well. Starting here covers the overwhelming majority of guest concerns even before you get into anything more specific to your region.

It is worth building this list once, in writing, rather than carrying it in someone's head. A shared reference that new hires can be pointed to, and that survives staff turnover, is worth more than any individual's memory of what usually needs flagging, however reliable that person happens to be today.

What disclosure actually requires

At minimum, it means a guest can find out, before ordering, whether a dish contains one of these allergens. It does not necessarily mean a full ingredient breakdown for every item, though that is the more thorough approach. Most regions now require some form of allergen disclosure for food sold to the public, and the general direction across markets has been toward more disclosure over time, not less, so building the habit now saves a scramble later.

A reasonable middle ground for most restaurants is dish-level tagging against the common allergen list, backed by staff who can answer a more detailed ingredient question when a guest asks one. That combination covers the majority of real situations without requiring a full recipe printout on the menu itself, which few guests would actually read in full anyway.

• Start with the common allergen list: peanuts, tree nuts, shellfish, fish, dairy, eggs, wheat, soy, sesame, sulphites
• Tag every dish against that list at the recipe level, not just the finished description
• Make the information easy for a guest to find before ordering, not only available on request
• Update tags whenever a recipe or supplier changes
• Treat this as an ongoing habit, not a one-time project you finish and forget

Where owners get stuck

The common failure point is not ignorance of the list. It is inconsistency: tagging is done carefully once, at launch, and then not maintained as the menu evolves. A disclosure system is only as good as its last update, which is why the process matters more than the initial one-time effort.

A note on staying general where you should

It is tempting to want a precise, authoritative statement about exactly what your region requires, but rules vary enough by place, and change often enough, that a restaurant owner is usually better served treating this as a floor to build above rather than a ceiling to meet exactly. When in doubt, disclosing more than the minimum rarely backfires, while disclosing less than guests expect quietly costs you their trust.

If you want certainty about your specific local requirements, that is worth a short conversation with a local health authority or an industry association rather than a generic online guide, since the details genuinely do vary by place in ways that matter.

What does not vary by place is the underlying logic: a guest deciding what to eat deserves to know, before they order, whether a dish is likely to hurt them. Whatever local rules require as a minimum, that basic obligation is worth treating as the actual standard you are building toward.

A simple way to check whether you are meeting that standard in practice, rather than just on paper, is to ask a new employee to find the allergen information for three random dishes without help. If they struggle, a guest almost certainly would too, regardless of what your official disclosure policy says on file.

TasteGraph builds allergen tagging into the onboarding process when a menu goes live, roughly a 10 minute setup per menu, and keeps those tags attached to each dish permanently so disclosure stays current without depending on anyone remembering to revisit it later.