A bill of materials should answer a basic question: what is in this product?
For an assembled product, a flat list of parts and quantities can be enough. There are components, each has an identity, and the final product is made by bringing them together.
A formulation is different. It is not a collection of parts. It is a recipe, where every ingredient has a proportion, a function, a relationship to the other ingredients, and often a history of changes behind it.
That distinction matters because a flattened BOM can capture what was in a formula at one point in time. It cannot reliably hold how that formula behaves as a product record.
Why Is a Recipe Different From a Parts List?
A flat BOM gives you ingredients and quantities. It does not naturally preserve the fact that the quantities are proportions that must balance.
If a formulator changes one ingredient in a coating from 4% to 6%, something else may need to change. The recipe has to remain coherent. A BOM that treats every line as an unrelated part does not understand that relationship. It becomes a static snapshot that someone has to update and validate by hand.
The same issue appears when a formulation includes sub-recipes. A finished coating may contain a thickener and a defoamer that are themselves formulas, each with its own composition and held cost. Flattening those into one long ingredient list hides the structure of the product. It also makes it harder to understand where a change originated and what it affects.
A formulation-aware BOM retains the recipe hierarchy. It knows that the finished product contains sub-recipes, that those sub-recipes contain their own ingredients, and that the composition and cost need to roll upward.
For a closer explanation of the difference between formulation and discrete PLM, see Formulation PLM vs. Discrete PLM: Why a Recipe Isn’t a Bill of Parts.
What Does a Formulation-Aware BOM Keep?
The first thing it keeps is the formulation itself.
Ingredients are held as percentages or other relevant formulation units on the product record, so the BOM remains tied to the recipe it represents. When the formula changes, the BOM changes with it. Teams do not need to maintain one version in R&D and another version as a separate lifecycle document.
It also keeps the nesting that real products require.
A formulation-aware BOM can show a finished product, the sub-recipes inside it, and the ingredients inside those sub-recipes. This makes the structure visible without reducing the product to a flat list that nobody can interpret once the original formulator has moved on.
The same structure supports cost roll-up.
Uncountable holds unit costs on the relevant records and rolls them up to a cost per kilogram for the finished product. In the current coating demo, the finished formula rolls up to $1.99/kg. If a held input cost changes by 5.07%, the impact can be reflected in that product-level roll-up.
That is a record of cost, not a budgeting or margin-management tool. The purpose of the BOM is to preserve the current cost information attached to the composition, not to make pricing recommendations or run repricing scenarios.
Why Does Where-Used Matter?
Raw materials do not belong to one product.
A resin, pigment, preservative, or additive may appear across dozens of formulas. When its cost, availability, specification, or regulatory status changes, the first question is usually not “What does this mean for this one formula?”
It is “Where else do we use it?”
A formulation-aware BOM can answer that question because the raw material remains connected to every product that contains it. In the current demo, an acrylic resin is used across 38 products. That relationship is visible from the ingredient record, rather than requiring teams to search through individual BOMs or ask each product owner.
That becomes important when an ingredient needs to be changed across a portfolio. The work starts with an accurate list of affected products, then moves into the different formulation, quality, and lifecycle decisions each product requires.
A flat, per-product BOM can show that an ingredient is present in one formula. It cannot easily show the portfolio behind it.
Why Does Versioning Matter?
A BOM is only useful if people can trust that they are looking at the right version.
In many organizations, the working formula, the approved product definition, and the latest specification can drift apart because they are maintained in separate places. The records may all look valid. The problem only becomes visible when a quality issue, raw-material change, or customer question requires the team to establish which one was actually in force.
A formulation-aware BOM stays connected to the formulation and raw-material records it represents. Its revisions remain part of the product history, alongside the changes that created them.
That gives teams a clearer answer to basic questions: what changed, when did it change, which ingredients were affected, and which version of the product is current?
This is the role of a formulation-first Product Lifecycle platform. It keeps the BOM, formulation, specifications, and revision history connected as one product record, rather than asking teams to maintain several parallel versions.
Why Does the BOM Lead the PLM Conversation?
The BOM often leads a PLM conversation because it exposes whether the system understands the product itself.
If the product is an assembly, a conventional parts model may be the right fit. If the product is a formulation, the system needs to understand proportions, sub-recipes, raw materials, held costs, specifications, and revisions as connected parts of the same record.
Get that structure right and the downstream work becomes more reliable. Cost can roll up from the ingredients. A sub-recipe remains visible inside the finished product. A raw material can be traced across the portfolio. A change can carry its context forward.
Get it wrong and teams work around the system. The real recipe survives in informal files and specialist knowledge, while the official BOM becomes a simplified copy that has to be reconciled later.
The practical test is straightforward. Take a real formulation with at least one sub-recipe and a shared raw material. Ask the system to show how the cost rolls up, where the raw material is used, and which product revision is current.
If those answers require exports, separate documents, or manual reconstruction, the BOM is still flattened.
.png)
.png)
.png)
