There’s a recurring argument in manufacturing companies that looks like a personality clash and isn’t. Engineering says the BOM is correct. Production says it’s missing half of what they need. Both are right, because they’re describing different documents that happen to share a name.

Two Documents, Two Purposes

The engineering BOM describes the product as designed. It’s organised by function and assembly logic, it lists what makes the product work, and it’s owned by the people responsible for it working. It answers the question: what is this thing?

The manufacturing BOM describes the product as built. It’s organised by the sequence of operations, it includes everything consumed in production, and it’s owned by the people responsible for making it. It answers a different question: what do we need, in what order, at which station?

The MBOM is almost always the longer document, and the gap between them is where production problems live.

What The EBOM Leaves Out

Consumables. Adhesives, solvents, lubricants, welding consumables, cleaning agents. Engineering specifies a bonded joint; production needs to know how much adhesive, from which supplier, with what shelf life.

Packaging. Cartons, inserts, labels, pallets, stretch wrap. Almost never in the EBOM, always required, and a shortage stops shipment just as effectively as a missing component.

Process scrap. The EBOM lists one metre of material because the part is one metre. Production cuts from a stock length and generates offcuts. Without a yield allowance, every MRP run under-orders.

Intermediate stages. Engineering sees a finished assembly. Production may build three sub-assemblies at different stations on different days, each needing its own record.

Tooling and fixtures. Not consumed, but required, and their absence stops the job as surely as a missing part.

Two Failure Modes

Running production off the EBOM. Requirements come out short on everything the EBOM doesn’t list, and production compensates with informal stock and last-minute purchases. Everyone adapts, nobody records the workaround, and the BOM stays permanently wrong.

Maintaining them entirely separately. Engineering approves a change to the EBOM and the MBOM is updated by whoever notices. Sometimes nobody notices. The two documents drift apart until they describe different products, and reconciling them becomes a project.

How to Link Them Properly

The MBOM should be derived from the EBOM, not written independently. Every EBOM item maps to one or more MBOM items, and the MBOM adds its own layer of manufacturing-specific content. The mapping is what matters: when an EBOM component changes, the system should be able to identify every MBOM line affected.

Change control has to span both. An engineering change request should trigger an MBOM review as a mandatory step, with a named owner and a completion date, before the change is considered released.

And someone needs to own the MBOM explicitly. In a surprising number of manufacturers, nobody does — it’s maintained collectively, which means it’s maintained by nobody in particular.

ticktick.ai maintains linked engineering and manufacturing BOMs, so an approved design change surfaces every affected production record automatically.