Single Level vs Multi Level BOM Explained

The difference between a single level vs multi level BOM comes down to how deep the structure goes: a single level BOM lists only the direct components that go into one product, while a multi level BOM breaks every sub-assembly down through all of its own layers until it reaches raw materials. Neither is “better”. They answer different questions, and most real production environments need both.

If you build simple products from parts you buy in, a single level BOM is usually enough. The moment you start making parts that go into other parts — a welded frame that goes into a machine, a blended base that goes into a finished bottle — a single level view stops telling the whole story. That’s where multi level BOMs earn their keep, and where a lot of spreadsheet-run workshops quietly start losing accuracy.

Key Takeaways

A single level BOM shows one parent and its direct children only — one layer deep, nothing below.
A multi level BOM expands every sub-assembly into its own components, layer by layer, down to raw materials.
Sub-assemblies decide the structure. No sub-assemblies means a single level BOM is fine; sub-assemblies mean you almost certainly want multi level.
Costing and stock behave differently at each level: single level costs the immediate parts, multi level rolls cost up from the bottom.
You don’t pick one forever. The same product often has a multi level “engineering” view and a single level “shop floor” view for each stage.
Structure only helps if it’s connected to real stock, purchasing and works orders — a tidy BOM in a spreadsheet still can’t tell you what to buy.

What a Single Level BOM Actually Shows

A single level BOM is the flat list. One parent product at the top, and directly beneath it every component that goes into it — with quantities — and nothing more. If one of those components is itself something you make, the single level BOM doesn’t care. It just lists it as a line, the same as a bought-in screw.

Think of a wooden dining table built from four bought-in legs, one bought-in top and a bag of fixings. Its single level BOM is four items. Clean, obvious, easy to keep in a spreadsheet.

The strength here is clarity. For a single stage of assembly — one workstation, one job — a single level BOM is exactly what the person building it needs. No noise, no layers, just the parts for this step. Many businesses run their entire shop floor on single level BOMs, one per assembly stage, and never need anything deeper.

What a Multi Level BOM Adds

A multi level BOM keeps going. Where the single level version lists a sub-assembly as one line, the multi level version opens it up and shows what that sub-assembly is made of — and if those parts are themselves made, it opens those too. You end up with an indented tree: finished product at level 0, its sub-assemblies at level 1, their components at level 2, and so on down to raw materials.

Take a made-to-order machine. Level 0 is the machine. Level 1 might be a welded chassis, a control panel and a drive unit — three sub-assemblies you build yourself. Level 2 under the control panel is the wiring loom, the enclosure, the switches. A single level BOM of the machine would show three sub-assemblies and hide everything below. The multi level BOM shows the whole thing.

That’s the real value of multi level: it exposes dependencies. When you plan a works order, you can see every part at every depth, work out what to make versus buy, and spot the low-level component that’s about to run out before it stops a high-value build.

Sub-Assemblies: The Thing That Decides Which You Need

The honest rule of thumb: if your product has sub-assemblies, you want a multi level BOM. If it doesn’t, a single level BOM is enough. A sub-assembly is any part you build that then becomes a component of something else — a stage that has its own inputs, its own labour, and often its own stock on the shelf.

Sub-assemblies matter because they can exist independently. You might build a batch of wiring looms on Monday, put them into stock, and consume them into three different machines over the following fortnight. That loom needs its own BOM, its own stock record and its own works order — and the parent machine’s BOM needs to point at it rather than re-listing every wire.

Flatten a real sub-assembly into the parent and you lose the ability to track it. You can’t tell how many looms you have in stock, you can’t build them ahead, and your cost roll-up gets fuzzy. Keep it as its own level and everything downstream gets sharper.

Costing and Stock Behave Differently at Each Level

Structure isn’t just tidiness — it changes the numbers. In a single level BOM, cost is the sum of the direct components at that level, and a sub-assembly line carries whatever value you’ve assigned to it. In a multi level BOM, cost rolls up from the bottom: raw materials feed the cost of each sub-assembly, which feeds the cost of the parent. Change the price of a raw material four levels down and, if the structure is live, the finished product cost updates on its own.

The same split hits stock. Single level tells you what to consume for one build. Multi level lets you explode a demand for finished units all the way down into gross raw-material requirements — the basis of any real purchasing plan.

Here’s the £-cost of getting it wrong. A workshop we spoke to costed finished machines off a single level BOM with fixed sub-assembly values that hadn’t been touched in a year. Copper and steel had moved. Every quote was carrying an out-of-date sub-assembly cost, and nobody knew by how much until margins on a big job came in thin. A rolled-up multi level cost would have caught it the day the raw-material price changed.

When to Use Each (and Why It’s Often Both)

You rarely choose one structure for the whole business. The practical pattern:

Use a single level BOM for the shop-floor instruction at each stage — the picking list for that one job.
Use a multi level BOM for engineering, costing, and full planning — the complete tree.
Use both on the same product when it has sub-assemblies: a multi level master that explodes for planning, and a single level view per stage for the person actually building it.

Simple, single-stage products (a bought-in kit, a two-part assembly) genuinely don’t need the overhead of multi level structure. Forcing it on them just adds admin. Complex, multi-stage products almost always do. The mistake is picking a tool or a spreadsheet that only supports one and then bending your real process to fit it.

Where Spreadsheets Break

A single level BOM lives happily in a spreadsheet. A multi level BOM in a spreadsheet is where trouble starts. The tree structure, parents pointing at sub-assemblies pointing at parts, is exactly what a flat grid is bad at. People fake it with tabs, indentation and colour-coding, and it works until a shared component changes and you have to hunt every place it appears by hand.

The failure isn’t dramatic. It’s a relay price that got updated in one bundle’s tab but not the other three. It’s a sub-assembly quantity that’s right in engineering’s copy and wrong in the shop-floor copy. Small drifts, compounding quietly, until a costed quote or a works order is wrong and no one can say which layer introduced the error.

This is the ceiling: spreadsheets can hold a BOM, but they can’t keep it consistent across levels, roll cost up automatically, or explode a demand into a purchasing plan. For a deeper look at what a BOM is and the fields it should carry, see what is a bill of materials. When the spreadsheet starts fighting you, the options are laid out in bill of materials software, and how BOMs feed the shop floor sits in works order processing software.

Build, Buy, or Own the System

You’ve got three honest routes. Buy a dedicated BOM or MRP tool: good if its model of sub-assemblies and costing matches how you actually build, painful if it doesn’t and you end up reshaping your process around its assumptions. Keep the spreadsheet: fine while you’re single-level and simple, a slow leak once real sub-assemblies appear. Or own one system built around how you work, where the BOM structure, stock, purchasing and works orders are the same connected data rather than four copies that drift.

OpsMavix isn’t an ERP and isn’t a cheaper clone of a BOM package. It’s the right-sized middle: single level and multi level BOMs that live in one place, roll cost up from live prices, explode demand into what you need to buy, and stay in step with the parts you actually have on the shelf — a system you own, shaped to how you run.

The structure question — single or multi level — is really a question about your product, not your software. Get the structure right first, then make sure whatever holds it can keep every level honest.