Compliance checked in the recipe
Ingredient regulations are checked as the formula is built, not after it. Uncountable maintains its own regulations database, kept up to date from the official sources, so your team never maintains regulations manually. Every recipe has a compliance status for each market you want to check.
Used by the world's leading companies
Screening Arrives After the Work Is Done
Regulatory screening usually sits in a separate system, run in batches by someone other than the formulator. Directions that were never viable get developed for weeks, and the answer arrives too late to change what was worth trying in the first place.
Today
With Uncountable
From Ingredient to Checked Recipe
Status sits on the recipe being built, not in a separate tool alongside it.
Formulators see the status for every market on the recipes page as they build, a green Pass or red Fail computed live against the regulation's limit.
One column per market, so a fail in one market is visible immediately, not discovered later in a separate review.
Check the recipe as formulated or the finished product, whichever your team uses, via per-family basis calculations.
Uncountable maintains its own regulations database from official sources, and every row carries its citation.
Every row carries jurisdiction, product category, the permitted level with units, a pinned source URL, and the date it was last checked.
Regulations are ingested and refreshed from official sources across covered jurisdictions, so your team never updates limits manually.
When an official source updates a limit, every recipe already checked against it reflects the change, without someone tracking it down.
Recipe edits can be locked down independently of the regulatory check itself.
A workspace-level change-control setting can require an edit-lease on a recipe's inputs and outputs before changes are made.
The edit-lease is a records-integrity control, configurable per workspace. It doesn't key off the regulatory status; it governs who can change a recipe and when.
A lease expires on its own; there's no manual step to release it, and no lock left open after someone forgets.
What Regulatory Management Handles
Where Regulatory Management Shows Up
Select the market and every existing recipe checks against it, rather than starting a manual screening project from zero.
A substitution that changes the compliance picture shows up on the recipe immediately, not after the reformulation is finished.
When an official source updates a limit, every recipe checked against it reflects the new rule, without someone tracking it by hand.
Checking every active recipe against its markets at once, rather than recipe by recipe on request.
The governing regulation, the source, and the last-checked date are already attached to the recipe, not reconstructed after the request.
A recipe that passed can fail after a reformulation, and the change is visible on the recipe itself, in the same place the original check ran.
.png)
The regulation is visible as you formulate, not after.
Your own regulations database, kept current from official sources, checked inline on every recipe.
FAQs
Not directly today. The Pass/Fail status is computed live and shown inline, but it doesn't itself gate a lock or publish action. A separate, workspace-level change-control setting can require an edit-lease on a recipe's inputs and outputs; that's a records-integrity control, not a regulatory pass/fail gate. Confirm current behavior with your account team if a hard release gate matters to your evaluation.
Coverage is bounded by what's been ingested into the regulations database, currently strongest in food, with jurisdiction coverage expanding. "Every market you sell into" depends on your product category and markets; confirm current coverage with your account team.
Yes, separately from the pass/fail status. A workspace-level change-control setting can require an edit-lease on a recipe's inputs and outputs, so edits are controlled and attributable. It's a records-integrity control, not a regulatory gate.
Regulatory Management is part of the Product Lifecycle suite. Check with your account team for current packaging.
