Manufacturing Bill of Materials (MBOM): What It Is and How to Manage It
Key takeaways
A manufacturing bill of materials (MBOM) lists every part, material and subassembly needed to build a finished product, in the way your shop floor actually builds it.
The MBOM is different from the engineering BOM (EBOM). Engineering designs what the product is; manufacturing defines how it gets made, including packaging, consumables, scrap and build sequence.
Most manufacturers need a multi-level MBOM, where subassemblies have their own BOMs nested under the finished item.
An MBOM works best inside your ERP, where it drives material planning, costing and production orders from one source of truth.
Version control matters: when a component changes, a dated BOM version keeps planning, costing and the shop floor in sync.
What is a Manufacturing Bill of Materials?
A manufacturing bill of materials (MBOM) is the complete list of parts, raw materials, subassemblies and quantities needed to produce one unit of a finished product. It reflects how the product is actually built on your shop floor, not just how it was designed.
Think of it as the recipe your production team follows. A recipe doesn't just list ingredients. It tells you how much of each to use, which ones get combined first, and what happens at each step. An MBOM does the same for a manufactured product.
Your MBOM feeds almost every operational decision you make:
Purchasing uses it to know which raw materials to buy and when.
Production planning uses it to calculate material requirements for every order.
Costing uses it to roll up the standard cost of each finished item.
The shop floor uses it to pick the right components for each job.
When the MBOM is wrong, every one of those processes inherits the error. That's why getting it right, and keeping it right, is one of the highest-value things a manufacturer can do.
MBOM vs. EBOM: What's the Difference?
The engineering BOM describes what the product is. The manufacturing BOM describes how you build it. Both list the same core parts, but they're organized for different people and different jobs.
The engineering bill of materials (EBOM) is created by your design team, usually in CAD or PLM software. It groups parts by function and reflects the product as designed. It rarely includes things like packaging, labels, adhesives or the extra material lost to cutting and trimming.
The manufacturing bill of materials (MBOM) takes the EBOM and restructures it for production. Parts get grouped into the subassemblies your shop actually builds, in the order it builds them.
Manufacturing adds everything needed to ship a finished unit: packaging, consumables, scrap allowances and the units of measure your purchasing team buys in.
A simple example: your EBOM for an office chair lists a seat, a base, five casters and a gas cylinder. Your MBOM groups the base, casters and cylinder into a "base assembly" built at one workstation, adds the box and foam inserts, and allows extra fabric for cutting waste.
The gap between the two is where costing errors and shortages tend to hide. If purchasing plans from the EBOM, you'll never order the boxes.
What Goes Into a Manufacturing BOM
Every line on an MBOM answers the same question: what does the shop need, and how much of it, to make one unit of the parent item? A complete MBOM usually includes:
Item number and description for every component, matching your item master exactly.
Quantity per parent, in the unit of measure the shop consumes it in.
Unit of measure, with conversions where you buy in one unit and consume in another (for example, buying steel by the sheet and consuming it by the square foot).
Scrap allowance, the extra material you expect to lose during production.
Subassemblies, which point to their own BOMs.
Packaging, labels and consumables that engineering may never have listed.
The operation that consumes each component, so materials arrive at the right workstation at the right step.
Single-level vs. Multi-Level Bills of Materials
A single-level BOM lists only the direct components of one item. It's simple, but it hides everything below the first layer.
A multi-level bill of materials shows the full product structure. The finished item sits at the top, its subassemblies sit one level down, and each subassembly's own components sit below that. A bicycle might have a front-wheel subassembly, which itself has a rim, spokes and a hub.
Most manufacturers need multi-level BOMs because that's how they actually plan. When a sales order comes in for 100 bicycles, the system needs to know it must also schedule 100 front wheels, and, at 36 spokes per wheel, buy 3,600 spokes to build them.
Phantom Subassemblies
Sometimes a group of components is easier to manage as a unit even though you never build or stock it separately. A fastener kit or wiring harness that goes straight into the parent item is a good example. Many ERPs handle this with a phantom BOM: a grouping that organizes the structure but passes its components straight through to the parent order, with no separate production order or inventory.
Routings: the Other Half of the Manufacturing Bill of Materials
A BOM tells you what materials you need. A routing tells you what operations happen, in what order, at which work centers and for how long. Together they define how a product is made.
Linking BOM lines to routing operations is what makes your plan realistic. Components arrive at the workstation that consumes them, and labor and machine time roll into product cost alongside materials.
How to Manage Manufacturing BOM's in Your ERP
Spreadsheets work for a handful of products. Once you have dozens of items, shared subassemblies and frequent engineering changes, the MBOM needs to live in your ERP, where planning, purchasing and costing all read from the same record.
Here's how that works in practice, using Microsoft Dynamics 365 Business Central as an example.
Production BOMs and Certification
In Business Central, the MBOM is called a production BOM. Each line specifies whether it's an item or another production BOM, the quantity per parent, and an optional scrap percentage. When you create a production order, the production BOM drives the material requirements for that order.
A production BOM moves through statuses: you build it as New or Under Development, then set it to Certified when it's ready. Microsoft recommends certifying BOMs before using them in production or planning, which keeps half-finished structures out of live orders.
Multi-level and Phantom BOMs
A production BOM line can point to an item that has its own production BOM, which is how Business Central builds multi-level structures. You can also add a phantom production BOM to a line. When the system calculates material requirements, it explodes the phantom's components directly onto the parent production order, with no separate subassembly order or inventory.
Versions for Engineering Changes
When a component is replaced, or a customer needs a special variant, you create a new production BOM version with a starting date. Each version stays valid until the next one starts, so planning and costing always use the right structure for the right date. A built-in comparison page shows quantities across every version side by side.
Routing Links and Costing
A routing link code on a BOM line ties that component to a specific operation in the item's routing, so materials are consumed at the right step. For standard-cost items, Business Central can roll component and resource costs up through the BOM to calculate the finished item's standard cost.
Common MBOM mistakes (and how to avoid them)
Most BOM problems don't come from complex products. They come from small gaps that compound across every order.
Planning from the engineering BOM. If purchasing and production work from the EBOM, packaging and consumables never get ordered. Keep a separate MBOM that operations owns.
Ignoring scrap. A BOM that assumes zero waste understates material needs and product cost. Set realistic scrap percentages and review them against actual consumption.
Unit of measure mismatches. Buying fabric by the roll and consuming it by the yard without a clean conversion creates shortages and inventory errors. Define conversions on the item, not in someone's head.
Editing live BOMs instead of versioning them. Overwriting a BOM in place loses the history and can change open orders mid-production. Create a dated version instead.
Letting BOMs and routings drift apart. When a new operation is added but the BOM still consumes materials at the old step, the shop floor works around the system. Review both together whenever a process changes.
No clear owner. When engineering, purchasing and production can all edit the MBOM, nobody is accountable for its accuracy. Assign ownership and a simple change process.
A quick way to find gaps: compare last quarter's actual material consumption against what your BOMs say you should have used. Large variances point straight to the BOMs that need attention.
Comments