BOM (Bill of Materials)

What it is

For a simple product, a BOM is a short list: this many metres of fabric, this many buttons, this much thread and one label per garment. For anything assembled in stages it becomes a tree — a multi-level BOM — where a finished good is made of sub-assemblies that each have their own list of parts. Each line records the item, the unit, the quantity per finished unit and, in a good system, the expected wastage.

In an ERP the BOM is master data, not a document. It lives against the product, carries a version so that changes are traceable, and is read automatically by material planning, production orders, costing and purchasing. When a style changes from a 5-button to a 4-button front, the BOM changes once and every downstream calculation follows.

Why it matters for a growing business

Without a maintained BOM, material requirements are estimated by experience: the production manager knows roughly what a 10,000-piece order needs, and purchasing orders a little extra to be safe. That works until the number of styles, sizes and colourways grows, at which point either stock piles up or the line stops waiting for a component nobody counted.

A BOM turns that experience into a rule the system can apply to any order size. It makes costing honest — the material cost of a product is the sum of its BOM lines at current prices — and it makes wastage visible, because actual consumption can be compared to what the BOM said it should be. For garments exporters, buyers increasingly expect exactly this kind of consumption record.

How AutoProbaho uses it

In the manufacturing and garments ERPs AutoProbaho builds, the BOM is the link between sales orders and the shop floor: an order for a style and quantity explodes into material requirements, drives purchase suggestions through MRP, and becomes the basis for issue-to-production and consumption variance reports. BOMs are versioned, importable from Excel and editable by the people who actually know the product.