If you're building a hardware product, you already have a BOM. You might not call it that. It might be a tab in a Google Sheet, a CSV export from KiCad, or a table on a drawing in Onshape. But it exists, and everything downstream of your design depends on it being correct.
BOM management software is the tooling that keeps it correct. This post covers what a BOM actually is, what the software does, and who the players are across the market. If you want the honest take on why your current setup will eventually fail you, that's in Part 2.
What Is a BOM?
BOM stands for Bill of Materials. It's the complete list of everything that goes into your product: every mechanical part, every electronic component, every fastener, every wire harness, every piece of packaging, every subassembly. It includes part numbers, descriptions, quantities, revision status, and supplier information.
Think of it as the recipe for your hardware product. Without it, nobody can build your thing consistently. With a bad one, they'll build it wrong.
The tricky part: a hardware product doesn't have one BOM. It has several, depending on who's looking at it and why.
The engineering BOM (eBOM): This is the design-intent BOM. It lives in your CAD tools, organized around how the product was designed: assemblies, subassemblies, individual parts. Your MCAD tool (Onshape, SolidWorks) owns the mechanical side. Your ECAD tool (KiCad, Eagle, Altium) owns the PCB side. They don't talk to each other.
The manufacturing BOM (mBOM): This is what your contract manufacturer actually needs. It's organized around how the product gets built, not how it was designed. It includes things your CAD tools don't track: packaging materials, adhesives, lubricants, labels, wire harnesses, assembly instructions, and anything else that goes into the box.
The master BOM: What most startups call the spreadsheet where they try to stitch all of the above together. We'll come back to this.
What Does BOM Management Software Actually Do?
BOM management software is the layer between your CAD tools and your manufacturer. It's where all of those separate BOMs get unified into a single source of truth: one place where you can see your complete product, track changes over time, manage part revisions, understand your costs, and hand off clean data to the people who need it.
The things it does that a spreadsheet genuinely cannot:
Hierarchy and structure: A product isn't a flat list; it's a tree. Subassemblies contain parts; assemblies contain subassemblies. When a spreadsheet tries to represent that, you end up with nested rows, color-coded indentation, and formulas that break the moment someone sorts the sheet. A BOM tool understands hierarchy natively; it knows that changing a subassembly component affects every assembly that uses it.
Version control and change tracking: When you update a part, a BOM tool records what changed, when, and why. A spreadsheet gives you "last edited by [person] at [time]" and a prayer. When your CM asks "is this the latest version," you want to be able to say yes with confidence.
Cost rollups: Want to know what your product costs to build at 500 units? A BOM tool can calculate that across the entire product tree automatically. In a spreadsheet, that's a custom formula someone has to maintain, and that breaks every time you add a subassembly.
Multi-source BOM management: One place to see both your mechanical and electrical BOM, instead of two separate exports you reconcile by hand every time either one changes.
Supplier and component data: Approved vendor lists, manufacturer part numbers, lead times, lifecycle status. The stuff that lives in three different tabs of your master spreadsheet, slightly out of sync with each other.
The BOM Management Software Landscape
Not all BOM software is built for the same buyer. The market has three distinct tiers, and understanding where each one lives matters when you're deciding what's right for your team.
Tier 1: Enterprise PLM (Boeing, Not You)
At the top end, you have the true enterprise platforms: Siemens Teamcenter, Oracle Agile PLM (now Fusion Cloud PLM), SAP PLM, and Dassault ENOVIA. These aren't just BOM management tools; they're full PLM, ERP, MRP, MES, and SCM ecosystems rolled into one monolithic platform.
Enterprise loves acronyms almost as much as it loves monolithic software.
These systems are built for companies managing millions of parts across global supply chains, aerospace programs, and automotive platforms. Implementation is measured in years, not months. You need a dedicated IT team to run them, a systems integrator to deploy them, and a lot of patience. Oracle Agile PLM, one of the stalwarts of this tier, is actually reaching end-of-life in December 2027, which tells you something about how old this generation of software is.
If you're a hardware startup, these tools are not for you. They're not even in the same category as what you need.
Tier 2: Mid-Market PLM (Getting Warmer, Still Not You)
Below the true enterprise tier, you have the mid-market platforms: PTC Windchill and Arena PLM are the clearest examples. These are purpose-built PLM tools for manufacturers who are past the startup stage but not running billion-dollar supply chains.
Arena runs $1,200 to $2,500 per user per year, with a minimum spend that typically lands at $10K or more before implementation fees. Windchill starts higher, at $2,500+ per user annually, with significant setup costs on top. A 25-person team on Arena is realistically looking at $30K to $75K per year, plus the time it takes to implement, configure, and train your team.
These tools are genuinely good for what they're designed for: companies with dedicated ops or IT resources, formal change control processes, and enough product complexity to justify the overhead. That's not a criticism; it's just a description of the buyer they were built for.
If you're a hardware startup trying to get to your first production run, the cost and implementation timeline alone put these tools out of reach.
The Gap: Spreadsheets and oroForge
Below the mid-market tier, there isn't much. OpenBOM is worth a mention: it's a cloud-based, CAD-integrated BOM and parts catalog tool that sits in the gap between spreadsheets and full PLM. It handles structure and collaboration better than a spreadsheet, and it integrates with several CAD platforms. It's not a full PLM, but for teams primarily needing better BOM structure and CAD sync, it's a reasonable option.
For most hardware startups and small teams, though, the real default is still Excel or Google Sheets. It's free, it's flexible, and everybody already knows how to use it. The problem isn't that spreadsheets are bad tools; it's that they're the wrong tool for this specific job. More on that in Part 2.
This is the gap oroForge is built for: a lightweight PLM platform designed for hardware startups and small teams, at startup-friendly pricing, operational in minutes rather than months. The PLM that actually fits your team.
Who Actually Uses BOM Management Software?
Worth naming, because it's not just engineers. The BOM touches every function that interacts with your product:
Engineering: Authors the eBOM, owns component selection, manages revisions as the design evolves.
Procurement: Uses the BOM to source parts, track lead times, and flag components that are end-of-life or at risk of going out of stock.
Operations: Translates the eBOM into the mBOM for manufacturing, manages the handoff to contract manufacturers and suppliers.
Quality: References the BOM during inspection, non-conformance investigations, and compliance reviews.
Finance: Uses BOM data for cost rollups, margin analysis, and budget forecasting.
Every one of those roles needs the same current, accurate version. A spreadsheet with three slightly different copies floating around Slack doesn't give you that.
The Bottom Line
A BOM is the backbone of your hardware product. BOM management software is what keeps that backbone intact as your product evolves, your team grows, and your manufacturing relationships get more complex.
The right tool depends entirely on where you are: enterprise platforms for companies that can afford years-long implementations; mid-market PLM for established manufacturers with the budget and staff to support it; and purpose-built tools for startups and small teams that need to get organized without grinding to a halt.
In Part 2, we get into the specifics of why spreadsheets fail for hardware startups, when you actually need dedicated software, and what to look for when you're evaluating options.