Checking one formula against multiple markets at once

A single product sold in five countries is, from a compliance standpoint, five products. Each market has its own permitted ingredients, its own maximum levels, its own claim rules, its own labeling requirements. Checking one formula against all of them by hand is slow, repetitive, and exactly the kind of task where something gets missed. A market-aware compliance engine does it at once, as you formulate. Here is how that works and why it changes things.

Why one formula faces many rulebooks

Regulations are territorial. A nutrient form permitted in one market may not be in another. A maximum level differs from country to country. A claim authorised in one region is not allowed in another. So the same formula — unchanged — can be compliant in one market and non-compliant in the next.

For a company selling internationally, this means compliance is not a single check but a matrix: every product against every market it is sold in. And that matrix grows with every product added and every market entered.

The manual approach and why it strains

Done by hand, multi-market compliance means holding the rules for each market — limits, permitted forms, claims — and checking each formula against each one, every time the formula changes or a market is added. It is feasible for one product in one market. It becomes a serious burden across a catalogue and several markets, and a fragile one: rules change, the matrix is large, and a single skipped or outdated check is a compliance gap.

What a market-aware engine does

A compliance engine encodes the rules for each market and checks the formula against them automatically. You select the markets a product is for, and the engine evaluates the formula against each market's requirements at once:

Maximum levels — the cumulative amount of each nutrient checked against each market's limit, flagging where a market's ceiling is exceeded.

Permitted forms and ingredients — each ingredient checked against what each market allows, flagging a form or substance not permitted in a target market.

Claims — the claims a product carries checked against what each market authorises and what the formula supports.

The result is a clear picture, per market, of whether the formula is compliant — and where it is not.

Checking as you formulate, not after

The decisive difference is timing. Manual checking happens at the end, when a formula is finished — so a problem means going back and reformulating, with all the rework that implies. A built-in engine checks as you build, so the moment an ingredient or dose pushes a market out of compliance, you see it while you can still adjust. Compliance becomes a live constraint during formulation, not a verdict delivered afterwards.

This also reveals the binding constraint — often the strictest market sets the real ceiling — so you can decide whether to formulate to the strictest limit for one global formula or maintain market-specific variants, with the actual numbers in front of you.

Keeping the rules current

Regulations change, and a compliance check is only as good as the rules behind it. A maintained compliance engine keeps the market rule data current, so checks reflect the present rules rather than a snapshot from whenever a spreadsheet of limits was last updated. This is a key question to ask of any compliance feature: who keeps the rules current, and how.

Because regulations differ by market and change over time, confirm the current requirements for your specific products and markets rather than relying solely on any general summary.

Where Lemoniq fits

Lemoniq includes a market-aware compliance engine. Select the markets a product is for, and it checks the formula against each market's maximum levels, permitted forms and ingredients, and claim rules at once — flagging issues as you formulate, not after. It surfaces the strictest applicable constraints so you can choose between a single global formula and market-specific variants with the real numbers visible. The rule data is maintained, so checks reflect current requirements, and the same market selection drives the correct labels and documents for each market.

The takeaway

Selling across markets turns every formula into a compliance matrix — different limits, forms, and claims in each. A market-aware engine checks one formula against all your markets at once, as you build it, so problems surface while they are still cheap to fix and the strictest constraints are clear. The matrix that strains a manual process becomes a selection and a set of automatic checks.

Lemoniq checks one formula against every market you sell into — limits, permitted forms, and claims — live as you formulate. See how it works