Ask a venue where allergen truth lives and you may get four answers: the chef's notebook, a Google Sheet, a laminated matrix and last year's PPDS label file. When those disagree, guests get the wrong information while everyone believes they are being careful.
A single recipe record is the boring fix that works.
What "one source of truth" means
Each sellable dish (and drink) has one maintained recipe that includes:
- Ingredients and sub-recipes
- Regulated allergen flags
- Any custom allergen or dietary tags you support
- Notes needed for cross-contact honesty
- Links to supplier codes where relevant
Every guest menu, staff view, PPDS label and training example should draw from that record — or from a generated view of it — not from parallel copies.
The cost of duplicates
Duplicate systems fail in predictable ways:
- Marketing updates the website PDF; kitchen changes the sauce
- Labels print from an old export
- New sites clone an outdated matrix
- Specials exist only on a board
Each copy creates a new opportunity for anaphylaxis-risk information to go stale.
What good architecture looks like in hospitality software
- Edit the recipe once
- Allergen data recalculates from components
- Digital menus update in near real time
- Label content can be generated from the same data
- Site overrides are explicit, not invisible
That is the design centre of Quiteful: menu updates, multi-location overrides, custom allergens, nutrition and PPDS-oriented workflows hanging off the same dish model.
Migration without boiling the ocean
You do not need to perfect four hundred legacy dishes on day one.
- Start with top sellers and high-risk items (nuts, shellfish, PPDS lines)
- Retire the old matrix for those items first
- Expand by section
- Freeze off-system specials
Progress beats a grand project that never launches.
People still matter
A perfect database with a culture of silent substitutions still fails. Pair the system with:
- Goods-in checks
- Stop-sale rules when data is pending
- Short FOH drills
- Manager ownership
Technology carries the record; teams protect it.
How this ties to UK duties
Whether you are meeting FSA-style expectations for accurate allergen information, Natasha's Law for PPDS packs, or simply trying not to harm a guest, the common need is the same: know what is in the food and tell the truth consistently.
One recipe record will not write your risk assessment for you. It will stop your channels contradicting each other.
Bottom line
Allergen safety scales with clarity. Collapse spreadsheets, PDFs and tribal knowledge into a single maintained recipe — then let every surface publish from it. That is how compliance becomes routine instead of a recurring scramble.
See real-time menu updates in Quiteful, or browse more on UK allergen labelling basics.