Your menu can be perfect on Monday and wrong on Thursday because a supplier quietly changed a sauce. Reformulations, alternative SKUs and "equivalent" substitutions are normal in food supply. Allergen programmes that ignore goods-in will drift.

The hidden change problem

Suppliers update products for cost, availability, taste or regulation. Packaging may look identical. The allergen profile may not be.

Typical scenarios:

A mayonnaise base switches emulsifiers or mustard content
Bread rolls gain sesame for a seasonal recipe
A "same" curry paste is a different code with peanut
Wine or vinegar sulphite levels change enough to matter for labelling thresholds

If nobody compares the new spec to the recipe record, guest-facing information goes stale while the kitchen thinks nothing happened.

Own the intake moment

Build a simple goods-in rule:

Check the product code against what the recipe expects
Read allergen declarations on new deliveries for priority ingredients
Flag any change to whoever owns the menu data — same day
Hold sale of affected PPDS items until labels match

This does not need to be bureaucratic. It needs to be consistent.

Priority ingredients to watch

You cannot deep-read every tin every day. Focus on high-impact components:

Sauces, pastes and dressings
Breads and buns
Stocks and gravy bases
Ice creams and dessert components
Spice blends and marinades

These cause outsized allergen surprises relative to their invoice line.

One recipe system, not tribal knowledge

"Chef knows" does not scale across doubles, holidays and second sites. Keep supplier product references on the recipe where possible, and update allergen flags in the same system that powers the guest menu.

Quiteful treats recipes as the source of truth for real-time menu updates. When a component changes, you update once — QR menus, embeds and internal views can follow.

Multi-site complication

Groups often centralise recipes while sites buy local alternatives when stock runs out. That is fine if local overrides are explicit. It is dangerous if Site B silently swaps ingredients and Site A's allergen data still publishes for the group website.

Use location overrides deliberately. Quiteful's multi-location approach is built for shared recipes with local differences — the key is making those differences visible in the data.

A weekly supplier hygiene routine

Review any temporary substitutions from the past week
Confirm specials used approved components
Archive old label templates tied to discontinued SKUs
Spot-check two packed PPDS items against current specs

Communicate changes to the floor

When milk appears in a previously dairy-free sauce, FOH needs to know before the first allergy question. Pair data updates with a short shift note. Silence is how outdated answers spread.

Bottom line

Honest allergen data is a supply-chain habit as much as a menu design problem. Treat every reformulation as a menu event, and your compliance story stays boring — which is exactly what you want.

See how menu updates work in Quiteful when ingredient data changes.