Food safety/Allergen management

Ingredient substitutions: review the change before reusing a recipe record

A substitution record should identify the intended ingredient, actual replacement, information reviewed and authorised decision. A similar product name does not establish that composition, handling requirements or customer information remain unchanged.

A chef compares an original ingredient jar with a visually different replacement pesto jar before adding either to a recipe. The sous-chef checks the full ingredient declaration with a magnifier. Both jars remain closed, no invented allergen text.
AI-generated editorial illustration

At a glance

A substitution record should identify the intended ingredient, actual replacement, information reviewed and authorised decision. A similar product name does not establish that composition, handling requirements or customer information remain unchanged.

Define the decision behind the record

Give staff a clear route to report a substitution before treating the existing recipe information as current. Keep the supplier specification or packaging evidence associated with the actual product used. Unreviewed information should remain visibly unresolved.

Review a proposed ingredient before the first affected batch

Record the old and proposed ingredients with their actual supplier and specification identities. Identify the recipes, products and information that depend on the old ingredient. Assign the authorised reviewer and an intended effective point; submitting a proposed substitution is different from approving its use.

Compare the current evidence and document required changes to ingredient information, recipe, labels and handling instructions. Keep uncertainty visible and obtain clarification where needed. A matching product description, brand or package size does not establish that the ingredients have the same relevant characteristics.

Before implementation, check that the reviewed instructions reach the team and that superseded information is distinguishable. Identify the first affected batch and preserve the decision and supporting evidence. Test a substitution that is declined as well as one approved with changes, so the workflow cannot turn every completed form into automatic permission to use the ingredient.

Worked example

A delivery contains a different brand from the one specified. The receiving team records the difference and routes the replacement for review. The relevant person assesses the implications and updates the recipe information and instructions where required before authorising the next step.

Build a usable record

Use the fields below to capture the facts needed for this particular decision. Keep the actual observation separate from any later correction or approval.

  • Original and replacement ingredient
  • Supplier and product identifiers
  • Composition evidence reviewed
  • Decision and responsible approver
  • Affected recipes and communication

Example record and review decision

Fictional record example: CHANGE-01: old ingredient A / SPEC-A; proposed ingredient B / SPEC-B; RECIPE-02 and LABEL-02: affected records.

Compare the actual specifications and assess required recipe, label, process and handover updates before use.

Similar product names or packaging do not establish that allergen information and handling requirements are equivalent.

Test the review, not just the form

Try an unfamiliar replacement in a practice record. Staff should be able to report it without selecting an inaccurate equivalence. Check whether the reviewer can find affected recipes and whether the original ingredient reference survives the change.

A few useful answers

Is a matching product name enough to approve a substitution?

No. Review the relevant product information and process implications under the approved procedure.

Can a familiar ingredient name stand in for a specification review?

No. Identify the actual proposed product and evidence. Similar naming does not resolve differences in composition or instructions, and does not show which dependent records need to change before use.

Sources and further reading

Markdown

Explore starter templates

Start with a useful checklist

English