What Is a Bill of Materials? Plain-English Guide

What is a bill of materials? A bill of materials (BOM) is the complete, structured list of every component, raw material, sub-assembly and quantity required to build one unit of a finished product, together with the instructions for assembling it. Think of it as the recipe for what you make: if a recipe tells a cook the exact ingredients and amounts for one cake, a BOM tells your production, purchasing and stock teams exactly what goes into one of your products, and how much.

It sounds simple, and at the smallest scale it is. But the moment you build anything with more than a handful of parts, or you make several variants of the same product, the bill of materials stops being a note in someone’s head and becomes the single document that purchasing, production, costing and inventory all depend on. Get it right and every downstream job runs clean. Get it wrong, or leave it living in one person’s memory, and you get shortages, over-ordering, mis-priced quotes and half-built products waiting on a missing part.

Key Takeaways

A BOM is the recipe for one finished product — every part, every quantity, and how it all goes together, in one structured list.
It is not just a parts list. A proper BOM includes quantities, units of measure, part numbers, and often the assembly sequence and where each part is used.
BOMs come in levels. A single-level BOM lists direct components; a multi-level BOM shows sub-assemblies broken down into their own parts, like a family tree of your product.
Different departments need different BOM views — engineering, manufacturing, purchasing and sales each read the same product differently.
An accurate BOM drives purchasing, costing and stock. It tells you what to buy, what a build actually costs, and what to deduct from inventory when a job runs.
The BOM breaks first when it lives in spreadsheets that don’t sync with your stock, your orders or your shop floor.

What a Bill of Materials Actually Contains

A useful BOM is more than a list of part names. At minimum, each line typically carries:

Part number or SKU — the unique identifier for the component, so there’s no ambiguity about which washer or which grade of steel.
Part name and description — the human-readable label.
Quantity — how many of that component go into one finished unit.
Unit of measure — each, metres, kilograms, litres. This is where a lot of BOMs quietly go wrong: buying in one unit and consuming in another.
Reference or level — whether the part is a raw material, a purchased component or a sub-assembly you build yourself.

Better BOMs go further and include the assembly sequence, procurement type (make or buy), and notes tying a component to a specific step in production. The richer the BOM, the less tribal knowledge your build depends on.

The Different Types of BOM (and Why the Type Matters)

Not every BOM looks the same, because different teams need to see the same product through different lenses.

Single-level BOM. A flat list of all the components that go directly into the finished product. Simple, fast to read, but it hides the structure — you can’t see which parts belong to which sub-assembly.

Multi-level BOM. A hierarchy. The finished product is broken into sub-assemblies, and each sub-assembly is broken into its own parts, down to raw materials. This is the “family tree” view, and it’s essential once you build anything you assemble in stages.

Engineering BOM (EBOM). How the design team defines the product — organised the way it was designed.

Manufacturing BOM (MBOM). How the product is actually built on the floor, including the consumables, packaging and sequencing that the engineering view often leaves out.

The gap between an EBOM and an MBOM is where a lot of manufacturers lose time. One production supervisor told us their engineering drawings never listed the adhesives, tape and packaging the line actually consumed, so those items were never on any purchase forecast and always ran short at month-end.

Why an Accurate BOM Matters More Than People Think

The BOM is quiet infrastructure. Nobody notices it when it’s right. When it’s wrong, everything downstream inherits the error.

Purchasing. Your BOM, multiplied by your production plan, is your buy list. If a quantity is off by one, or a unit of measure is wrong, you either over-order (cash tied up in stock you don’t need) or under-order (a job stops dead waiting on a £4 part).

Costing. A build’s material cost is the sum of its BOM lines at current prices. If the BOM is incomplete, every quote you send is quietly under-priced. This is where BOM accuracy connects directly to job costing — you cannot cost a job you cannot itemise.

Inventory. When a works order runs, an accurate BOM tells the system exactly what to deduct from stock. Without it, your stock figures drift from reality until a physical count forces a painful reconciliation.

Production. The BOM feeds the works order — the document that tells the floor to build a specific quantity of a specific product. A wrong BOM means a wrong works order means a wrong build.

Here’s a £-framing operators recognise. A wholesaler-turned-assembler we spoke to described the same failure every quarter: a sub-assembly’s BOM listed four fixings when the real build used six. Small error, tiny part. But across a production run of a few hundred units, it meant hundreds of missing fixings, an emergency courier order, and a line standing idle for half a day. The part cost pennies. The stoppage cost a shift.

Where BOMs Break in the Real World

Almost every growing manufacturer starts with the BOM in a spreadsheet, and for a while that’s fine. The break happens at a predictable point: when the spreadsheet stops talking to everything else.

The classic failure pattern looks like this. The BOM lives in one workbook. Stock levels live in another. Orders come in through email and a third system. Someone updates a component on the design side, but the purchasing sheet is a separate copy that nobody re-syncs. Now you have two versions of the truth, and the floor is building from whichever one they happened to print.

Operators tell us the symptom is always the same: the numbers stop agreeing. What the BOM says you need, what the stock sheet says you have, and what’s physically on the shelf all tell three different stories.

The spreadsheet isn’t the villain. It’s just a tool that was never built to be a shared, live source of truth across purchasing, production and stock at the same time. It has no concept of “when this BOM changes, update the buy list,” or “when this works order completes, deduct these components from inventory.” Those links have to be made by a human, every time, and humans in busy workshops forget.

From a BOM to a Working System

A bill of materials is only as useful as the things connected to it. On its own it’s a document. Wired into your operations, it becomes the engine that drives purchasing, costing, stock deduction and production scheduling automatically.

That’s the difference between having BOMs and running on them. When your BOM is connected:

Raising a works order automatically checks component availability against live stock.
A shortage flags before the job starts, not halfway through.
Completing a build deducts the right components from inventory without anyone re-keying anything.
Your material cost per unit updates as component prices change, so quotes stay honest.

This is the territory the bill of materials software buyer’s guide covers in depth — how to choose the system that turns your BOMs from static lists into live operational logic.

Build, Buy, or Own the System Around Your BOM

If you make one or two simple products, a well-kept spreadsheet BOM is genuinely fine. Don’t over-engineer it. The honest advice is to stay lightweight until the spreadsheet visibly starts costing you time or money.

Once you have multiple products, variants, multi-level assemblies, or a purchasing team that needs the buy list to be right the first time, you’ve outgrown the spreadsheet. At that point you have three routes. You can buy a full ERP, which will handle BOMs beautifully but arrives with a hundred modules you don’t need, a long implementation, and a price tag to match. You can keep patching spreadsheets and absorb the leaks. Or you can run one operations system shaped around how you actually build — where the BOM, stock, orders and production live in one place and stay in sync, and you own it.

That middle path is the one most growing manufacturers are missing. Not because it doesn’t exist, but because the market pushes them to jump straight from spreadsheets to enterprise software, skipping the practical layer in between.

The right question isn’t “which BOM software is best.” It’s “what would it take for our BOMs, our stock and our shop floor to finally agree with each other?” Answer that, and the tool choice becomes obvious.