Managing Frozen Ingredient Changes After Recipe Approval

When an approved frozen ingredient changes, compare the proposal with the version and application originally accepted. Identify what changed, which finished products use it, and what evidence is needed before that version can enter routine production. The decision should cover the ingredient, recipe, process, label and transition lots. Updating a purchasing code alone leaves too much of that decision unexplained.

Not every change needs the same work. An administrative reference change with a documented connection to an unchanged ingredient is different from a new cut, processing site or allergen profile. The review should establish that difference from evidence. This guide uses fictional frozen carrot and fruit examples to show how purchasing, development and QA can organise the work without turning every proposal into either an automatic approval or a complete development restart.

Recover the approved ingredient and its recipe context

Begin with the actual approved specification and revision. Find the supplier and manufacturing-site identity, product form, composition, relevant limits, packing configuration and agreed intended use. Locate the approval record that explains why this version was accepted. If the original decision depended on a particular sample, connect its identity and trial record to the specification rather than relying on a bag in the sample freezer with an incomplete label.

The recipe context matters as much as the incoming description. An ingredient might be accepted for a cooked soup but still be under evaluation for another application. Record the finished-product codes, recipe versions, addition stage and process route covered by the approval. Include the particular customer or market where that limits its use. A single “approved supplier” entry should not be stretched into an approval for every ingredient, factory and recipe offered by that company.

Imagine a manufacturer using frozen carrot cubes in vegetable soup. Its original trial used a named cut specification, a defined recipe and a recorded mixing and filling route. Purchasing later receives a proposal for a different cut under a new material reference. The first task is to retrieve those original conditions. A photograph of the old cubes can help identify appearance, but it cannot recover the cooking, mixing or filling conditions that were never recorded.

Also find the boundaries that were intentionally left open. Perhaps the original approval covered a named site but allowed a specified range of crop origins. Perhaps two packing formats were accepted, but only one was trialled through an automatic dosing system. These distinctions prevent unnecessary work on an option already assessed, while exposing a proposed use that sits outside the agreed scope.

The Innovation Center for US Dairy’s supplier controls resource packet distinguishes supplier information, technical data sheets and notification arrangements. Although written for dairy businesses, it makes a useful document-control point: assess whether the information answers the questions relevant to your product. For a frozen ingredient, build the baseline around the approved form and application, not around whichever attachment happens to be newest.

If the baseline is incomplete, record that gap. Do not invent an earlier acceptance limit or describe an unrecorded trial as a validated process. The team may need to reconstruct the approval from reliable records or agree new work before it can judge the proposed change fairly.

Describe the change before deciding its significance

Ask for a comparison that states the existing condition, proposed condition, reason, intended timing and affected products or lots. “Equivalent quality” is a conclusion to assess, not an adequate description of the change. Useful notification gives the buyer enough detail to understand what would arrive differently and which supporting records will change with it.

For produce, the proposal could concern origin, cultivar, cut geometry, maturity selection, processing, manufacturing site or packing. Ask whether more than one attribute changes at once. A move to another site might also introduce another cutting line, a different pack or revised testing arrangements. Reviewing only the site name can miss the combined proposal that the customer actually needs to assess.

The two original carrot photographs in this article show different physical forms. They are not samples from a paired trial, and they do not establish a size specification. Their value is simpler: “carrot” alone does not describe cubes and crinkle-cut coins adequately. A proposed substitution needs an explicit cut description, together with the other attributes relevant to the approved recipe.

Distinguish a planned change from a nonconforming delivery. If a shipment fails an agreed specification, manage that deviation through the business’s hold and disposition process. Do not quietly revise the specification to make the lot appear compliant. A buyer may separately consider a controlled alternative use, but the original result and the actual decision need to remain traceable.

Set notification responsibilities in the supply agreement. Define the types of change requiring advance discussion, the technical contact, the information expected and how customer approval is recorded where required. Agree commercially workable notice periods for the product and programme. A universal number of notice days would ignore the difference between an artwork update, an agricultural contingency and a new production route.

Temporary and emergency proposals need a defined scope too. If an alternative ingredient is requested for a limited order, state the permitted product, quantity or lots and the end condition. Urgency changes the scheduling problem; it does not answer a safety, label or application question. Keep the request under review until the responsible people have made the necessary decisions.

A supplier should not have to guess which features matter to your recipe. Explain, for example, that visible carrot distribution after filling is an acceptance point, or that a customer requires a named origin. That information helps the supplier flag relevant changes early instead of sending a general notice after the material has already been produced.

Map the effects on recipe, process and label

Follow the proposed change into each finished product that uses the ingredient. Purchasing can identify where it is ordered, development can explain its function, production can describe its route through equipment, and QA can review hazards and acceptance criteria. Include the person responsible for labels and customer specifications where those may be affected. Give each unresolved question an owner rather than asking everyone to sign the same unexplained approval box.

The following matrix is an authored review aid. It names questions to investigate; it does not assign automatic risk ratings or prescribe a test package. Some rows may close through documented review. Others may lead to a recipe trial, production trial, supplier assessment or additional safety work. The reason for that choice belongs in the decision record.

For the fictional carrot soup, a smaller cut raises concrete questions: will the filled portion still show the expected pieces, can the dosing and transfer route handle the proposed distribution, and does the change affect any assumptions used to assess the process? Those are separate questions. A pleasing appearance in a bowl does not settle process safety, and a satisfactory incoming inspection does not establish the customer’s preferred bite.

Composition and allergen information require particular care. A plain vegetable description does not tell you everything about a proposed seasoning, coating or shared-line situation. Canadian CFIA guidance connects ingredient substitutions with updated recipes and label review, and distinguishes allergens in the ingredient from those handled on the line or at the establishment. Review the destination’s requirements; do not copy one country’s allergen list into every market decision.

Customer requirements may be more specific than the general review process. Coca-Cola’s published ingredient supplier allergen requirement, revised in September 2020, requires its suppliers to report allergen-status changes promptly and review relevant changes in cross-contact risk. This is an example of one customer’s programme, not a universal notification contract or an XMG certification claim.

Choose checks that answer the actual uncertainty

Write the review question before choosing the test. If the only documented change is an administrative code and the supplier establishes that the ingredient, site, process and use remain unchanged, a controlled document review may answer the question. If the proposed cut may affect the finished soup’s appearance, inspect the cut and compare the application. If a change may affect a safety control, send that issue to the qualified food-safety reviewer rather than trying to clear it through a sensory panel.

For US facilities subject to the relevant preventive-controls requirements, 21 CFR 117.170 requires reanalysis when a significant facility change creates a reasonable potential for a new hazard or a significant increase in an existing hazard. It also addresses qualified oversight and documenting the basis when revision is unnecessary. Apply the provision’s actual scope and timing requirements; a commercial change form does not replace the required food-safety work.

When an application trial is needed, preserve the conditions that make the comparison interpretable. Use the identified baseline and proposed ingredient, the agreed recipe, the same preparation route and a defined observation point. Record what was held constant and what changed. If the team also adjusts mixing or adds more liquid, say so: it is then evaluating a revised recipe or process, not isolating the ingredient alone.

In the carrot example, development could compare the two forms in the same soup recipe, record piece distribution and texture using an agreed method, and retain clearly identified observations. The production team can then decide whether a line trial is needed for dosing, transfer or filling. No fixed number of bowls or production runs proves suitability for every change. Plan the coverage around the variability and decisions that matter to this programme.

Consider another fictional proposal: a fruit ingredient from a different cultivar for an approved sauce. If the recipe depends on acidity, flavour or consistency, obtain the relevant information and test the effect in that application where necessary. Do not assume a matching product name, or a matching value for one measurement, establishes the whole recipe outcome. Equally, do not declare the new cultivar unsuitable before reviewing it.

SQFI’s change management guidance describes evaluating connected effects, assigning approval and checking the implemented result. Use the code and edition applicable to the site. As checked in September 2026, the Edition 10 FAQ says audits will not begin before 2 January 2027 and that timing depends on benchmarking progress. Publication of guidance should not be presented as proof that a particular factory is already audited against that edition.

Close each question with a reasoned outcome: evidence accepted, further work needed, change rejected, or a clearly limited use approved. Record restrictions as part of the approval itself. A trial that supports one soup recipe should not silently authorise every finished product using the same purchasing ingredient code.

Keep old and new versions separate through the handover

Approval needs an effective boundary. Identify the last intended old-version supply and the first intended new-version supply using the available production, shipment and lot references. A calendar date can help organise the plan, but it is rarely enough on its own when stock is in transit or several production dates arrive together. Ask how the physical bags and cartons will show which version they contain.

Use the same distinction in purchasing, receiving, storage and production instructions. If a system must retain one commercial ingredient code, establish another reliable way to control the revision and permitted use. Do not rely on the storekeeper recognising a slightly different bag shade. The identification should survive decanting, partial use and movement between storage and the production area.

For a fictional handover, version A remains approved for the original soup while version B is accepted only for a revised soup recipe. Receiving records identify the version, storage keeps it distinguishable, and the production order names the permitted pairing. An operator can then verify the actual ingredient against the recipe instruction without searching the development team’s email history.

Decide what happens to remaining old stock before the new material arrives. It might continue in an already approved use, be held for a decision or require another disposition. Do not infer that the new approval cancels every previous approval, or that leftover stock can automatically be blended into the new recipe. Where rework or mixed-version use is proposed, have the responsible team review that specific use.

Labels and documents need an equally clear handover. Make the current production recipe available, withdraw obsolete working copies and control any artwork affected by the change. CFIA’s guidance includes keeping recipes current and checking labels when formulation changes. Record which label version goes with which finished product; a correct new label can still be wrong if applied to an old recipe with different information.

Before release, make a practical check with the people who will handle the stock. Show them the identification method, the production instruction and the action to take if they disagree. This often reveals a missing field more quickly than another round of signatures. Keep the technical approval and the operational instruction connected so the reviewed version is the one actually used.

Review the first use and close the change

Define what will be checked after implementation and who will review it. The first routine use is an opportunity to confirm that the agreed version arrived, the instructions were followed and the relevant outcomes remain acceptable. This is verification of the implemented change. It should follow the necessary approval and safety work, with suitable controls for any trial production that has separate restrictions.

Look at the points that motivated the review. For the carrot soup, that might include receiving identification, dosing behaviour, filled piece distribution and the agreed finished-product observations. Review any applicable process-control records through the site’s food-safety system. Record the actual conditions so that a different outcome can be investigated instead of being attributed immediately to the supplier.

If an issue appears, identify the affected lots and manage them under the appropriate hold or disposition procedure. Compare the incoming material, recipe, line conditions and handling history. A problem after a change is a reason to investigate; timing alone does not prove which changed feature caused it. Keep the supplier informed with the observed facts and the evidence needed to narrow the question.

A temporary substitution also needs closure. Record whether the business returns to the previous version, extends the limited approval or starts a separate permanent-change review. Do not let an emergency purchasing workaround become routine simply because no one entered an end date into the ordering system.

The completed file should let a colleague answer six questions: what changed, why it changed, where its effects were assessed, what evidence supported the decision, which lots and uses were authorised, and what the first implementation showed. Keep unresolved limitations visible. That record is more useful for the next crop or supply change than a folder containing several unsigned specifications with similar names.

Finally, update the baseline for the uses actually approved. Retain the earlier version and its decisions according to the business’s document-retention requirements. The next reviewer should be able to compare a new proposal with a stable, traceable starting point, while still understanding which older stock or customer programme may follow a different approved version.

References

• eCFR: 21 CFR 117.170, reanalysis.
• CFIA: preventive controls for allergens, gluten and added sulphites.
• Innovation Center for US Dairy: supplier controls resource packet, Version D.
• Coca-Cola: ingredient supplier allergen requirement, September 2020 revision.
• SQFI: change management guidance.
• SQFI: Edition 10 transition FAQ.