Hardware Engineering Guide

BOM Tracking Best Practices for Hardware Engineers

A complete guide to hardware bill of materials tracking software — covering BOM structure, change management, tooling selection, and cost control for engineering teams at every stage of development.

12 min read·Updated March 2025

What Is a Hardware BOM?

A bill of materials (BOM) is a structured, hierarchical list of every component, sub-assembly, raw material, and consumable required to build a physical product. It defines what to build, how many of each part are needed, and where each part comes from.

For hardware engineers, the BOM is arguably the most important engineering document produced during product development. It bridges design intent and production reality — connecting the CAD model to the procurement order, the cost estimate to the invoice.

Industry data: According to a 2022 Lifecycle Insights survey, 67% of hardware engineering teams still manage their primary BOM in spreadsheets — despite reporting that spreadsheet-based BOMs are their top source of production errors. Teams that migrate to structured hardware bill of materials tracking software report a 23% reduction in BOM-related production defects within the first year (Aberdeen Group, 2021).

A BOM typically includes: part number, part name, description, quantity per assembly, unit of measure, manufacturer, manufacturer part number (MPN), approved vendor, unit cost, and reference designator (for PCBAs).

Engineering BOM vs Manufacturing BOM

One of the most common sources of production errors is the gap between the engineering BOM (eBOM) and the manufacturing BOM (mBOM). Understanding the difference is fundamental to running a reliable development process.

AttributeEngineering BOM (eBOM)Manufacturing BOM (mBOM)
OwnerDesign / Electrical EngineerManufacturing / Process Engineer
StructureFunctional assemblies (how it works)Assembly sequence (how it's built)
IncludesAll designed componentsProcess materials: solder paste, adhesives, packaging
Primary usePrototyping, design reviewProduction, MRP, procurement
Created atDuring design phaseDuring DFM / production transfer
FormatCAD-linked, component-centricWork-order linked, operation-centric

During early-stage development (EVT/DVT), the eBOM is the primary working document. As the design matures toward pilot production (PVT), the eBOM is transformed into an mBOM by manufacturing engineering. Keeping these in sync through an automated BOM management system — rather than manual copy-paste — is the single highest-leverage improvement most hardware teams can make.

“The eBOM-to-mBOM transition is where most hardware startups lose weeks. If your BOM lives in three different spreadsheets owned by three different people, you will ship the wrong part at least once.”

— Hardware manufacturing consultant, quoted in Fictiv State of Hardware Development Report 2023

How to Structure Your BOM

A well-structured BOM uses a consistent, hierarchical numbering system and captures sufficient metadata to support procurement, costing, and change management without becoming unmanageable.

BOM Levels

  • Level 0: The finished product (top-level assembly)
  • Level 1: Major sub-assemblies (e.g., chassis, PCBA, power module)
  • Level 2: Component assemblies within each sub-assembly
  • Level 3+: Individual parts and raw materials

Required Fields for Each Line Item

FieldPurposeRequired for
Part NumberUnique internal identifierAll stages
Part Name / DescriptionHuman-readable identifierAll stages
Quantity per AssemblyHow many per parent assemblyAll stages
Unit of Measurepcs, g, mm, m, etc.All stages
MPN (Mfr Part Number)Links to specific component versionProcurement, DVT+
Approved VendorWho to buy fromProcurement
Unit CostPer-unit price for costingCost roll-up, BOM total
Reference DesignatorPCB position (R1, C2, U4…)PCBA BOMs
BOM LevelHierarchy depthIndented BOMs
RevisionCurrent design versionChange management

BOM Categories

Categorizing BOM line items by type makes filtering, cost analysis, and procurement planning significantly easier. Common categories include:

  • MECH — Mechanical parts: brackets, enclosures, bearings, gears
  • ELEC — Electronic components: resistors, capacitors, ICs, connectors
  • ELECTROMECH — Motors, solenoids, relays, sensors
  • FASTENER — Screws, bolts, nuts, standoffs, inserts
  • SOFTWARE — Firmware licenses, software libraries
  • OTHER — Packaging, labels, documentation

Change Management: The ECO Process

An Engineering Change Order (ECO) — sometimes called an Engineering Change Notice (ECN) — is the formal mechanism for making controlled updates to a BOM. Without a disciplined ECO process, BOM changes become invisible, untraceable, and eventually catastrophic.

Industry data: A 2023 PTC survey found that uncontrolled engineering changes account for 31% of hardware production escapes — defects that reach customers. Teams with a formal ECO process tied to their BOM reduce change-related escapes by an average of 58%.

What an ECO Should Capture

  • ECO number and date
  • Reason for change (cost reduction, component EOL, design fix, regulatory)
  • Affected assemblies and BOM levels
  • Old part vs new part (MPN, revision, quantity)
  • Disposition of existing inventory (use as-is, rework, scrap)
  • Effective date or serial number
  • Approvers (engineering, quality, procurement, manufacturing)

BOM Revision Best Practices

Version your BOM using a consistent scheme — typically alpha revisions during development (Rev A, B, C) and numeric revisions in production (Rev 1, 2, 3). Lock a BOM revision at each major milestone: end of EVT, end of DVT, start of PVT, production release. Never edit a locked revision — create a new one via ECO.

BOM Tracking Software Comparison

The right hardware bill of materials tracking software depends on team size, development stage, and integration requirements. Here is how the main categories compare:

Tool TypeBest ForLimitationsExamples
SpreadsheetSolo engineers, early concept BOM (< 50 parts)No version control, error-prone, no collaborationExcel, Google Sheets
Project Planning ToolPre-prototype teams needing BOM + requirements in one placeNot connected to ERP/MRPSpecZero
PLM (Product Lifecycle Mgmt)Mid-stage teams, multi-engineer, eBOM + mBOM managementComplex setup, expensiveArena PLM, Windchill, Teamcenter
ERP-integrated BOMProduction-stage teams, MRP, procurement integrationRequires IT, not engineer-friendlySAP, Oracle, NetSuite
PCB EDA (ECAD-linked)PCBA BOMs generated from schematicMechanical BOM only; siloedAltium, KiCad, Cadence

For most hardware startups and small teams, the practical BOM lifecycle is: spreadsheet → project planning tool → PLM → ERP. The mistake most teams make is staying in a spreadsheet too long, or jumping to a full PLM before the design is stable enough to justify the overhead.

Cost Control and Unit Price Tracking

A BOM is also a cost model. Every line item carries a unit price, and the sum of all line items — multiplied by quantity — gives you the Bill of Materials Cost (BOMC), the foundation of your product’s Cost of Goods Sold (COGS).

Industry data: McKinsey & Company found that 45% of hardware products exceed their target COGS at launch, primarily due to BOM costs that were not tracked or updated during development. Teams that maintain live unit prices on every BOM line item hit COGS targets at 2.3x the rate of teams using static cost snapshots.

Cost Tracking Best Practices

  • Enter a unit price on every BOM line item — even a rough estimate is better than nothing
  • Distinguish between target cost (what you need it to cost) and actual quoted cost
  • Update prices at each design milestone as quotes come in
  • Track total BOMC at the top assembly level and set an alert threshold
  • Categorize costs by BOM category (MECH, ELEC, FASTENER) to identify overspend quickly
  • Remember that BOMC at prototype quantities will be 3–10× higher than production pricing — normalize for volume

Source Classification

Beyond price, classify each line item by how it is sourced — this affects lead time, risk, and cost model accuracy:

  • PURCHASED — Off-the-shelf components ordered from a supplier
  • FABRICATED — Custom parts manufactured to your drawings (machined, sheet metal, injection molded)
  • PRINTED — Parts produced in-house via 3D printing or similar rapid prototyping

Common BOM Mistakes and How to Avoid Them

Mistake: Using a flat BOM when structure matters

Fix: Build a multi-level indented BOM from day one. A flat BOM makes it impossible to identify where a part is used or calculate accurate total quantities.

Mistake: Not capturing the MPN

Fix: Always record the manufacturer part number, not just the description. Descriptions are ambiguous — MPNs are not. A missing MPN at production will cause procurement delays.

Mistake: Treating the BOM as a static document

Fix: The BOM is a living document. Treat every BOM change as a tracked event with a timestamp and author. Use revision control — never edit a released BOM in place.

Mistake: No approved vendor list (AVL)

Fix: Document at least one approved vendor per line item. Supply chain disruptions are inevitable — an AVL makes re-sourcing a managed process instead of a fire drill.

Mistake: Skipping BOM reconciliation before pilot build

Fix: Before every build, run a BOM-to-kit check: every BOM line item must have a physical part in the kit. Discrepancies found on the bench cost hours; discrepancies found in production cost thousands.

Frequently Asked Questions

What is a hardware bill of materials (BOM)?

A hardware bill of materials (BOM) is a structured list of all components, sub-assemblies, raw materials, and quantities required to build a physical product. It serves as the single source of truth for procurement, manufacturing, cost tracking, and change management throughout the product development lifecycle.

What is the difference between an engineering BOM and a manufacturing BOM?

An engineering BOM (eBOM) reflects the design intent — organized by functional assemblies as the design team sees the product. A manufacturing BOM (mBOM) reflects how the product is actually assembled on the production line, including process-specific components like solder paste, fasteners, and packaging. Aligning eBOM and mBOM is a key challenge in hardware development.

What software do hardware engineers use for BOM tracking?

Common hardware bill of materials tracking software includes dedicated PLM tools (Arena PLM, Windchill, Teamcenter), ERP-integrated BOM modules (SAP, Oracle), and lightweight tools like SpecZero for early-stage project planning. Many small teams start with spreadsheets but migrate to structured software once BOM complexity exceeds 50–100 line items or multi-engineer collaboration is required.

How do you handle BOM changes during development?

BOM changes are managed through an Engineering Change Order (ECO) process. A formal ECO documents what changed, why it changed, which assemblies are affected, and who approved the change. Best practice is to version-stamp each BOM revision and maintain an audit trail so every product unit can be traced back to the exact BOM state at time of manufacture.

What is BOM explosion?

BOM explosion is the process of expanding a top-level assembly into all its constituent parts and sub-assemblies to calculate the total quantities of every component needed for a given production run. It is used in materials requirements planning (MRP) to drive procurement and manufacturing schedules.

Track Your BOM in SpecZero

SpecZero is hardware project planning software with built-in BOM tracking — per-item unit prices, category filters, source classification, and a Master BOM that aggregates across all project sections.

Start Free

Related Guides