Engineering Bill of Materials vs Manufacturing BOM: What Changes Between Design and the Shop Floor

What an engineering bill of materials actually contains

The engineering bill of materials is the design view of the product. Wikipedia’s definition is blunt and useful: an EBOM is a bill of materials reflecting the product as designed by engineering, including substitute and alternate part numbers and parts contained in drawing notes. It usually falls out of CAD, or out of a spreadsheet that shadows CAD.

Structurally, it is organised the way the product is conceived — a machine grouped by function (drive assembly, control assembly, frame), a PCB assembly grouped by circuit block. The hierarchy expresses design intent, not build order.

What it reliably contains:

• Designed and purchased parts, with engineering part numbers
• Quantities per assembly
• Revision level and drawing references
• Material specifications, finishes, tolerances
• Alternates and substitutes the designer has approved

What it reliably leaves out:

• Consumables — adhesive, solder, flux, weld wire, thread lock, paint, cutting fluid
• Packaging, labels, manuals, desiccant
• Anything that exists only because of how you make it: jigs, fixtures, masking, test fixtures
• Sequence — what goes on before what
• Scrap and yield allowances
• Sub-assemblies that exist for production reasons only, such as a pre-wired loom

None of those omissions are mistakes. The engineer’s job is to define the product, not to define your factory. Arena’s definition draws the line the same way: the EBOM deals with how a product is designed, while the MBOM details what is needed to assemble it — and the two differ in structure as well as depth.

What the manufacturing BOM adds on top

The manufacturing BOM is the build view. The plain definition does the work: an MBOM contains all the parts and assemblies required to build a complete and shippable product, plus information about how those parts relate to each other. That last clause is the whole difference. The EBOM says what. The MBOM says what, in what order, with what else, on what equipment.

The same page notes the ISA-88 parallel, where the material list is only the formula part of a recipe — the recipe also carries the procedure and the equipment requirements. Worth stealing even if you make discrete parts: your MBOM is the formula, and it is not much use without the procedure next to it.

The additions, roughly in order of how often they get forgotten:

1. Consumables — glue, solder, fasteners bought by the kilo, abrasives, coolant, weld gas. Individually trivial, collectively a real line on the P&L, and invisible to stock control if they never enter a BOM.
2. Packaging and despatch materials — carton, insert, pallet, shrink wrap, label, manual. UK producers over the reporting thresholds have a hard reason to know these by material and weight: packaging EPR requires you to report the weight in kilograms of the individual materials for each packaging activity you carry out — aluminium, glass, paper or card, plastic, steel, wood — split out separately. If packaging sits on the MBOM at the right weights, that report is arithmetic. If it doesn’t, it’s a weekend.
3. Process sub-assemblies — the welded frame, the potted module, the pre-tested board. These are real stockable items on the floor and often do not exist in the design tree at all.
4. Scrap and yield allowances — the extra material you must buy because not every piece survives.
5. Routing links — which operation consumes which component, on which work centre, for how long.
6. Alternate parts as actually purchased — the supplier part number rather than the generic spec, with the second-source substitute your buyer really uses.
7. Phantom or transient items — things that exist for one step and are never stocked.

Engineering bill of materials vs manufacturing BOM at a glance

The last row is the one people miss. An MBOM has more reasons to change than an EBOM, so even a perfectly stable design produces a moving manufacturing list.

The handover: what actually happens at release

The transition has a name in bigger organisations — EBOM release, or engineering-to-manufacturing transfer — and a shape in smaller ones, usually “Dave gets sent a PDF”. Done properly, four things happen between the released design and the first works order:

1. Restructure. The functional tree becomes build stages. A “control assembly” in design might become three MBOM sub-assemblies, built at different benches on different days.
2. Enrich. Consumables, packaging, jigs and process items are added, each with a real consumption quantity, not a shrug.
3. Substitute. Generic specs become purchasable items: “M6×20 A2 cap screw” becomes a supplier code with a pack size and a lead time.
4. Allow. Scrap and yield factors are applied so the buy quantity reflects reality.

Each step is a translation, and translations lose things. The failure modes are equal and opposite: translate too loosely and the built product drifts from the design; translate too tightly and the MBOM is just the EBOM with a different filename, which means the floor goes on running from memory.

Worked example: a steel enclosure, EBOM to MBOM

Take a wall-mounted control enclosure. The design parts list is short.

EBOM — Enclosure ENC-400, Rev C

Seven lines. Now the manufacturing list for the same enclosure.

MBOM — ENC-400, build route FAB → WELD → PAINT → ASSY → PACK

Seven lines became twenty. Nothing was invented — every added line is something the business already buys and consumes. The only question is whether it is consumed on a list or silently.

The commercial consequence is straightforward. Quote from the EBOM and you have priced seven lines of a twenty-line product. Powder, gas, packaging, masking, cut allowance and the pallet all land in overhead, where they get spread evenly across jobs that use them very unevenly. That is not a rounding error on a product you make three hundred times a year, and it is exactly the leak that surfaces as “we’re busy but the margin isn’t there”.

Scrap allowances: why the MBOM asks for more than the drawing

This is the difference people argue about most, usually because it looks like the two lists contradict each other. They don’t — one is a specification, the other is a purchase plan.

ERP systems formalise it with distinct scrap types. SAP’s manufacturing training material separates them clearly: assembly scrap increases the order quantity of the assembly and therefore every component beneath it, component scrap increases the dependent requirement for one specific component, and operation scrap reduces the quantity carried into the next operation. Where both assembly and component scrap apply, they stack.

You do not need SAP to use the idea, just three questions answered per line:

• Does the component get damaged before it goes in? Component scrap — the gasket cut short, the connector crimped twice.
• Does the whole assembly fail sometimes? Assembly scrap — you start twenty to ship nineteen.
• Does one operation lose parts? Operation scrap — the paint line rejecting two in every hundred.

A single blended “add 10%” across everything is how businesses over-buy trivial parts and under-buy the expensive one at the same time. Recording actual losses per operation is the only way allowances stop being folklore — the argument for scrap and rework tracking as a routine rather than a project.

Why the two lists legitimately differ — and when a difference is a defect

Not every gap between EBOM and MBOM is a problem. The discipline is knowing which differences are meant to be there.

Legitimate differences:

• Extra lines for consumables, packaging and process materials
• Quantities inflated by scrap and yield
• A different hierarchy that follows build stages rather than function
• Supplier part numbers replacing generic specifications
• Process-only sub-assemblies with no design equivalent
• Items sequenced across operations rather than listed flat

Defects dressed up as legitimate differences:

• A component sitting on the MBOM at a superseded revision
• A part quietly substituted on the floor and never fed back to engineering
• A quantity that differs with no scrap rule to explain it
• A design change released weeks ago that has never reached the build list
• An MBOM line nobody can trace to an EBOM line or a process reason

The test is worth writing down: every difference should have a stated reason — consumable, packaging, process step, scrap allowance, approved substitute. If a line’s reason is “not sure”, it is a defect, and usually the one that produces the next wrong build.

What breaks when you keep only one of them

Most businesses that meet this problem are keeping one list and asking it to do two jobs. Both single-list strategies fail, differently.

If you keep only the engineering BOM, you under-buy and under-price. Purchasing orders exactly what the drawing says, so consumables get bought reactively when someone notices the glue has run out. Job costs exclude everything that isn’t a drawn part, so margin looks healthy at quote and thin at year-end. Works orders carry no sequence, so scheduling lives in a supervisor’s head. Packaging and consumable stock stays invisible until it is zero.

If you keep only the manufacturing BOM, you lose design control. There is no clean record of what the product is supposed to be, only what you happened to build last time. A floor-level substitution becomes permanent by default, and nobody can answer “which revision is this serial number?” when a warranty claim arrives. Regulated sectors turn that into a compliance failure; everywhere else it bites the day you want a second supplier or a second site and have nothing to hand them but tribal knowledge.

The pattern is the same either way: information living in someone’s memory rather than in a record works at ten units a month and fails somewhere between fifty and two hundred.

A quick sizing test. Do designs change after production starts? Do you buy consumables or packaging that appear on no parts list? Do you scrap material often enough that buy quantity differs from drawing quantity? Does the build run in stages, with part-built stock between them? Must you ever prove which revision a despatched unit used? None or one yes: a single accurate manufacturing BOM is enough. Two or three: add the missing lines before splitting anything. Four or five: you need both views, and you are already paying for not having them.

Keeping the two in step without buying a PLM

Full PLM systems exist to manage this handover, and for a business with hundreds of active part numbers and formal design control they earn their money. Most growing UK manufacturers are nowhere near that. The working minimum is smaller than the sales pitch suggests:

1. One product record, two views. The EBOM and MBOM hang off the same product, not two unrelated files. Every MBOM line either maps to an EBOM line or carries a reason code.
2. A release step that is an event, not an email. A revision is either released to manufacturing or it is not, with a date and a name attached.
3. A change flag that travels. When an EBOM line changes, the linked MBOM line is marked for review. It does not update itself — someone still decides whether the process changes — but it cannot be silently missed.
4. Effectivity, so a change is never retrospective. The record knows which revision each works order was built to.
5. Consumption at works-order issue. Issuing a job moves stock for every MBOM line, consumables included. Without this, the MBOM is documentation rather than control.

Points two and four open onto a discipline of their own — release states, change requests and orders, effectivity dates — and this page stops at the seam rather than working through it; that is bill of materials management. Depth is a different axis again: if the product tree runs more than two layers deep, the parent-child mechanics matter as much as the design-versus-build split.

What this looks like in a right-sized operations system

This is not really a documentation problem, it is a systems one. A spreadsheet holds an EBOM perfectly well. It cannot hold two linked views of the same product, flag one when the other changes, apply scrap rules at works-order issue and consume stock — because a spreadsheet has no events, only cells.

The other end of the market, full ERP with PLM bolted on, solves it completely and asks you to reshape the business around the software’s opinion of how design release should work. For a business too messy for spreadsheets but not ready for a full ERP, the middle option is an owned operations system built around your actual route: one product record with a design view and a build view linked line by line, revision effectivity, scrap allowances taken from recorded losses rather than a guess, and works orders that consume every line including the glue and the box.

FAQ

What is the difference between an engineering bill of materials and a manufacturing BOM?

The engineering bill of materials describes the product as designed — functional structure, drawn parts, revisions, exact quantities — and is owned by engineering. The manufacturing BOM describes it as built: restructured into build stages, with consumables, packaging, process sub-assemblies, supplier part numbers and scrap allowances added, each line tied to an operation. The MBOM is almost always the longer of the two, and the pair should never be identical.

Should the engineering BOM and manufacturing BOM have the same quantities?

No, and expecting them to is a common source of argument. The EBOM carries the quantity that ends up in the product; the MBOM carries the quantity you must issue to get there, inflated by component scrap, assembly scrap and operation losses — a gasket specified at 1.8 metres might be issued at 2.0 metres for cut waste. Every quantity difference should have a stated allowance behind it; an unexplained one is a data error, not a scrap rule.

Who owns the EBOM to MBOM handover in a small manufacturer?

In a business without a dedicated manufacturing engineer, the honest answer is usually “nobody, and that is the problem”. Name one person — often the production manager — as owner of the MBOM, with a standing rule that no design revision reaches the floor without passing through them. Ownership matters more than job title; what breaks the handover is diffuse responsibility, not a missing role.

Can we keep just one BOM if we are small?

Yes, if the design is stable, the build is one stage and nothing gets scrapped. Keep a single manufacturing BOM that includes consumables and packaging, and treat the drawing pack as the design record. The moment design changes start reaching the floor late, or you need to prove which revision a shipped unit was built to, you need two linked views rather than one list doing both jobs badly.

Sources

• Wikipedia — Engineering bill of materials — EBOM as the product as designed by engineering, including alternates and parts in drawing notes.
• Wikipedia — Manufacturing bill of materials — MBOM as all parts and assemblies required to build a complete, shippable product, plus the ISA-88 recipe parallel.
• Arena — What is an Engineering Bill of Materials (EBOM)? — EBOM as designed versus MBOM as assembled, differing in structure and depth.
• SAP Learning — Routing: Scrap — assembly scrap, component scrap and operation scrap, and how each changes BOM quantities.
• GOV.UK — How to collect your packaging data for extended producer responsibility — the requirement to report packaging weight in kilograms by individual material.