Image source: https://centralinnovation.com/assets/Screenshot-2025-11-20-154439__ScaleMaxWidthWzEyMDBd.png
In most manufacturing businesses, the bill of materials gets built twice. An engineer creates it in CAD, exports it to a spreadsheet, and then someone in purchasing or production types it back into the ERP system, line by line, fixing part numbers and quantities as they go. Nobody designed it that way. It just grew. And it works right up until a revision lands halfway through a job and the shop floor is building to revision C while purchasing is still ordering for revision B. The right software closes that gap, but only if you pick it for the right reasons. Most feature lists look alike. What separates a useful tool from expensive shelfware is how well it carries a BOM from the design office to the people who buy and build.
Start With Where Your BOM Breaks Today
Before you sit through a single demo, trace one recent job from model to dispatch. Where did the BOM leave CAD? Who touched it next? How many times was it copied, reformatted or re-keyed before a work order went out? Most shops find three or four handoffs they didn't know they had, plus at least one person who quietly corrects part numbers because the CAD file and the ERP item master never agreed. That map becomes your buying criteria. If your pain is re-entry, you need automated transfer. If revisions keep going missing, you need change control first.
Some owners push back here. Re-keying a 40-line BOM takes ten minutes, so why bother? Fair point, except the ten minutes was never the cost. The cost is the one job in fifty where the wrong quantity goes in and nobody notices until the material turns up.
Check How It Turns an Engineering BOM Into a Manufacturing BOM
This is where a lot of software falls over. The BOM an engineer builds in CAD, the engineering BOM or EBOM, describes the product as designed. Production needs something different: a manufacturing BOM (MBOM) that reflects how the thing is actually made. That means raw material called up as cut lengths or sheet sizes, consumables like welding wire and fasteners that never appear in the model, phantom assemblies that exist in CAD but not on the floor, and purchased parts split out from made ones. Picture a simple steel frame. In CAD it's six members and a base plate. On the floor it's two lengths of RHS cut to size, one sheet of plate, weld wire, primer and a subassembly that gets painted before final fit-up. Software that can't bridge those two views just leaves the gap for someone to fill by hand.
Ask every vendor to show you that conversion using one of your own assemblies, not their tidy demo file. Good bom management software applies rules to restructure the EBOM automatically, so nobody rebuilds it by hand each time. If the answer is "your team adjusts it in Excel before import", you'd be paying for a tool that keeps the exact step you're trying to get rid of.
Judge the Integration, Not the Feature List
A BOM tool earns its keep in the connections. It should read directly from the CAD and PDM setup you already run (SOLIDWORKS PDM is common in Australian and New Zealand shops), write into the ERP or MRP system you already use, and deal with any custom systems without a months-long development project.
So ask the awkward questions. What happens when a new part appears in the model: does it create the item in ERP, or flag it for someone to create? Does data flow one way or both? Purchasing often needs lead times and stock levels while the design is still being finished, and a one-way feed won't give them that. Be wary of anything that needs a consultant every time you add an ERP field. Integration that only works on day one isn't really integration. It's a project with a support contract attached.
Make Sure Changes Are Controlled Across Teams
Revisions are where disconnected BOMs do the most damage. You want one governed BOM that engineering, purchasing and production all see, with a clear revision history and an approval step before anything reaches the shop floor. When an engineer swaps 6 mm plate for 8 mm, purchasing should know straight away which open orders are affected, and production should see the new revision on their work orders without anyone sending an email.
Check who can approve a change and whether the system records why it was made, not just what changed. That note matters six months later, when a customer asks why their unit differs from the last one.
Don't choose on the demo. Choose on your own data. Take the job you traced earlier, hand the same assembly to two or three vendors, and watch how each one moves it from CAD into ERP without a spreadsheet in the middle. The one that copes with your messiest BOM, odd consumables and all, is usually the right pick. The rest is presentation.