A single-level BOM answers one question: what goes into this product? That’s enough when you buy every component ready to use. The moment you start making your own sub-assemblies, it stops being enough — and most manufacturers cross that line without ever formally deciding to.
What Changes With Multiple Levels
A multi-level BOM is a hierarchy. The finished product sits at the top. Below it are sub-assemblies, and below those are components, and possibly further sub-assemblies below those. A pump might break down into a motor assembly, a housing assembly, and a seal kit. The motor assembly has its own components and its own lead time. Each level is a real thing that gets built, counted, and costed.
This matters because planning now has to work backwards through the tree. If the seal kit takes twelve days to assemble and the finished pump takes three, you can’t start the pump build until the seal kit is done. Your material requirement dates for the seal kit components sit fifteen days before the customer promise date, not three. Get this wrong and you’ll be permanently late on products you thought had short lead times.
Phantom Assemblies
Not every sub-assembly needs stocking. If you build a wire harness and immediately install it in the same operation, it never sits on a shelf. Flag it as a phantom and the system passes requirements straight through to the components without creating an inventory record for something that exists for four minutes. Skipping this step is why some manufacturers have thousands of stock items with permanent zero balances.
Where The Cost Really Is
Multi-level structures let you roll up cost properly. The seal kit has a material cost and a labour cost. The pump inherits both, plus its own. Without the hierarchy, you’re either lumping all labour into a single overhead rate or ignoring it — and then wondering why some products are far less profitable than the model says.
It also lets you answer questions that flat BOMs can’t. Which products use this component? If a supplier discontinues a bearing, a multi-level structure tells you every finished good affected, three levels up. A flat list tells you nothing.
Common Pitfalls
Building the tree too deep is a real risk. Every level you add is a level someone has to maintain, count, and transact against. If a sub-assembly is never built independently, never stocked, and never sold as a spare, it probably doesn’t need to be its own level.
The opposite failure is equally common: keeping everything flat because the hierarchy feels like paperwork, then discovering you can’t plan lead times or trace a defect back to a sub-assembly batch.
A good rule — create a level when the item is stocked, sold separately, built on a different schedule, or needs its own traceability. Otherwise, don’t. ticktick.ai handles multi-level explosion and roll-up costing automatically, including phantom logic, so the structure reflects how you build rather than how the software prefers things.
