Natasha's Law and Recipe Changes: Keeping Labels Accurate

One of the most common ways Natasha's Law compliance breaks down in practice is not through ignorance of the law, but through process failures when recipes change. A label that was accurate yesterday can become a liability today if the recipe changes and the label does not.

Why Recipe Changes Are High-Risk

When a supplier changes a product formulation, an ingredient becomes unavailable, or a kitchen team makes a substitution, allergen content can change without anyone in the business explicitly updating the label. This is how allergen-related incidents happen even in businesses that understand the law.

Trigger Points for Label Review

Every one of the following should automatically trigger an allergen label review:

A supplier notifies you of a formulation change to an ingredient
You substitute an ingredient due to availability issues
A recipe is updated or adjusted by the kitchen team
A new supplier is used for an existing ingredient
Seasonal variation requires ingredient substitution

Building a Recipe Change Process

A practical process looks like this:

Document every recipe with full ingredient list and allergen matrix
When a change is made, update the recipe document before production begins
Review the allergen matrix against the updated recipe
Generate updated labels before packaging new batches
Confirm old labels are removed from circulation

The Role of Supplier Communication

Many allergen incidents trace back to a supplier changing an ingredient without adequately notifying customers. Build supplier allergen notification requirements into your procurement contracts. Request advance notice of formulation changes.

Managing Version Control for Recipes and Labels

One of the most overlooked aspects of allergen compliance is version control. When a recipe exists only in someone's head, or as a single unlocked spreadsheet that anyone can edit, there is no reliable audit trail. If an incident occurs, you need to be able to demonstrate exactly what was in a product on a specific date, what label was applied, and who approved the change. Without documented version history, that defence is not available to you and enforcement bodies will take a dim view of informal systems.

The practical solution is to treat recipe documents the same way software teams treat code: every change creates a new version, the previous version is retained, and a responsible person signs off before the new version is used in production. This does not need to be expensive software. A clearly structured folder system with dated files and a simple sign-off log can be sufficient for smaller producers. What matters is that the process is consistent, followed every time, and that old versions are archived rather than deleted.

Version control also protects you commercially. If a wholesale customer or retailer asks you to evidence your allergen management process during an audit, being able to produce a clean version history of your recipe documents demonstrates a mature, systematic approach. It shows that compliance is embedded in your operations rather than handled reactively. That kind of documentation builds trust with buyers and reduces the likelihood of being delisted if an allergen query arises.

Cross-Contamination Risks During Transition Periods

Recipe changes create a specific window of elevated risk that is often underestimated: the transition period between old and new batches. During this window, both the old ingredient and the new one may be present in your production environment simultaneously. If a product previously contained no nuts and the reformulated version uses an ingredient processed on shared equipment with nuts, there is a real contamination risk during the changeover that needs to be actively managed rather than assumed away.

Standard operating procedures should define exactly what happens when production switches from an old recipe to a new one. This includes cleaning protocols between batches, sequencing decisions about which products are made first on a given day, and clear labelling of ingredient storage containers so that the old and new versions of an ingredient are never confused. These are not hypothetical scenarios — they are exactly the circumstances under which allergen incidents occur in otherwise well-intentioned food businesses.

It is also worth considering what happens to any partially used stock of the old ingredient once a recipe change has been made. If that ingredient contained an allergen that the new formulation does not, using it up informally in the next batch creates an undeclared allergen in what is now supposed to be a reformulated product. A clear policy of segregating and disposing of superseded ingredients, rather than using them up to avoid waste, is the correct approach and should be written into your recipe change procedure.

Updating Digital Listings Alongside Physical Labels

For food businesses selling through Shopify or any other online channel, a recipe change requires updates in two places simultaneously: the physical label on the product and the digital product listing on your storefront. These two things can easily fall out of sync. A label reprint might be handled by the production team while the website is managed by someone else entirely, and without a shared checklist or system, one of them gets missed. The result is a customer who reads accurate allergen information on your website but receives a product whose label reflects the old formulation, or vice versa.

Natasha's Law applies specifically to prepacked for direct sale products at the point of sale, but the allergen information you publish online forms part of the overall picture a customer relies on to make safe choices. If your website lists a product as free from sesame and your reformulated recipe now includes a sesame-containing ingredient, that discrepancy carries real legal and reputational risk. Online product descriptions, ingredient lists published on product pages, and any downloadable allergen guides should all be included in your recipe change checklist as mandatory update items.

Using a tool like Allergen Matrix helps close this gap by connecting your allergen data directly to your Shopify product listings. When you update your allergen information in the app, it reflects across your store rather than existing in a separate document that someone has to remember to act on. For businesses managing a range of products with overlapping ingredients, this kind of systematic approach is far more reliable than manual updates and significantly reduces the chance of a critical inconsistency going unnoticed.

Staff Training and Accountability Around Recipe Changes

Compliance systems are only as effective as the people operating them. A well-designed recipe change process can still fail if staff do not understand why each step matters, who is responsible for each action, or what to do when they are unsure. Training should not be a one-time induction exercise. It should be revisited whenever a process changes, whenever a new team member joins, and ideally on a regular scheduled basis so that the reasoning behind the procedures stays fresh rather than becoming routine steps that people follow without understanding.

Accountability is equally important. Each step in your recipe change process should have a named responsible role attached to it. Updating the recipe document might be the responsibility of the head of production. Reviewing the allergen matrix might fall to a designated compliance lead. Confirming old labels are removed from circulation might be a warehouse or packaging team responsibility. When everyone knows which steps are theirs to own, things are far less likely to fall through the gaps that exist between roles.

It is also worth creating a simple mechanism for kitchen and production staff to flag concerns when they notice something that does not look right — an ingredient that seems different from usual, a label that does not match the recipe they are working from, or a supplier delivery that came with different documentation than expected. A culture where staff feel confident raising these observations, rather than assuming someone else has already checked, is one of the most effective practical safeguards a food business can build. Process documents matter, but the people following them matter more.

What to Do When a Change Happens Unexpectedly

Not every recipe change is planned. Emergency ingredient substitutions happen, supplier deliveries arrive with reformulated products that were not flagged in advance, and kitchen teams sometimes make practical adjustments mid-production. These unplanned changes are the highest-risk scenarios precisely because they fall outside the normal review process. Having a clear protocol for what happens when a change occurs unexpectedly is just as important as having a process for planned reformulations.

The first step in any unplanned change scenario should always be: stop and check before continuing production. If an ingredient has been substituted without a prior allergen review, that review needs to happen before that batch is packaged and labelled. This may feel disruptive, but it is significantly less disruptive than a product recall or an allergen incident affecting a customer. Build this expectation explicitly into your team culture so that pausing to check is seen as the right and responsible action rather than an inconvenient delay.

Document unplanned changes with the same rigour as planned ones. Record what changed, why, when, who made the decision, and what allergen review was completed before production continued. Over time, a log of unplanned changes can also reveal patterns — a supplier who routinely delivers reformulated products without notification, or an ingredient category that is consistently difficult to source consistently — that inform longer-term procurement and process improvements. Reactive compliance is a minimum standard; using incident data to improve your systems proactively is what separates businesses that stay compliant from those that are perpetually catching up.

Try Allergen Matrix free at saltai.app — no credit card required.