Most factories already have a bill of materials. It usually lives in a spreadsheet, it lists what goes into a product, and somebody updates it when a component changes. That is a parts list. It is useful for costing and almost useless for planning.
The difference matters the moment you try to answer a simple question: if we accept this order, can we build it?
What a planning BOM has to carry
To answer that question the structure has to hold more than names and quantities. It has to know how the product is actually made.
- Quantities per unit, with the wastage the process genuinely produces
- The processes each component passes through, in order
- Substitutes, so a shortage on one line does not stop the job
- Variants, so a size or finish change does not fork the whole record
- Sub-assemblies as their own structures, not flattened into the parent
Once those are in place the BOM stops being a reference document and starts being an input. Requirements can be calculated instead of estimated. Shortages surface before a job card opens rather than when a line stops.
Why flattening hurts later
It is tempting to flatten sub-assemblies into a single level. It makes the spreadsheet readable. It also means every change to a shared sub-assembly has to be found and repeated in every product that uses it, and it hides the stage where a shortage will actually bite.
Keeping the levels costs a little structure up front and saves the recurring work of reconciling records that were never meant to drift apart.
Where to start
Take one product that causes the most planning arguments. Model it properly: variants, processes, wastage, substitutes. Then run a real order through it and compare what the structure predicts against what the floor actually consumed. The gap is your roadmap.
