Formula Change Control: Who Can Change Your Recipe, and How

Picture the last two years of your best seller. During a shortage, the plant switched to a different supplier's paprika. Your operations lead raised the vinegar a little to pull a pH reading back toward the middle of the range. The dried garlic was backordered, so frozen garlic went in instead. A buyer asked for less sugar, so some came out. Every one of those decisions was reasonable. None of them was written down in the same place, and nobody ever tasted all four together against the product you launched.

That is how a formula drifts. Not through carelessness, but through small, sensible fixes that each made sense on the day. Change control is the habit that stops it. The phrase sounds like a big company's quality department, but for a brand with a handful of SKUs and one or two co-packers it comes down to three agreements: what counts as a change, who can approve one, and where it gets written down.

Whether a product needs reformulating at all is a different question, covered in recipe reformulation: when and why to rethink your formula. This article is about the plumbing underneath every change, planned or forced on you.

What Counts as a Change

Start by drawing the line, because drift lives in the gray area where nobody thought a change was big enough to mention. My working test: if it could move the taste, the texture, the color, the pH, the Brix (the measure of dissolved solids, mostly sugar), the label, or the allergen statement, it is a change. That covers more than most brands expect.

• Ingredients. A new ingredient, a removed one, or a different percentage of an existing one.
• The same ingredient from somewhere else. A new supplier, grade, or form. Tomato paste at a different solids level, vinegar at a different strength, ground chile replaced with an oleoresin (a concentrated spice extract), or the reverse. Oleoresins can hold heat and color more steadily than ground spice over shelf life, which is a good reason to consider one. It is still a change.
• Process. Order of addition, cook temperature, hold time, agitation, fill temperature, cooling, or a move to a different kettle or line.
• Packaging. Container size or shape, closure, headspace. These can matter to the thermal process, not just the look of the shelf.
• The spec itself. Widening a pH or viscosity range is a change, even if nothing in the kettle moves.

Corrections are not changes

One distinction keeps this from turning into paperwork for its own sake. A good spec already tells the plant how to correct a batch that lands slightly off target, within limits you wrote down in advance (and, for anything that touches the acid or the pH, limits your process authority has seen). Using an allowed correction is the spec working, not a change to it. The same goes for an alternate ingredient already qualified and written into the spec, which is the whole idea behind qualifying a second source for critical ingredients ahead of a shortage. Anything outside those goes through change control.

Give Every Version a Number

A version number sounds like software, but it solves a food problem: when a customer writes in about a jar, you need to know which formula made it. Keep the scheme simple. For example:

• Whole numbers (2.0, 3.0) for any change that touches the label, the allergens, the claims, the Nutrition Facts panel, or anything your process authority reviewed.
• Decimals (2.1, 2.2) for changes that stay off the label and outside the reviewed process, such as qualifying an equivalent ingredient from a new supplier or tightening a range.

The scheme matters less than three rules that go with it. Every document carries the version and the date: the formula, the spec sheet, the process notes, the label file, and ideally the plant's batch sheet. Old versions are marked superseded and kept, never deleted. And the change log records the first lot code made under each new version, so any jar on any shelf traces back to its formula. If your lot codes cannot answer that today, run a mock recall and take a hard look at your lot coding.

The Change Log: One Entry per Change

The change log is a running record, one per product. A spreadsheet is fine. What matters is that there is exactly one, that you hold it, and that every entry answers the same questions:

1. The new version number and the date it was approved.
2. What changed, exactly, written as before and after. "Changed the vinegar" is not an entry. The old ingredient, supplier, and percentage set next to the new ones is.
3. Why. A shortage, a cost target, a buyer request, a quality fix.
4. Who asked for it.
5. What was tested, and against what. For anything that touches flavor, that means a side-by-side against your gold standard (the reference sample that defines the product), with the call made at week two, once the flavor has settled.
6. Which downstream items were checked, and the result for each. The list is in the next section.
7. Who approved it, in writing.
8. The first lot made under the new version, and the plan for old labels and leftover ingredient stock.

If an entry cannot be filled in, the change is not ready to run.

What One Small Change Can Touch

This is the part that earns change control its keep. A single ingredient swap can ripple into places nobody at the kettle is thinking about. Walk every change through this list on purpose. Most changes touch one or two items. The point is to rule the others out in writing instead of by assumption.

• The ingredient statement. A new ingredient, a compound ingredient with its own sub-ingredients, or a percentage shift that reorders the list all mean new label copy, reviewed by whoever handles your label compliance.
• Allergens. A replacement spice blend, flavor, or starch can bring an allergen, or a cross-contact question from the supplier's facility, that the old one did not. It can also change how the plant schedules and cleans around your product. See allergen control in co-packing for the plant's side.
• The Nutrition Facts panel. Changes to sugar, salt, oil, or anything else that shifts the numbers may mean recalculating or retesting the panel. A nutrition label service does the work. Your job is to tell them a change is coming.
• Claims and certifications. No added sugar, gluten-free, vegan, organic, Non-GMO. A new supplier has to carry the same paperwork, and some certifiers expect to hear about a formula change before it happens. Your retailers' ingredient rules and your own brand values (pasture-raised eggs, for example) can rule out a substitute that works perfectly well in the kettle.
• The process authority review. A process authority letter covers the formula and process it reviewed. Changes to the acid, the amount of low-acid ingredients like vegetables or beans, particle size, fill temperature, container size, or the thermal process are the kind that often go back to the process authority. Whether yours does is their call, not yours and not mine. See FDA process authority letters for acidified foods.
• pH headroom. Plants and process authorities like a finished pH with room to spare, since pH can drift after production. A change that nudges your pH up a tenth can matter even when the number still looks comfortable.
• Texture through the process. A thickener is matched to what it has to survive, from the acidity to the plant's kettles and pumps. Swap in one that seems like "the same thing" and the texture can look fine at fill, then thin out or weep on the shelf weeks later.
• Shelf life. Anything that touches acid, sugar, salt, oil, a preservation hurdle, or packaging can change how the product ages. Ask your shelf-life testing lab whether the existing study still holds.
• Your finished-product targets. If a change moves pH, Brix, viscosity, or color on purpose, update the targets and ranges, or the plant will measure the new product against the old numbers.
• Buyers and stock. Some buyers expect advance notice of a formula change. Old labels need a plan, and so does the pallet of an ingredient you no longer use, which will not keep forever.

Who Is Allowed to Say Yes

Write down who approves what, and give a copy to every plant that makes your product. A simple version for a small brand:

• The brand owner, usually the founder or CEO, signs off on anything that changes how the product tastes, what the label says, or what it claims. It is your name on the jar.
• Whoever holds the formula, your product lead or an outside formulator, reviews the technical side: does the change do the same job, what does it do to pH, texture, and flavor, and what testing does it need.
• The co-packer's food safety and quality team reviews anything that touches their process, their food safety plan, their allergen program, or their line. They have the final word on what their plant can run safely.
• The process authority reviews anything that touches what their letter covers. Who arranges that review varies: sometimes the plant handles it, sometimes it falls to the brand. Find out which before you need it, and put it in writing.
• Your label and regulatory help reviews the ingredient statement, the panel, and the claims.

Two rules make this hold up. First, approval is written. An email reply that names the version number counts. A nod during a plant walk-through does not. Second, the person who proposes a change is never the only person who approves it, and that includes the founder. Plenty of changes start inside the brand, from a sales promise to a buyer to a late-night idea about the heat level, and they go through the same process as anything the plant suggests.

When the Plant Proposes a Substitution

Sooner or later the request comes. The plant would like to use a different starch, another supplier's vinegar, or a pre-blended spice mix instead of six separate weighings. It helps to understand why plants ask. Their supplier may be short. They may already buy a similar ingredient in volume and would rather store one pallet than two. A different starch may handle their pumps and shear better. A pre-blend removes a weighing step, and an error point, from a busy line.

Those are good reasons. Co-packers optimize for their line, and that is their job. Your spec protects your product, and that is yours. A plant that asks before it swaps is working with you the right way, and it deserves a real answer, quickly. Here is how to give one.

1. Thank them, then get the details in writing. The exact proposed ingredient, the supplier's spec sheet, a recent certificate of analysis, the allergen statement, any certifications, and the reason for the request.
2. Ask whether it is temporary. A short supply gap may be better handled as a time-limited exception for named lots than as a permanent new version.
3. Compare by function, not by name. What jobs does the current ingredient do: flavor, body, acidity, color, emulsion, the story on the label? The substitute has to do all of them, not just the obvious one.
4. Test it side by side. Bench batches against your gold standard, judged at week two. If it passes, a pilot or a closely watched first batch at the plant, because ingredients behave differently in a full kettle. The pilot batch protocol applies to changes as much as it does to launches.
5. Walk the touch list. Every item in the section above, ruled in or out on paper.
6. Decide, and say why. Approve it (as a new version, as a listed alternate in the spec, or for named lots only) or decline it. If you decline, explain why and help solve the problem behind the request. If the issue is supply, maybe you source the ingredient yourself, or the two of you qualify a different alternate together.

What you are protecting against is not bad faith. It is accumulation. Four substitutions, each one close enough on its own, can add up to a product that no longer matches the one your customers chose. Change control is how you see the sum before your customers taste it.

Setting It Up Without a Quality Department

You do not need software or a quality manager to start. You need a folder and an afternoon.

• One master formula document per SKU, with the version number and date in the header.
• One change log per SKU, started today. If you do not know the history, write down what is running now and call it the current version. That is a legitimate starting point.
• A one-page approval list showing who signs off on what.
• A short written note to each co-packer: please do not change ingredients, suppliers, or process steps on our products without written approval of a new version; here are the alternates already approved; here is who to contact. A clear process helps the plant too, because it tells them how to get a fast yes.
• A request that batch records name the formula version.
• A sample from every batch, sent to you. Quality control is mostly the plant's job, and they do it on every run. Tasting each batch against your gold standard yourself is how you catch a change that slipped past the paperwork.

The Judgment Calls Behind the Paperwork

The system above is the easy part to copy, and I would rather you had it than not. What it cannot do on its own is make the technical calls. Will a proposed starch hold at your pH through that plant's shear and hold time? Will a new paprika fade faster by month nine? Which changes should go to your process authority, and with what data? Those answers depend on the specific product, its ingredients, and the line it runs on. Working them out, alongside the people who run the plant and review the process, is the part of formula work I do inside client projects.