Ingredient change control for hospitality groups
Written allergen menus are coming. Keeping them true is the hard part.
When an ingredient changes, every menu knows. DishSignal surfaces which dishes and menus need reviewing when a supplier or recipe spec changes — and records who decided what.
DishSignal is a change-propagation and record layer. It does not determine safety.
Why now
The FSA's March 2025 guidance made written allergen information the expectation for non-prepacked food.
It is best practice rather than law, but environmental health officers increasingly inspect against it. The FSA's evaluation of how well businesses adopted the guidance was due in spring 2026, and it feeds directly into whether Owen's Law — mandatory written allergen menus — becomes legislation.
If written allergen information becomes a legal requirement, every venue needs a maintained written source of truth. Publishing it once is easy. Keeping it accurate every time a supplier changes a spec is the product.
What happens today
The allergen matrix lives in a spreadsheet
One person maintains it. It is correct on the day it is printed and drifts from then on.
Supplier spec changes never reach front of house
A revised declaration arrives by email or PDF and stops at the person who opened it.
No trail when an EHO asks
Nobody can show who reviewed the change, when, and what they decided for each dish.
One change. One review trail. Every relevant view.
- 01
An ingredient changes
A supplier issues a new declaration. The previous version stays on record.
- 02
DishSignal surfaces the impact
Recorded recipe links surface every dish and menu that references the ingredient.
- 03
A named person reviews
A named person decides what happens to each dish, and why. That decision is recorded.
- 04
Menus and briefings update
Staff briefing and written customer wording are drafted for the operator to approve.
DishSignal supports the workflow. The operator remains responsible for every decision.
Supplier update received
EXAMPLE SUPPLIERRoasted pepper dressing · Version 2.1
Change: mustard added to declared ingredients
Three dishes require review
What the diner sees
Clearer information without pretending certainty.
Warm grain salad
Recorded ingredients include mustard.
Please speak to the restaurant team about preparation and possible cross-contact.
Why not the tools you already use
Erudus, Nutritics
Spec and nutrition data libraries.
We consume that data and act on the change: impact, review, record.
Kafoodle, Menutech
Allergen menu authoring and publishing.
Publishing once is the easy part. We keep it accurate after the tenth spec revision.
Allergen modules in menu/POS systems
A field on the dish record.
No change propagation, no named reviewer, no defensible trail.
Start with one real menu problem.
We are looking for one operator — a group, pub company or contract caterer — to run discovery against a real menu and a real supplier spec change.
Discuss a discovery pilotPre-revenue. No live integrations yet. The product demonstration uses fictional data.