Regulatory Management: Compliance Checked in the Recipe
Regulatory screening usually sits in a separate system, run in batches by someone other than the formulator. A direction gets developed for weeks before anyone confirms whether it can be sold in the markets it was intended for, and by the time the answer arrives it is too late to change what was worth trying in the first place. Meanwhile someone in regulatory affairs keeps a spreadsheet of permitted levels current by hand, checking official registers for amendments that may or may not have happened.
Uncountable maintains its own regulations database, kept up to date from the official sources, so your team never maintains regulations manually. Ingredients map to the rules for the product category you are making, not to the ingredient alone, which is the difference between a permitted level that applies to your product and one that does not. Every recipe shows a pass or fail for each market you sell into, inline on the recipes page as the formula is built, with one column per market so a failure in a single jurisdiction is visible immediately. Every row carries its jurisdiction, product category, permitted level, a pinned link to the official source, and the date it was last checked.
House interpretations hold. Admins can edit or override any row, and re-pulling a source will not overwrite that edit, so the way your regulatory team reads a rule survives every update. Source wording stays verbatim in its original language and tagged, so nothing is lost in translation. A failing result can stop a recipe being locked or published, configurable per workspace, and the check can run against the recipe as formulated or the finished product, whichever basis your team works to.
The regulation is visible as you formulate.
FAQs
It covers how Uncountable checks ingredient regulations inside the formulation workflow: where the regulation data comes from and how it is kept up to date, how ingredients are mapped to the rules for a product category, what the formulator sees on the recipes page, how house interpretations are preserved, and how a failing check can gate a release.
Uncountable maintains its own regulations database and keeps it up to date from the official sources, so nobody on your team updates limits manually. Sources are re-pulled when the published text changes, and every row carries its citation and the date it was last checked, so you always know exactly what edition a recipe was evaluated against.
A screening tool sits alongside the work and answers in batches. Here the check runs where the formulation is built, so status is visible on the recipe itself rather than in a separate system. Permitted levels are scoped to the product category rather than the ingredient alone, and the regulatory result sits on the same record as the formulation and the quality data behind it.
Yes. Admins can edit or override any row, and those edits survive a source refresh rather than being overwritten. Regulation wording is kept verbatim in its original language and tagged, so your regulatory team can check an interpretation against the source text rather than against a translation.
The failure appears inline on the recipes page as the formula is built, with the market, the governing regulation, and the permitted level shown alongside it. A failing result can be configured to block a recipe from being locked or published, so a non-viable direction is caught before it is developed rather than after.
