A perfect Bill of Materials (BOM) is made by listing every component and sub-assembly, giving each part the correct internal and manufacturer part number, writing exact quantities and units, adding approved alternates, and locking the list with revision control so every team member works from the same version. When these steps are done right, the BOM stays clear, complete, and ready for quoting, buying, and production.
A good BOM is a simple parts list that shows exactly what to buy and what to build. But one wrong part number, missing quantity, or unclear entry can cause a wrong quote, a wrong purchase, or a stalled build. So, how do you make a bill of materials perfectly? This guide walks you through a clear step-by-step process, shows the fields you must include, and explains how CalcuQuote BOM Health helps keep your BOM source-ready from the first quote to the final build.
A perfect BOM is complete, accurate, and up to date. It includes every part required for production along with part numbers, descriptions, quantities, supplier data, alternates, pricing, lifecycle status, and revision codes. The BOM must match CAD files and assembly drawings. Before sending it to production, review all fields for errors, missing entries, or inconsistencies. This removes confusion for sourcing teams and prevents expensive rework during assembly. The practices involve:
A BOM is the main document that describes every component required to manufacture a product. It includes raw materials, electronics components, mechanical parts, consumables, and packaging items. In electronics, it also includes ICs, passives, connectors, sockets, sensors, PCBs, and more. Factories rely on BOMs for purchasing, costing, and assembly.
Different types of BOMs support different stages of a product’s development. Each format plays a unique role and helps different teams stay aligned.
An Engineering BOM is created during the design stage. It reflects the exact components used in the schematic or CAD file. Because it is still part of the design process, it may contain trial parts, temporary components, or items that will later be replaced with production-ready versions. This BOM changes often until the design becomes stable and ready for manufacturing.
A Manufacturing BOM is the version used directly by the factory. It removes all experimental parts and lists only confirmed, production-ready components. This BOM includes complete information such as reference designators, supplier details, alternates, packaging format, and any other data the production team needs. An MBOM remains stable and supports smooth and predictable assembly.
A Sales BOM is used by sales teams to describe product bundles or kits. It lists everything included in a package that customers will receive. It does not guide production but helps prepare accurate sales quotations and explains the contents of a bundled product clearly.
A Service BOM is created for repair and maintenance work. It includes only the parts needed to fix or service a product after it has been delivered to customers. This helps service staff quickly identify the correct replacement components without searching through the full manufacturing list.
Here is a quick side-by-side view of the main BOM types, helping teams understand how each version supports design, manufacturing, sales, and service activities:
|
BOM Type |
Purpose |
Used By |
Key Features |
|
Engineering BOM (EBOM) |
Represents the design-stage components |
Design & R&D teams |
May include trial parts, early versions, and frequent updates |
|
Manufacturing BOM (MBOM) |
Used for actual production and assembly |
Manufacturing & production teams |
Contains production-ready parts, designators, suppliers, and alternates |
|
Sales BOM (SBOM) |
Defines product bundles or kits for customers |
Sales & marketing teams |
Lists items included in a package; not used for manufacturing |
|
Service BOM |
Supports repair and maintenance activities |
Service & support teams |
Includes replacement parts needed after delivery |
A BOM stays useful only when it includes all key details that support purchasing, costing, and production. Here are the core components of a good BOM:
A correct BOM follows a clear sequence that moves from choosing the BOM type to validating every detail. Use these nine steps to answer how to make a bill of materials, with correct structure, clear part identity, sourcing details, and revision control.
Name the BOM view first. Use EBOM for design (PTC), MBOM for how the factory builds (Siemens Digital Industries Software), and SBOM for service parts (PTC). This stops teams from using different lists and arguing over versions.
Choose a structure to match the assembly. A single-level BOM is a flat list for simple products. A multi-level BOM groups parts into subassemblies such as PCBA, enclosure, cables, and packaging, clearly showing quantities.
Set identity rules before adding rows. Use your internal part number as the stable key, add the manufacturer part number for purchasing, write plain descriptions, and keep units consistent across the BOM.
Fill the core fields next: line item, level, internal part number, description, quantity, unit, revision, and short notes. These columns prevent duplicates and help reviews move fast across engineering, purchasing, and manufacturing.
Table: Core BOM columns
|
Column |
What to write |
Why it matters |
|
Line item |
10, 20, 30 |
Easy review references |
|
Level |
0, 1, 2 |
Supports multi-level BOMs |
|
Internal PN |
Your part number |
Prevents duplicates |
|
Description |
Plain-language name |
Faster buy and build |
|
Qty per assembly |
Exact number |
Prevents shortages |
|
Unit |
ea, m, kg |
Prevents unit errors |
|
Revision |
BOM or part rev |
Keeps versions aligned |
|
Notes |
Only what is needed |
Keeps it readable |
Add sourcing details so buyers do not chase engineering. Include manufacturer, MPN, supplier name, supplier part number, lead time if tracked, and lifecycle status. This cuts RFQ delays and reduces risky substitutions.
List approved alternates using AML and AVL. AML records approved manufacturer options for a part, and AVL records approved suppliers. Rank alternates so sourcing stays consistent when your first-choice item is unavailable.
For PCBAs, include reference designators, package, DNP or DNI, and variant fields. These tie each BOM line to the schematic and assembly, prevent footprint surprises, and make variant builds repeatable.
Table: Electronics-only BOM columns
|
Column |
Example |
Why it matters |
|
RefDes |
R1, R2, C10 |
Ties BOM lines to the schematic and placement. |
|
Package |
0402, 0603, QFN-32 |
Prevents footprint mismatch. |
|
DNP/DNI |
Yes/No |
Controls variant installs clearly. |
|
Variant |
Base, Pro, EU |
Defines what gets installed and when. |
|
Alt group |
ALT-RES-10K |
Keeps alternates organized. |
Fix issues before the RFQ so production does not stop later, and simplify your supply chain with smart BOM Import by letting the system structure and clean your BOM automatically.
Table: BOM validation checklist
|
Check |
Pass rule |
What breaks if you fail |
|
Missing MPN |
0 blank MPNs for buying parts. |
The buyer cannot source. |
|
Qty mismatch |
RefDes count matches Qty (PCBA). |
Wrong placement count. |
|
Duplicate parts |
Same PN used once per level. |
Double buys, confusion. |
|
DNP/DNI clarity |
DNP is shown in its own column. |
Wrong variant build. |
|
Revision present |
BOM rev is visible. |
Teams use different versions. |
|
Compliance flagged |
RoHS noted where required |
Compliance risk |
|
Lifecycle checked |
NRND/Obsolete flagged |
Late redesign and delays |
Control changes with ECO. Do not edit a released BOM in place. Create a new revision, record what changed and why, set when it takes effect, and keep approvals for traceability.
A clean BOM uses consistent fields, clear descriptions, correct quantities, and proper sourcing details. This example shows a simple, readable format suitable for electronics products. Below is a sample table, you need to understand:
Table A:
|
Line |
Level |
Internal PN |
Description |
Qty/Unit |
RefDes |
Package |
DNP/DNI |
Variant |
BOM Rev |
|
10 |
1 |
IPN-1001 |
Resistor 10k ohm, 1%, 0603 |
8 ea |
R1–R8 |
0603 |
No |
Base |
A |
|
20 |
1 |
IPN-1002 |
Capacitor 0.1uF, 50V, X7R, 0402 |
12 ea |
C1–C12 |
0402 |
No |
Base |
A |
|
30 |
1 |
IPN-2001 |
Microcontroller, ARM MCU |
1 ea |
U1 |
QFN-48 |
No |
Base |
A |
|
40 |
1 |
IPN-3001 |
BLE module |
1 ea |
U2 |
Module |
Yes |
Pro |
A |
Table A shows how the product is built. Table B shows how each line is sourced, costed, and risk-checked. Match them using the Internal PN.
Table B:
|
Internal PN |
Manufacturer (Preferred) |
MPN (Preferred) |
AML (Approved manufacturers) |
Supplier (Preferred) |
Supplier PN |
ASL (Approved suppliers) |
Unit Price |
Currency |
Lead Time (wks) |
Lifecycle Status |
|
IPN-1001 |
Yageo |
RC0603FR-0710KL |
Samsung: (Alt), Vishay: (Alt) |
Digi-Key |
311-10.0KHRCT-ND |
Mouser: (Alt), Arrow: (Alt) |
0.01 |
USD |
6 |
Active |
|
IPN-1002 |
Murata |
GRM155R71H104KE14D |
TDK: (Alt), Samsung: (Alt) |
Mouser |
81-GRM155R71H104K |
Digi-Key: (Alt), Arrow: (Alt) |
0.02 |
USD |
8 |
Active |
|
IPN-2001 |
STMicroelectronics |
STM32xxxx |
NXP: (Alt), Microchip: (Alt) |
Arrow |
(Supplier PN) |
Digi-Key: (Alt), Mouser: (Alt) |
3.50 |
USD |
18 |
NRND |
|
IPN-3001 |
(Mfr) |
(MPN) |
(Alt Mfr): (Alt MPN) |
(Supplier) |
(Supplier PN) |
(Alt supplier): (Alt PN) |
6.80 |
USD |
10 |
Active |
BOM quality matters because the BOM is the single source that tells teams what to buy, how much to buy, and what to build. If the BOM is wrong or unclear, every downstream step inherits the mistake, from quoting to purchasing to production. Here’s what poor BOM quality usually causes:
In short, BOM Insights enables you to combine supplier and internal data to fill BOM gaps, and a clean BOM reduces avoidable questions, prevents preventable mistakes, and keeps quoting and builds predictability.
CalcuQuote BOM Health helps teams keep their BOM stable by checking every line against real supply data. Instead of relying on a static spreadsheet, it shows availability, lifecycle position, pricing signals, and alternatives so teams can act early and avoid delays during quoting, buying, and production.
Here is what BOM Health adds to your process:
In simple terms, BOM Health protects the BOM from hidden risks and keeps it stable from the first quote until the final build.
A BOM is only “accurate” if it stays usable in the real world, not only in a file. Parts go out of stock, lead times change, and lifecycle status shifts, which can turn a clean-looking BOM into a sourcing problem overnight.
CalcuQuote helps prevent that by keeping supplier data close to your BOM, so teams can verify pricing and availability early, spot risky line items with BOM Health, and move to approved alternates before production gets blocked. It also reduces RFQ delays by keeping supplier responses and clarifications in one place, so engineering, purchasing, and program teams stay aligned from quote to buy.
Book a demo session to see how BOM Health flags lifecycle risks and checks availability across 24,000+ suppliers before you quote.
To make a Bill of Materials (BOM), list every part and subassembly, assign an internal part number, add the manufacturer part number, set the quantity and unit, include approved alternates, and control revisions so everyone uses the same BOM.
At a minimum, BOM can include part number, part description, quantity per assembly, and unit. For purchased parts, include the manufacturer name and manufacturer part number for clean sourcing.
Run a BOM scrub before RFQ or production by checking for missing MPNs, wrong quantities, duplicates, unclear descriptions, missing revisions, and obsolete parts. Fix issues early to avoid delays.
Include reference designators (R1, C3, U7), package/footprint, and DNP/DNI rules for variants, so the assembler places the correct parts in the correct locations.
CalcuQuote BOM Health checks each BOM line for supply risk signals like lifecycle status, stock levels, lead time, and supplier coverage, so teams can switch to approved alternates before RFQ, buying, or production.