Most small manufacturers start their bill of materials in Excel, and there is nothing wrong with that at the beginning. A simple product with a handful of components fits comfortably in a spreadsheet. Someone lists the parts, adds the quantities, maybe links in a rough cost per unit. It works.
The trouble starts as the product line grows. More components. More variations. More people touching the file. A single BOM spreadsheet that once fit on one screen turns into a tangle of tabs, each one slightly different from the last, and nobody is fully sure which version reflects what actually gets built on the shop floor today.
This post looks at why Excel BOMs break down as a manufacturer grows, what a production-ready bill of materials system actually needs to do differently, and what small manufacturers should look for when they are ready to move on.
Why Excel works for a BOM at first
A bill of materials is fundamentally a list: which components go into a finished product, in what quantities, and at what cost. Excel handles lists well, so it makes sense that most manufacturing bill of materials work starts there. A founder or production lead builds the first BOM by hand, and it does exactly what is needed for a small number of products with a small number of components each.
The spreadsheet stays manageable as long as three things stay true. The product line stays small. Only one or two people ever edit the file. And the BOM rarely needs to connect to anything else, like current stock levels or actual production costs, because someone can check those manually without much effort.
Where Excel BOMs actually break down
Growth breaks all three of those conditions, usually around the same time.
Version control becomes the first casualty. Once more than one person needs to update a BOM, keeping a single source of truth in a spreadsheet gets genuinely difficult. Someone updates a component quantity on their local copy. Someone else makes a different change to a copy they saved from last week. By the time these get reconciled, if they get reconciled at all, nobody is fully confident which version is the one actually being used on the production floor.
Cost accuracy erodes next. A BOM that calculates production cost based on component prices only stays accurate if someone manually updates those prices every time a supplier changes them. In a spreadsheet, that update depends entirely on someone remembering to do it. Miss a price change, and every cost calculation built on that BOM quietly becomes wrong, sometimes for months before anyone notices margins have shifted.
Stock disconnection creates the third problem. A spreadsheet BOM has no built-in awareness of what components are actually in stock right now. Production planning based on a BOM that does not check current inventory risks committing to a build the business cannot actually complete, because a key component ran out weeks ago and nobody cross-referenced the two.
Multi-level BOMs push spreadsheets past what they can reasonably handle. Products with sub-assemblies, components that are themselves built from other components, require nested structure that Excel was never designed to manage cleanly. Manufacturers end up building workaround formulas and multiple linked tabs just to approximate what a proper BOM system handles natively.
What production planning actually needs from a BOM
A genuinely production-ready bill of materials needs to do more than list components. It needs to connect that list to the rest of the operation in ways a static spreadsheet cannot.
Cost accuracy needs to stay current automatically. When a supplier raises a component price, that change should flow into every BOM using that component immediately, updating production cost calculations without anyone needing to manually find and fix every affected spreadsheet.
Stock awareness needs to be built in. A production planning system should check current component stock against what a planned build actually requires, flagging a shortfall before production starts rather than after a build has already been scheduled around components that are not there.
Multi-level structure needs native support. Sub-assemblies and nested components should work the way they actually work on the production floor, not as an approximation forced into flat spreadsheet rows.
Version control needs to be built into the system itself. One current BOM per product, editable by the right people, with a change history that shows exactly what changed and when, removes the ambiguity that comes from multiple spreadsheet copies circulating at once.
Why this matters more as product complexity grows
A manufacturer building one simple product can often get by on a spreadsheet for longer than intuition suggests. The real pressure builds as product variation increases, as sub-assemblies get introduced, and as the business starts quoting production costs to customers based on numbers that need to hold up under scrutiny.
Inaccurate BOM costing does not just create an internal reporting problem. It directly affects pricing decisions. A manufacturer quoting a customer based on a stale component cost either underprices the job and absorbs the difference, or discovers the error too late to adjust. Either outcome erodes margin in a way that compounds across every job priced off the same outdated BOM.
What to look for in bill of materials software
Not every system marketed as BOM software actually solves the problems small manufacturers run into with spreadsheets. A few things are worth checking before assuming a platform delivers a real improvement.
Component costs should update automatically when supplier prices change, flowing through to every BOM that uses that component. The system should support multi-level BOMs natively, handling sub-assemblies without requiring workaround formulas. Stock levels should connect directly to the BOM, so production planning can check component availability before committing to a build. And the BOM should tie directly into actual production costing, so the number a manufacturer quotes a customer reflects real, current costs rather than a figure last checked months ago.
How Monesize Core approaches this
Monesize Core connects bill of materials data directly to inventory and purchasing, so component costs stay current automatically as supplier pricing changes, and production planning checks real stock levels before a build gets committed. Multi-level BOMs and sub-assemblies work natively, without forcing a manufacturer to approximate nested structure through spreadsheet workarounds.
Because BOM data lives inside the same connected system as purchasing and inventory, a small manufacturer gets one current version of each product’s BOM, with a clear change history, rather than several spreadsheet copies circulating with no reliable way to confirm which one reflects current production.
Moving from spreadsheet to system
Excel served its purpose for a lot of small manufacturers early on, and there is no shame in starting there. The shame is staying there once product complexity, team size, and the cost of a pricing error have all grown past what a spreadsheet can reliably manage.
If your BOMs live in Excel and nobody is fully confident which version is current, or your production costs have not been checked against real supplier pricing recently, that gap is worth closing before it shows up in a quote that undercuts your own margin.
Manage bill of materials and production costs in one system with Monesize Core. Request a demo to see how it fits your production process.