A formulation can look finished long before its product record is under control.
The lab has tested it. The ingredients are known. It may have passed stability, performance, and quality checks. But the bill of materials sits separately from the formula, cost is maintained somewhere else, and no one can state with confidence which product version is current across R&D, quality, and manufacturing.
For products made from recipes, that is not a documentation problem. It is a product-definition problem.
A coating, adhesive, cosmetic, food product, specialty chemical, or formulated material is not simply an assembly of components. Its ingredients have proportions that must balance. Some ingredients are themselves sub-recipes. A raw material can appear across many finished products. One change can affect cost, specifications, quality work, compliance, and the products where that material is used.
The best PLM for formulation-based products is the one that can represent those relationships naturally, without forcing teams to maintain the real recipe somewhere outside the system.
Why a parts model can fall short
Many PLM systems were designed around discrete products, such as equipment, electronics, vehicles, or manufactured assemblies. In those environments, the bill of materials is typically a hierarchy of parts, quantities, assemblies, and subassemblies. The central challenge is controlling product structure and engineering changes across those relationships.
Formulation products have a different logic.
A recipe contains ingredients expressed as percentages, concentrations, or formulation units. When one ingredient changes, another may need to change so the formula remains coherent. The outcome can also depend on raw-material grade, order of addition, process conditions, packaging, test method, and product application.
A standard parts-based BOM can often be configured to hold some formulation information. The question is whether the configuration still works like the recipe that scientists, quality teams, and manufacturing teams need to manage.
The warning signs are familiar:
- The formula is stored as a static attachment rather than structured data.
- Sub-recipes are flattened into a long ingredient list.
- Costs do not roll up in a way the formulator recognizes.
- The real formulation is maintained in spreadsheets because the official BOM is difficult to use.
- Product versions exist, but teams cannot see what changed in the formula or why.
- R&D, quality, and manufacturing maintain separate versions of the same product information.
Start with the formulation record
A formulation PLM should treat the recipe as a first-class product record.
That means ingredients, amounts, units, concentrations, supplier grades, process context, specifications, and revision history are held as structured information. The formula should not be a PDF or spreadsheet attached to a generic product record, because an attachment cannot easily show the relationships that matter when the product changes.
This becomes especially important during reformulation.
If a preservative moves from 0.5 percent to 0.7 percent, the product composition must remain valid. If a supplier material changes, teams need to understand whether the grade, specification, regulatory status, or performance profile is still appropriate. If a product has several regional or customer variants, the organization needs to see which version is affected before beginning an impact assessment.
The formulation record should make those questions easier to answer. It should not create another system that requires manual reconciliation.
A formulation-aware BOM is not a flat ingredient list
A bill of materials should answer a basic question: what is in this product?
For an assembly, a flat or hierarchical parts list may be sufficient. For a formulation, it is often not.
A flat ingredient list can show what was present in a formula at one moment. It does not necessarily preserve the fact that ingredients are proportions that must balance, that they have functional relationships, or that some ingredients are themselves controlled recipes.
Consider a finished coating that contains a thickener and defoamer, each of which is a separately managed formulation. Flattening those materials into one long list of ingredients hides the actual recipe hierarchy. Teams lose visibility into the version, source, cost, process context, and use of each intermediate.
A formulation-aware BOM should retain that structure. It should show the finished product, the sub-recipes inside it, and the components within those sub-recipes. When an intermediate changes, the system should make its relationship to the finished products visible instead of requiring teams to reconstruct it manually.
This matters in products such as coatings, adhesives, polymer compounds, food bases, masterbatches, fragrances, and personal-care formulations. The product structure must match how the product is developed and manufactured, not merely how a generic BOM is configured.
Cost should roll up from the recipe
Cost is often maintained in ERP or procurement systems, but product and R&D teams still need a clear view of the cost associated with the formulation they are developing or changing.
A formulation PLM should hold the relevant ingredient cost information and roll it up through sub-recipes to the finished product. This gives teams a current, formula-based view of cost without asking them to rebuild the calculation in a spreadsheet every time an ingredient price or concentration changes.
The purpose is not to replace finance, budgeting, or pricing decisions. It is to provide a reliable product record that reflects the cost of what is actually in the formulation.
For example, the Uncountable coating demo uses held ingredient costs that roll up to $1.99 per kilogram for the finished formula. If the held unit cost of one component changes by 5.07 percent, the finished-product cost can reflect the impact through the connected formula structure. The point is not the specific numbers. It is that cost remains attached to the recipe, rather than living in a separate calculation that may not match the current formulation version.
Where-used analysis prevents portfolio surprises
Raw materials rarely belong to one product.
A resin, pigment, preservative, additive, flavor, surfactant, or active ingredient can appear across multiple formulas. When its cost, availability, specification, supplier approval, or regulatory status changes, the first question is often not, “What does this mean for this one product?”
It is, “Where else do we use it?”
A formulation-aware PLM should answer that question directly. The raw-material record should connect to every formula, sub-recipe, product variant, and approved product where it is used. Teams should be able to identify the scope of a change before they begin testing or notifications.
In Uncountable’s current demo, an acrylic resin appears in 38 products. The useful proof point is not the number alone. It is the fact that the relationship is held as structured data. A team can see the affected portfolio from the ingredient record rather than opening individual BOMs or asking every product owner to check local files.
That becomes critical when a supplier discontinues a material or a new restriction affects an ingredient. Without where-used relationships, the organization begins with a manual search. With them, it can start with an accurate impact scope and make more deliberate decisions about testing, reformulation, customer communication, and controlled change.
Keep R&D evidence connected to PLM
A formulation does not stop being relevant when it moves from the laboratory into product lifecycle management.
R&D needs access to the experiments, observations, process conditions, and test results that explain why a formula was developed in a particular way. Quality needs to know which formulation revision and specification applied when a test result falls outside its expected range. Manufacturing needs the approved formula, process requirements, and work instructions required to make the product consistently.
Those records should not become three disconnected versions of the same product.
A formulation-native platform keeps the development, quality, and lifecycle context connected. It allows teams to manage the approved formula and BOM while retaining the experimental and quality evidence behind the version in use. That creates a more reliable handoff from lab to plant and makes future reformulation, root-cause analysis, and audit preparation less dependent on institutional memory.
Uncountable’s PLM connects formulations, bills of materials, test data, process parameters, documentation, revisions, and production context in one product record, helping R&D, quality, and manufacturing teams work from the same governed information.
Compare the right PLM categories
Different PLM categories can be appropriate for different product-development models. The goal is not to find a universally best system. It is to test whether the system represents the product you actually make.
A system can have an extensive feature list and still be a poor fit if its core product model does not reflect formulations. The practical question is whether people can do their daily work in the system without maintaining a separate, unofficial source of truth.
Test vendors with a real product
Do not begin with a generic feature checklist. Use a real formulation that reflects the complexity your teams manage.
Choose a product with a sub-recipe, a shared raw material, current costs, a recent revision, and supporting test evidence. Then ask the vendor to demonstrate how the system handles the questions that matter:
- Can it show the recipe, quantities, units, and ingredient relationships as structured data?
- Can it preserve a sub-recipe without flattening its composition into the finished-product BOM?
- Can it roll cost through the recipe hierarchy to a meaningful finished-product value?
- Can it identify every other product that uses a shared material?
- Can it show what changed between two product versions, why the change was made, and what evidence supported it?
- Can R&D, QC, and manufacturing see the appropriate parts of the same product record?
- Can the team assess a supplier, ingredient, or specification change without rebuilding the analysis in spreadsheets?
The best PLM demonstration is not a polished workflow designed for a generic product. It is a live test of whether the platform can represent the formula that your organization actually makes.
Choose a PLM that follows the product
For formulation manufacturers, PLM should not begin when R&D hands over a static recipe. It should carry the product forward with the formulation structure, evidence, specifications, costs, revisions, and relationships intact.
A flat BOM may be enough to list ingredients. It is not enough to manage a living formulation across product development, quality, scale-up, manufacturing, and change.
Choose a PLM that lets teams see the real product: the recipe, the hierarchy inside it, the evidence behind it, and the portfolio it affects when something changes.
.png)
.png)
.png)
