What a bill of materials is
A bill of materials (BOM) is the structured list of everything needed to make one unit of a product — every raw material, component, sub-assembly and bought-out part, each with its quantity per unit and unit of measure, arranged parent-to-child in levels. It is the manufacturing recipe: the item at the top is what the customer ordered, and everything beneath it is what the factory must make or buy to deliver it.
In a manufacturing ERP, the BOM is not a document that sits in a drawing folder — it is a live master record that other modules read. Explode it against a released order and it tells planning what to make, purchasing what to buy, stores what to issue and costing what the product should cost. That is why BOM accuracy is one of the highest-leverage disciplines in the whole system: every downstream number — the material plan, the purchase requisitions, the work orders, the standard cost — inherits whatever the BOM says.
The anatomy of a BOM line
Every BOM is a set of parent–child relationships, and each child line carries the same essential fields:
- Parent item — the assembly or finished item this line belongs to, drawn from the item master.
- Child item — the material, component or sub-assembly consumed, also a master item with its own type, group and category.
- Quantity per and UOM — how much of the child goes into one unit of the parent, in the child's inventory unit of measure.
- Level — where the line sits in the structure, which decides the order in which the explosion walks the tree.
- Make-or-buy character — inherited from the item master, it decides whether the explosion creates production demand or purchase demand for the line.
Because every child is an item-master record, the BOM automatically inherits the master's stock levels, lead time and cost — which is exactly what lets MRP net requirements against stock and lets costing roll prices up the tree without re-entering anything.
Single-level vs multi-level BOMs
A single-level BOM lists only the immediate children of one parent — one level deep, useful for a simple assembly or a kit. A multi-level BOM nests BOMs inside BOMs: the finished item's children include sub-assemblies, each sub-assembly has its own BOM, and the structure continues down to raw material. Most real engineering products are multi-level, and the difference matters operationally, not just visually.
| Aspect | Single-level BOM | Multi-level BOM |
|---|---|---|
| Structure | Parent → immediate children only | Parent → sub-assemblies → components → raw material |
| Best for | Kits, simple assemblies, packing lists | Engineered and fabricated products with sub-assemblies |
| Explosion | One pass — quantities multiply once | Level by level — quantities cascade through the tree |
| Work orders | One order makes the parent | Each make-level can carry its own work order and route |
| Costing | Sum of child costs | Costs roll up level by level to the finished item |
| Where stock helps | Rarely — everything is bought for the kit | A sub-assembly already in stock stops the explosion below it |
The multi-level tree is also what makes intermediate stock useful. If the explosion finds fifty of a level-1 sub-assembly already on the shelf, it does not need to plan the components below those fifty — netting happens at every level, not just at the top. A flat list cannot express that; a tree can.
BOM vs BOR — materials vs resources
The BOM answers what goes into the product. Its sibling, the bill of resources (BOR), answers what it takes to make it — the machines, labour and tooling each process step occupies, drawn from a resource master that groups and categorises them. The third piece is the process or route sheet, which fixes the sequence of operations the item travels through.
Together they cover the three planning questions: material to consume (BOM), capacity to occupy (BOR) and operations in sequence (route). Fast ERP maintains BOM and BOR on the same structure and pairs them with process sheets in the Production & Planning module, so exploding an order plans material and resources in the same pass — the same spine that Gantt-based machine loading reads when scheduling the shop.
The BOM against the sales order
A subtle but important distinction separates the master BOM — the standard structure held against the item — from the BOM against the order. In Fast ERP, when an Order Acceptance is released, the BOM is exploded against that specific order, so the requirement, the plan and the eventual work orders all carry the order's identity. Job-shop and engineer-to-order work often needs exactly this: the same item made for two customers may differ in a fitting or a finish, and the order-specific BOM captures the variant without corrupting the master.
This is also what makes end-to-end traceability real. A customer audit can start at the invoice and walk back through dispatch, work orders and material issues to the BOM revision the order was built against — because every downstream document references the order the BOM was exploded for.
What the BOM drives downstream
The reason BOM discipline pays for itself is the number of consumers reading it:
BOM costing — what the product should cost
Because every child line references an item-master cost, the BOM doubles as the product's cost model. A BOM costing report multiplies quantity-per by cost at each line, rolls the totals up level by level, and lands on a should-cost for the finished item. Put next to the quoted price, it shows margin before the first chip is cut; put next to actual process costs after production, it shows where reality drifted from the plan.
An illustrative example: a fabricated trolley with a frame sub-assembly, four castors and hardware. The frame's own BOM carries tube, plate and paint. Costing rolls tube-and-plate up into the frame, the frame up into the trolley, and adds the bought-out castors — one report, whole structure, no spreadsheet. When steel prices move, updating the raw-material cost on the item master re-prices every BOM that consumes it.
Want to see your own product structure as a live BOM tree?
Bring one drawing and a parts list — we will build the multi-level BOM, explode it against a sample order and show the plan, requisitions and costing it generates, in one 30-minute session.
Keeping the BOM honest: engineering change
A BOM is only as good as its revision control. Products change — a supplier part is substituted, a wall thickness is revised, a customer asks for a different finish — and if those changes are made by silently editing the live BOM, history is destroyed: nobody can say which structure last month's orders were built against.
The answer is the ECN — engineering change note. A change is raised as a document in its own right, describing what changes and why; it passes through change-document approval; and only on release does it take effect on the structure. Past orders keep their built-against revision, open orders can be assessed for impact, and purchasing, production and quality all receive one controlled signal instead of discovering the change at the machine. The full workflow — including changes raised against development orders and a change dashboard for tracking — is covered in the engineering change management guide.
How Fast ERP handles the BOM
Fast ERP treats the BOM as the hinge between sales and the shop floor, inside the Production & Planning module:
- Multi-level BOM and BOR entry on one structure, with items drawn from the shared item master and resources from the resource master.
- BOM tree view and level report — the whole structure visualised parent-to-child, and a level-wise listing for planning and audit.
- BOM against the Order Acceptance — order-specific explosion that drives the material plan, PR-against-BOM and work orders for that order.
- BOM costing and structural BOM reports — should-cost roll-ups and structure listings straight off the live data.
- ECN workflow — add, approve and release engineering changes with a change dashboard, so the structure only moves under control.
Because the BOM lives in the same database as stock, purchase and quality, its explosion is not an export to another tool — it is the direct source of the plans, requisitions and work orders those modules act on. That is the practical meaning of an integrated ERP, and it is the pattern proven across deployments like Nikhtish Engineering and Micro India.
Frequently asked questions
What is a bill of materials (BOM)?
A bill of materials is the structured list of everything needed to make one unit of a product — every raw material, component, sub-assembly and bought-out part, each with its quantity per unit and unit of measure, arranged parent-to-child in levels. In an ERP the BOM is a live master record, not a document: exploding it against a released sales order tells planning what to make, purchasing what to buy, stores what to issue and costing what the product should cost.
What is the difference between a single-level and a multi-level BOM?
A single-level BOM lists only the immediate children of one parent item — one level deep. A multi-level BOM nests BOMs inside BOMs: the finished item's children include sub-assemblies, and each sub-assembly carries its own BOM, down to raw material. Multi-level structure matters because an ERP explodes it level by level — level 0 finished item, level 1 sub-assemblies, level 2 components and so on — so requirements, work orders and costs roll up correctly through the whole product structure.
What is the difference between a BOM and a BOR?
The BOM (bill of materials) lists the materials that go into the product; the BOR (bill of resources) lists the machines, labour and tooling required to make it, process by process. Together with the process/route sheet they answer the three production questions: what to consume (BOM), what capacity to occupy (BOR) and in what sequence of operations (route). Fast ERP maintains BOM and BOR together on the same structure, so exploding an order plans material and resources at the same time.
How does a BOM drive MRP and purchasing?
When a sales order is released, the ERP explodes its BOM level by level to calculate gross requirements for every component, then nets those against stock on hand and open purchase orders. What remains short becomes purchase requisitions — Fast ERP raises PR-against-BOM directly from the explosion — which are checked, approved and converted to purchase orders. The same explosion drives the raw-material and component plans, so buying and making both trace back to the order through the BOM.
How are BOM changes controlled in an ERP?
Through engineering change management. Instead of editing a live BOM silently, an ECN (engineering change note) is raised describing the change, routed through change-document approval, and only applied when the ECN is released. That keeps every past order traceable to the BOM revision it was actually built against, and gives purchasing, production and quality a single controlled signal that the structure has changed. In Fast ERP the ECN workflow and change dashboard sit directly alongside the BOM screens.