The Food Standards Agency (FSA) sets the tone for how UK food businesses should handle allergen information. You do not need to memorise every guidance page. You do need to understand what "accurate, available and clear" looks like on a real menu in a real service.
This article turns FSA-style expectations into practical menu habits.
The core idea
Allergen information must be:
- Accurate — it matches what is actually in the dish today
- Available — guests can get it before they order, without chasing staff for ten minutes
- Clear — people can understand it without decoding jargon or tiny footnotes
Whether information is on a digital menu, a written matrix, packaging or provided by trained staff, those three tests still apply.
Non-prepacked food vs PPDS
FSA guidance distinguishes how information is provided depending on how food is sold:
- Non-prepacked (most restaurant meals): you must provide allergen information for the 14 regulated allergens; how you present it can vary, but it must be accurate
- PPDS: full ingredients list with allergens emphasised on the pack (Natasha's Law)
Many venues do both — plated meals and grab-and-go. Treat them as two workflows sharing one recipe database, not two unrelated jobs.
What "accurate" really costs you
Accuracy fails when operations move faster than documentation:
- Specials written on a board but never allergen-checked
- Supplier swaps accepted at goods-in without updating recipes
- Weekend chefs improvising dressings
- Multi-site menus copied from head office while local kitchens diverge
FSA guidance assumes you know your ingredients. That only works if someone owns the data and updates it when reality changes.
Making information available without friction
Guests increasingly expect allergen detail before they speak to a server — especially via QR menus. A printed matrix at the till can meet a minimum bar and still fail the guest experience if it is incomplete or hard to use.
A stronger pattern:
- Structured allergens on every dish
- Guest-facing filters for common exclusions
- Staff access to the same live data
- A clear path to escalate complex questions to a manager
Quiteful supports that pattern with live menu updates, custom allergens and dietary tags alongside the regulated 14.
Clear communication beats clever design
Avoid:
- Icons with no key
- "Ask staff" as the only answer for every dish
- Inconsistent wording between sites
- Mixing preference language ("light", "clean") with allergen facts
Prefer:
- Plain names for allergens
- Dish-level detail, not section-level guesses
- Honest limits on cross-contact when you cannot guarantee a free-from environment
Inspection culture, not inspection panic
Environmental health officers look for systems that work, not laminated theatre. If your team can show how allergen information is maintained, who updates it, and how guests receive it, you are in a stronger position than a venue with a perfect poster and chaotic recipes.
Takeaways for managers
- Assign ownership of allergen data
- Review specials and supplier changes on a fixed cadence
- Give guests a self-serve path to accurate information
- Train staff to verify, not guess
- Keep PPDS labels and plated-menu data aligned where you sell both
FSA guidance is not asking for perfection overnight. It is asking for a system you can defend — and guests can trust.
Explore how nutrition and allergen data sit together on a Quiteful menu.