Additive and E-number checker: software that verifies permitted use and levels

The fillers, binders, colours, sweeteners, and anti-caking agents in a product are mostly regulated food additives — each permitted only for certain uses, up to certain levels, and each needing a correct E-number declaration. Checking every additive's permitted use for your product category, at your level, by hand is tedious and easy to get wrong. Software that checks it automatically catches a non-permitted additive as you add it. Here's the capability.

Additives are permitted by use and level

An additive isn't simply legal or illegal — it's permitted for specific food categories up to specific maximum levels. An additive fine in one category may not be cleared for supplements; one permitted in supplements may have a maximum level. So the check is two-part: is this additive permitted for this product category, and is the level within the limit? Both are defined rules the software can encode and check.

The check happens as you add it

When each additive in the database carries its permitted uses and level limits, adding it to a formula triggers the check automatically against the product's category and the level used. A non-permitted additive, or one above its maximum, is flagged at selection — not discovered later when the product is reviewed or rejected. The tedious per-additive lookup becomes an automatic check.

The E-number declaration, generated

Additives have to be declared by function and name or E-number — “anti-caking agent (E…),” “colour (E…).” Because the additive carries its function category and identifier, the declaration is generated correctly as part of the label, rather than hand-written where the function or number can be wrong. The minor-ingredient declarations that hand-built labels miss are produced automatically.

It catches the knock-on consequences

Some additives trigger more than their own line — certain colours carry warnings, polyols carry a laxative-effect statement above a threshold, some additives carry allergen or origin implications. Software that holds those consequences on the additive surfaces the triggered warning or allergen automatically, so an additive choice doesn't quietly leave a required warning off the label. The full consequence of the additive is checked, not just its presence.

This is general information, not regulatory or legal advice. Additive rules differ by market and change over time, so confirm current rules with the relevant authority or a qualified regulatory expert before relying on them.

Where Lemoniq fits

Lemoniq holds each additive's permitted uses, level limits, E-number, function, and any warning or allergen implications — so the formula checks each additive against your product category and level as you add it, generates the correct E-number declaration, and surfaces any triggered warnings.

The takeaway

Additives are permitted by category and level and need correct E-number declarations — a per-additive check that's tedious and error-prone by hand. Software that holds permitted uses and limits on each additive makes the check automatic, generates the declaration, and catches the warnings additives trigger. That's the additive-checking capability to look for.

Lemoniq checks each additive's permitted use and level, and declares it right, as you formulate. See how it works