Manufacturers rarely describe their problem as a bill of materials problem. They describe it as purchasing buying the wrong quantities, production waiting for a component nobody ordered, inventory holding material that no current order needs, or a costing figure that the plant manager does not believe. These are usually the same problem observed from four different departments: the material structure cannot answer the question being asked of it.
A bill of materials is not documentation. It is the calculation model the rest of the system runs on. Purchasing, production planning, inventory and costing all read from it, and none of them can be more accurate than it is.
What a multi-level BOM actually describes
A multi-level bill of materials describes a finished item in terms of its components, and each of those components in terms of its own components, to whatever depth the product genuinely has. A subassembly appears twice in the structure: once as a component of its parent, and once as a parent of the materials that make it.
A single-level BOM answers one question: what is consumed directly to make this item. That is enough for a product assembled in one step from purchased parts. It is not enough the moment an intermediate item exists that is itself manufactured, because the material behind that intermediate item is now invisible to anyone planning the parent.
The multi-level structure closes that gap. Demand for the finished item can be resolved, in a single pass, into demand for every material at every level beneath it. That single pass is the reason the structure exists.
When a level is worth creating
Depth is not a virtue in itself. A level earns its place when the intermediate item needs an identity of its own — when it is stocked between operations, inspected and accepted separately, costed as a stage, sent out for job work, or sold as a spare. Each of those activities needs something to attach a quantity, a cost or a movement to, and that something is a level in the structure.
Levels created for other reasons add maintenance effort without adding capability. A structure that mirrors a drawing hierarchy or a departmental boundary, rather than the way material physically moves, produces a model that has to be reconciled against reality every time either one changes.
How demand becomes a material requirement
The structure only becomes useful when something drives it. In practice the sequence is:
- Demand arrives. A sales order, a forecast, or a production plan establishes how much of a finished item is required, and by when.
- The structure is exploded. The requirement is resolved down through every level, so each component and subassembly acquires its own gross requirement.
- Quantities are scaled. Component requirements follow the parent quantity, so planning for 40 units and planning for 400 are the same operation, not two different exercises.
- Requirements are netted. Gross requirements are reduced by what is genuinely available and what is genuinely already coming, leaving what actually has to be bought or made.
- Action is proposed. What remains becomes purchase or production demand, with the timing implied by the delivery commitment. Deciding what to do with that remainder, and whether the job can be released at all, is the subject of production planning and material requirement.
Step four is where the calculation most often gains or loses its usefulness, and it is worth being precise about.
Netting: why stock alone is the wrong number
Gross requirement minus stock on hand is an intuitive calculation and an unreliable one. Stock on hand describes only what is physically present at this moment. It says nothing about three quantities that change the answer:
- Material already on order. It is not in stock, but it is coming, and re-ordering it produces surplus that arrives in a batch nobody planned for.
- Material already committed. It is in stock, but another work order or another delivery commitment has a prior claim on it. Treating it as free creates a shortage in a different order.
- Material out for job work. It is neither in stock nor on order in the ordinary sense, but it is expected back, and its return date belongs in the availability picture. Keeping that quantity accountable while it is outside is the subject of job work and subcontracting.
A planning run that considers available stock together with pending quantities produces a more accurate net requirement than one that looks at stock alone. It may be lower, where valid incoming quantities already cover part of the demand, or higher, where apparent stock is already committed elsewhere. Either way the figure is closer to what the operation genuinely has to buy or make, and that accuracy is what eventually shows up in working capital.
Over-ordering caused by ignoring incoming quantities is rarely recognised as a planning error at the time. It is absorbed as inventory and surfaces months later as a slow-moving stock question, by which point the original cause is no longer obvious.
What inaccurate material structure costs, department by department
An inaccurate BOM does not fail loudly. It produces plausible numbers that are wrong, and each function absorbs the error in its own way.
| Function | What it reads from the structure | How the error appears |
|---|---|---|
| Purchasing | Net requirement and timing per material | Emergency purchases at unplanned prices, alongside surplus of materials that were over-derived |
| Production planning | Component availability before release | Work orders released that cannot be completed, and capacity committed to jobs that then stall |
| Inventory | What is genuinely committed and free | Physical stock that does not reconcile to system stock, and reservations nobody trusts |
| Costing | Expected material content of the item | Variance that cannot be interpreted, because the expectation itself was wrong |
The last row is the one that tends to be discovered last and matters most. Work-order costing compares what an item should have consumed with what it did consume. If the structure that defines should is inaccurate, the comparison produces a number, but the number carries no information. This is why material structure has to be settled before work-order costing and variance analysis can be relied on.
Revisions, and keeping history truthful
Products change. Components are substituted, quantities are corrected, suppliers change specification. A structure that cannot record change without rewriting the past creates a specific and damaging failure: last quarter's variance is recalculated against this quarter's structure, and becomes unexplainable.
Two requirements sit alongside each other:
- Treatment of open work must be explicit and controlled. Whether an open work order adopts a corrected revision, and at what point, depends on its status and on the governance the business applies to changes in flight. What matters is that the system makes its behaviour clear, rather than leaving it to be discovered after the fact.
- Completed work must stay tied to the structure it was actually made under. A closed work order costed against a superseded version should continue to show that version, or its cost history stops being evidence.
What to evaluate when selecting an ERP for multi-level BOM management
Most systems will demonstrate a bill of materials. The questions that separate them are about what happens after the demonstration. They sit inside a wider decision, covered in the ERP selection and evaluation guide.
- Depth without special cases. Does the structure support assemblies, subassemblies and raw materials at the depth the product actually has, or does it become awkward past a certain level?
- One-pass explosion. Does a single work order derive requirements across all levels, or does each level need to be planned as a separate exercise?
- Netting inputs. Does the planning calculation consider available stock and pending quantities, or only physical stock?
- Availability before release. Is a shortage visible before a work order is released to the floor, or discovered by the operator who needs the part?
- Revision behaviour. What happens to open work orders when a BOM changes, and what happens to closed ones?
- Costing continuity. Does the same structure that drives planning also drive expected cost, or are they maintained separately and reconciled by hand?
- No second system. Is the requirement calculation part of the ERP, or does it depend on an exported spreadsheet that immediately begins to age?
How exactllyERP supports material structure and multi-level BOM
In exactllyERP, multi-level BOM is defined with parent-child relationships, component quantities, and routing steps per operation. The structure supports assemblies, subassemblies and raw material components in depth, so an intermediate item that is stocked, inspected or subcontracted has somewhere to exist.
Work orders are raised against the BOM. Quantity is scaled automatically and component requirements are exploded across all levels, so material requirements are derived from the work order itself rather than from a separate MRP spreadsheet. Planning can take available stock and pending quantities into account, which is what turns a gross material requirement into an actionable procurement requirement. Material availability is checked at work order release, so shortages are shown before production starts rather than discovered during it.
Changes to the BOM propagate to open work orders that reference it, while BOM revisions are versioned so historical work orders remain linked to the version used at the time. Production demand itself can originate from sales orders: planned production quantities are derived from open sales orders and delivery dates, which is what connects a delivery commitment to the material behind it.
Routing and operation sequences are maintained alongside the structure, and the same work order that consumes material also accumulates cost. Those are separate subjects with their own requirements: what each operation needs by way of machine, process and time is covered in capacity, routing and process time, and the cost side in work-order costing.
This page describes capability, not configuration. How deep a structure should go, which intermediate items deserve their own level, and how planning parameters should be set are implementation decisions that depend on the product and the plant. They are worth settling deliberately rather than inheriting from a template.
Common questions
What is the difference between a single-level and a multi-level BOM?
A single-level BOM lists only the components consumed directly by one parent item. A multi-level BOM also describes how those components are themselves built, so a subassembly appears both as a component of its parent and as a parent of its own components. The practical difference is that a multi-level structure can be exploded in one pass to give the full material requirement for a finished item, including every intermediate stage, rather than requiring each level to be planned separately.
How many levels should a bill of materials have?
As many as the operation genuinely has, and no more. A level is worth creating when the intermediate item is stocked, inspected, costed, sold, or subcontracted in its own right, because each of those activities needs something to attach to. Levels created only to mirror an organisation chart or a drawing hierarchy add maintenance effort without giving planning or costing anything new to work with.
Why must material planning consider pending quantities as well as stock on hand?
Stock on hand describes only what is physically available now. Quantities already on order, already allocated to other production, or already expected from an open job work movement change what is genuinely free to use. Planning that looks only at physical stock will re-order material that is already coming, and will treat committed material as available. Both errors are expensive, and both are invisible until the shortage or the surplus appears.
What happens to work orders already in progress when a BOM is changed?
That depends on how the system versions the structure. In exactllyERP, changes to the BOM propagate to open work orders that reference it, while BOM revisions are versioned so historical work orders remain linked to the version used at the time. This matters for costing as much as for production: if history silently adopts today's structure, past variance can no longer be explained.
Does multi-level BOM management require a separate MRP system?
It should not. If the structure lives in the ERP, the requirement calculation belongs there too, because it needs current stock, pending quantities and open demand at the same moment. In exactllyERP, material requirements are derived automatically from the work order, without a separate MRP spreadsheet. A structure maintained in one system and exploded in another is the most common source of requirements that nobody trusts.