The problem: one ingredient change, many formulas to update
When a supplier issue hits an ingredient, teams have to find every affected product, judge the impact and update each formula, often by hand.
A supplier discontinues an ingredient used in a sub-recipe. The team has to find every product that uses it, directly or through premixes, and assess each one.
What this demo shows
- Keep one versioned record per product.
- Turn a supplier issue into a change request.
- Review an AI-drafted impact summary.
- Swap the ingredient and recalculate every affected formula.
Why it matters
An ingredient changes. Know which products need attention. Where-used relationships show every affected formula, including those using it through a sub-recipe.
Recalculating every affected formula, with cost rolled up and rechecked against spec, makes the impact clear before the change is approved.
See it with your own data
This video is part of Product Lifecycle Management. To see how it would work with your own formulations and records, request a demo. Our team replies within 30 minutes during business hours.
Read the transcript
Uncountable is one platform for R&D, quality, and product life cycle work. Each product has one record, what it is made of, how it was developed, and every version. The formula is multi-level. Sub-recipes roll up into the parent. So does cost to a cost per kilogram held against a target in the spec.
When a raw material has to change, its ingredient page lists the formulas that use it. Before the change goes for approval, Bodie, Uncountable's built-in AI, drafts the impact summary from those formulas. Change one ingredient in the sub-recipe, and every formula built on it recalculates and is checked against its spec again. Traditional PLM keeps version history.
Uncountable also keeps how each version was developed.
