The bill of materials is the recipe for everything downstream. If it is wrong, planning, purchasing, costing and stock are all wrong in the same way.
What a bill of materials is
A bill of materials, or BOM, is the recipe for making one product. It lists every component and raw material that goes into it, with the quantity needed for one unit or one batch. In most ERPs, including Sundial's Manufacturing module, it can also list the operations that turn those materials into the finished item, and the workstations where each operation happens.
On the shop floor, the BOM is what tells people what to pick. In planning, it tells the system what to buy. In finance, it is the basis for the product's cost. That is why a mistake in a BOM spreads so widely: every department relies on the same recipe.
What goes into a good BOM
Take a simple example: an office desk made by Kestrel Workspace. Its BOM might contain:
- Materials: one desktop panel, one steel frame, four leg levellers, a set of screws and a cable tray, each with a quantity and a unit of measure.
- Operations: cutting and edging the panel, assembling the frame, final assembly and packing, each with a workstation and a time per unit.
- Scrap: the expected offcut from cutting the panel, so material consumption and cost are realistic.
- Quantity: whether the BOM is for one desk or a batch of ten.
Units of measure deserve care. If panels are bought by the sheet and used by the piece, the conversion must be set once on the item, not worked out by the person picking.
Single-level and multi-level BOMs
Most products are built from sub-assemblies. The desk's steel frame might itself be made in-house from tubes, brackets and welding consumables. In that case, the frame has its own BOM, and the desk's BOM simply lists the frame as one component.
This multi-level structure has real advantages. Each sub-assembly can be made in advance, stocked and used in several products. A change to the frame updates every product that uses it. And planning can work out the full requirement for raw materials by exploding the levels, down to the last screw.
Keep the levels meaningful. Create a sub-assembly only when it is actually built separately, stocked, sold as a spare or used in more than one product. A level that exists only on paper makes work orders more complicated without helping anyone.
Costing from the BOM
Because every material has a valuation rate and every operation has a time and a workstation rate, the BOM can calculate the cost of a product: materials, plus operating cost, plus scrap. Sundial lets you base the material cost on valuation rate, the latest purchase rate or a price list, depending on whether you want a standard cost or a current one.
That cost is only as good as the inputs. Review workstation rates and operation times at least yearly, and compare the BOM cost with the actual cost of completed work orders. A large gap means either the recipe or the shop floor is not matching reality.
Changing a BOM without chaos
Products change: a new supplier's part, a cheaper material, a design fix. Handle changes deliberately:
- Create a new version, do not edit the old one. Submitted BOMs are kept as a record. Make a copy, change it and set it as the default when it is ready.
- Decide what happens to open work orders. Orders already started usually finish on the old BOM. New orders pick up the new default.
- Replace components everywhere at once. When a component is replaced across many products, a BOM update tool can swap it in every BOM that uses it and recalculate costs.
- Use up old stock. Check how much of the outgoing component is on hand or on order before switching.
Keeping the BOM honest
The surest sign of a wrong BOM is the shop floor working around it: extra material issued every time, components substituted without a record, operators ignoring the listed times. When that happens, fix the BOM rather than accepting the workaround.
A simple check is to compare material issued to work orders with the quantities the BOM expected. Consistent differences point directly to the lines that need correcting.
Where to start
Begin with your highest-volume products. Get their BOMs right, including operations and scrap, before moving on. Agree who is allowed to create and approve BOM versions, usually someone in engineering or production with a review from costing.
We are building Sundial so an AI agent can compare actual consumption with BOMs and suggest corrections for a person to approve. To see multi-level BOMs on sample data, try the demo.





