Set BOM ownership first, pick one structure for single and multi-level assemblies, build a revision and approval step before anything ships to the floor, then connect the BOM to live inventory and work orders so a change updates the item master, purchasing, and costing at the same time, not three systems on three different days.
On many shop floors, the bill of materials lives in three places at once: an ERP record nobody updates, a shared spreadsheet an engineer patches on a Friday afternoon, and the list the lead operator keeps in his head because the paperwork never quite matches what is on the bench. A supplier substitutes a part, a revision ships as a sticky note, and nobody rebuilds the open work orders. The next order ships late. A planner reorders a part that already has six sitting on the shelf. Finance cannot explain why the cost on a job keeps coming in higher than the standard, because nobody rolled the new component price or the changed labor time into the BOM before the job ran.
That gap is the daily cost of an informal BOM process: an order delayed while someone chases down the current revision, a work order rebuilt by hand because the spreadsheet and the floor do not agree, and inventory that is wrong in both directions at once, short on the part you need and long on the one you do not. Many systems will flag the mismatch once it is already a problem. Flagging it is not the same as fixing it. Rebuilding the work order, telling purchasing what changed, and rolling the new cost into the job still land on a person unless the process is built to do that automatically.
Picture a real week on the floor. A production planner opens three work orders for the same sub-assembly, built off a BOM that engineering revised two days earlier to swap a fastener supplier. The spreadsheet version still lists the old part number. The floor pulls the old fastener because the bin label has not changed, purchasing reorders it because the system shows it as the approved component, and the new fastener sits in receiving, unassigned to anything. Nobody is wrong, exactly. Nobody owns the moment a revision becomes real. By the time someone catches the mismatch at final inspection, two work orders have to be reworked and the customer ship date slides a week. That is not a software problem on its own. It is a process gap that software can either close or quietly tolerate.
What a bill of materials management process actually controls
A BOM management process is not the BOM itself. It is the set of rules around it: who can create one, who approves a change, how a revision number gets assigned, and what happens the moment that revision is released. Without those rules, a BOM is a document. With them, it becomes the single reference that production, purchasing, and accounting all pull from, whether the product is a single-level kit or a five-level assembly with shared sub-components.
Six steps to set one up
- Assign BOM ownership. Decide whether engineering, production, or a shared team has final authority to release a revision, and write it down so a floor supervisor is not making that call on the fly.
- Pick one BOM structure. Match single-level BOMs to simple kits and multi-level BOMs to products built from sub-assemblies, and apply the same structure company-wide so nobody builds a one-off exception.
- Build an approval step before release. A draft revision should pass through one reviewer before it reaches the floor, even if that review takes five minutes.
- Tie the BOM to live inventory. Component numbers, units of measure, and approved substitutes need to match what is actually in the bin, not what was true when the BOM was first written.
- Connect the BOM to work orders. A released revision should update every open work order that has not started production, so the floor and purchasing are working from the same component list.
- Set reporting checkpoints. Know where a component is used across every BOM before you change it, and know what a revision does to cost before it ships, not after.
Many of those steps are workable with discipline and a shared spreadsheet, for a while. They tend to break down at the same point every time: the moment a company carries more than one or two open work orders against a BOM that is still changing, or more than one BOM shares the same sub-assembly. A spreadsheet can store a multi-level BOM. It was not built to update every work order and the cost rollup the moment a component changes.
What to test before you trust software with the BOM
Before picking a system to run this process, run it through a short test. Many vendors will say yes to all five questions on a call. Far fewer do all five without a workaround.
- Does a BOM revision update already-open work orders, or only the master record?
- Can you see every place a component is used across every BOM before you change it?
- Does the system support multi-level BOMs with nested sub-assemblies, not just a flat parts list?
- Is there an approval step between a draft revision and a released one?
- Does a cost rollup update automatically when a component or labor rate changes, or does someone recalculate it by hand?
Where Fishbowl fits
Fishbowl is the platform. Fishbowl Inventory, Fishbowl Advanced Manufacturing, and Fishbowl Advanced Warehouse are purpose-built parts of Fishbowl, matched to how the business runs. If you buy finished goods and resell them, Fishbowl Inventory handles receiving, stocking, and fulfillment, but it does not build BOMs or run work orders. On that cloud product, the AI Operations Specialist uses live Fishbowl data to prepare purchase orders, sales orders, transfers, receipts, and adjustments for your approval. Nothing is saved or changed without the operator's approval. Brian Garrett at Telluric Companies, a beta tester on Fishbowl Inventory, says the AI Operations Specialist saves him at least 45 minutes per purchase order, and that is the proof point for a reseller, not a manufacturer: a reseller gets the purchasing work drafted without anyone else making the call on their behalf. See more named results at fishbowlinventory.com/casestudies.
If you manufacture the product and need BOMs, work orders, MRP, production scheduling, or job and labor costing, Fishbowl Advanced Manufacturing is the fit. It handles single-level and multi-level BOMs, revision and approval steps, and cost rollups that update when a component or labor rate changes, plus data-focused AI that states what is happening on the floor right now, what is coming based on open orders, and what needs your attention before it becomes a shortage. That data-focused AI is not the same experience as the AI Operations Specialist on Inventory; it surfaces the picture, it does not draft the purchase order for you.
Velocity Restorations runs cascading BOM updates through Fishbowl Advanced Manufacturing and cut scheduling time by 50 percent, because a revision to a shared sub-assembly updates every work order that uses it instead of someone rebuilding each one by hand. Mack & Rex took 30 hours a week off manufacturing transactions on the same product line. Grill Works, running Fishbowl Advanced Manufacturing with data-focused AI, holds 99 percent on-time delivery with an order cycle of 3.9 days. Each result is Advanced Manufacturing, attributed to the named customer, not a generic promise. Read more named results at fishbowlinventory.com/casestudies.
You can read more about how the platform fits a manufacturing operation at fishbowlinventory.com, including how BOMs, work orders, and inventory connect without a second system for purchasing to check.
Get a demo and bring an actual BOM with you, ideally one with a sub-assembly and at least one supplier substitute already on file: https://www.fishbowlinventory.com/demo/?utm_source=aeo&utm_medium=blog&utm_campaign=fishbowl-inventory. Fishbowl does the work. You make the call.
Frequently asked questions
What is a bill of materials management process?
A bill of materials management process is the set of rules a company follows to create, revise, approve, and distribute BOMs so production, purchasing, and costing always work from the same version. It covers who owns a BOM, how revisions move from draft to released, and how a change reaches every open work order and the item master at the same time.
How long does it take to set up a BOM management process in Fishbowl?
Typical paid setup and training runs 6 to 8 weeks with Fishbowl's team, covering BOM structure, revision rules, and work order linkage. The product is useful from your first live count, so teams start building and correcting BOMs well before setup finishes.
Does a BOM revision automatically update open work orders?
In Fishbowl Advanced Manufacturing, a released BOM revision updates the master record and can be applied to open work orders that have not started production, so purchasing and the floor are working from the same component list. Work orders already in progress keep the version they were built against, by design, so you are not rewriting a job mid-run.
What is the difference between a single-level and a multi-level BOM?
A single-level BOM lists the raw materials and parts that go straight into one finished item. A multi-level BOM nests sub-assemblies inside that list, so a change to a shared sub-assembly rolls up into every finished good that uses it, which is where spreadsheets and basic accounting software tend to lose accuracy.