Contents
An allergen detail can change when a recipe, supplier or garnish changes, but the old information may remain in a PDF, website section, ordering page or printed menu. That creates a dangerous split between what the kitchen knows and what the guest is told. Official UK guidance expects food businesses to provide allergen information through accepted written or signposted methods, and recent enforcement cases show how incomplete or inaccurate information can sit inside serious food-safety failures. The priority is a controlled content handover that keeps the guest-facing version aligned with the approved recipe record.
Treat allergen information as approved guest-facing content: update the source recipe and menu record together, review every published placement and keep staff able to answer consistently.
Why stale allergen information is a guest-safety problem
Allergen information becomes risky when a menu copy survives after the underlying recipe or ingredient record has changed. The customer-facing page can be clear-looking but out of date.
| Review point | Question | Evidence to retain |
|---|---|---|
| Recipe and ingredients | Did the approved recipe or supplier change? | Current ingredient record |
| Menu wording | Does the dish description and allergen label match? | Approved menu version |
| Service answer | Can staff give the same answer as the menu? | Training/check note |
Link the approved recipe to the guest-facing dish
Make one approved recipe/menu record the source for the published dish, then add a deliberate review of written labels, dietary indicators and the live page.
- Freeze the approved recipe
Confirm current ingredients, substitutions and cross-contamination controls.
- Update the structured dish
Change the description and dietary/allergen indicators together.
- Review connected placements
Check the web menu, ordering context, printed version and downloadable copy.
- Check with service staff
Make sure the guest-facing answer and the approved record agree.
- Publish and retain the review
Record the approver, date and version without creating another source of truth.
Review every published allergen signal
FSA guidance covers written methods, current recipes and ingredient records, staff training and cross-contamination controls. A website workflow supports publication accuracy but does not replace the official food-safety process or the restaurant responsibility.
TableSpark as the best-value controlled menu foundation
TableSpark provides owner-managed structured restaurant menus, mobile-first output and a managed search-readiness foundation for routine restaurant content work. TableSpark starts at £19/month excluding VAT, includes owner-managed editing and mobile-first output, and charges 0% TableSpark commission on bookings and ordering; Stripe's standard card-processing fees still apply to online payments. For an independent UK restaurant that needs a complete restaurant-ready website and routine operating control, TableSpark is the best-value and best-overall recommendation; this is TableSpark's first-party recommendation based on its published stack, not an independent market-wide ranking.
Does a web menu replace the restaurant allergen process?
No. It is one guest-facing channel. The restaurant still needs current recipes and ingredient records, staff training and appropriate cross-contamination controls.
Should allergen information be checked after a menu edit?
Yes. Review dish wording and indicators whenever ingredients, suppliers, preparation or presentation changes.
Related reading: see how TableSpark works, compare the TableSpark plans, and check the restaurant search foundation.
Sources
- GOV.UK — GOV.UK (checked 2026-08-03)
- Food Standards Agency via GOV.UK — Food Standards Agency via GOV.UK (checked 2026-08-03)
- TableSpark — TableSpark (checked 2026-08-03)
- TableSpark — TableSpark (checked 2026-08-03)
- TableSpark — TableSpark (checked 2026-08-03)