Multi-site food businesses face a specific allergen problem: head office publishes one menu story while individual kitchens quietly diverge. Guests — and regulators — still expect accuracy at the door they walked through.
Consistency does not mean identical prep everywhere. It means known differences, recorded and communicated.
How drift happens
- Local supplier swaps when the approved SKU is out of stock
- Franchise or regional taste tweaks to sauces
- Site-level specials never entered into the central system
- Old QR codes pointing at a group PDF that ignores local changes
- Training quality varying by manager
None of these are malicious. All of them break allergen trust.
Choose a model: central recipes with explicit overrides
A workable pattern:
- Maintain master recipes and allergen flags centrally
- Allow site overrides only through the same system
- Make overrides visible on that site's guest menu
- Review overrides on a schedule so temporary hacks do not become permanent lies
Quiteful's multi-location tooling is built around shared menus with room for local difference — the important part is that difference lives in data, not in someone's head.
One guest channel per site
Avoid a single group PDF for every location if kitchens are not truly identical. Prefer:
- Location-specific QR codes
- Location-specific digital menus
- Clear site names in the header so staff and guests know what they are viewing
Embeds on area websites should pull the right venue's data, not a generic brand menu.
Governance that busy ops teams will follow
- Appoint an allergen owner per site and a group owner
- Require same-day updates for supplier-driven allergen changes
- Ban off-system specials: if it is sold, it is in the system
- Audit two dishes per site per month against actual prep
Keep the rules short enough that people obey them.
Training across the estate
Roll out the same FOH scripts and escalation paths, then add site notes for layout-specific cross-contact (shared fryers, pizza ovens, bakery sections). Consistency of behaviour matters as much as consistency of flags.
Reporting what is out of sync
Group managers should be able to see which sites have overridden key recipes and which menus were updated recently. Silence is how a dairy-free dressing in Manchester becomes a buttermilk ranch in Leeds under the same dish name.
PPDS across sites
Packed products add another layer. If Site A and Site B both sell "tuna mayo baguettes" with different mayo, labels and ingredients lists must differ too. Shared dish names are not shared formulations.
Bottom line
Multi-site allergen safety is change control. Centralise what you can, document what you cannot, and publish the truth for each door. Guests do not care about your org chart — they care that the dish in front of them matches the information they used to choose it.
Several doors across a town is a different shape from several outlets inside one hotel or food hall. That destination case is one page for every outlet.