Reformulating to remove an additive: finding the swap without breaking the label

A regulator restricts an additive, a major retailer bans it from their shelves, or the market simply turns against it — and a manufacturer has to take a colour, sweetener, preservative or anti-caking agent out of products that were built around it. The temptation is to treat it as a deletion. It never is. The additive was doing a job, and removing it without replacing that function quietly breaks the product. Here is how to run an additive swap as a controlled change.

The additive did a job — name it first

Before removing anything, the manufacturer has to be honest about the function: the colour was masking an unappealing natural shade, the preservative was holding microbial stability, the anti-caking agent was keeping the powder flowable, the sweetener was carrying the taste. Delete it and the function goes with it. The reformulation is really a substitution — a different ingredient, or a system of ingredients, doing the same job within the new constraints. Software that records what each ingredient is for keeps that function from being lost in the edit.

The replacement reshapes the label

Swapping an additive ripples straight into the label. The ingredient list changes; the new additive may carry its own E-number, allergen or origin declaration; a natural colour replacing a synthetic one may bring a "colouring foods" consideration; a different preservative may shift the warnings. Running the swap as a tracked formula version with the panel, ingredient list and allergens regenerated catches these label consequences while the formula is on screen, not after artwork is printed.

Cost and dose rarely stay still

Natural replacements often cost more and work at higher inclusion levels than the synthetic additive they replace, which changes both the cost per unit and the space left in the formula for everything else. In a tight format — a small tablet, a packed gummy — a bulkier replacement can force other trade-offs. Seeing the cost and the formula's spare capacity update as the swap is modelled keeps the decision grounded in what the product can actually absorb.

Do it once, apply it everywhere

An additive being removed for regulatory or commercial reasons is usually in more than one product. Solving the swap once and applying the same replacement system across every affected formula — rather than re-solving it per SKU — keeps the catalog consistent and the work finite. A shared-ingredient system makes "replace X with Y everywhere it appears" a deliberate operation instead of a manual sweep.

Keep the before and after

When the change is questioned — by a retailer, an auditor, or your own QA — the useful answer is the two versions side by side: what the additive was, what replaced it, what changed on the label, and when. Versioning preserves that comparison automatically.

Because additive rules and permitted replacements differ by market, confirm the current requirements for your specific products rather than relying on a general summary.

Where Lemoniq fits

Lemoniq records what each ingredient does, runs additive swaps as tracked versions with the panel, ingredient list, allergens and cost regenerated, and — because ingredients are shared records — lets one replacement decision apply across every formula that used the additive. The before-and-after is the version history.

The takeaway

Removing an additive is a substitution, not a deletion, and its consequences land on the label, the cost and the dose. The manufacturers who do it cleanly are the ones who name the function, model the replacement as a tracked change, and apply it consistently across every product that used it.

Lemoniq turns an additive removal into a controlled swap with every label and cost consequence regenerated. We solve this exact problem. See how it works