A bill of materials (BOM) in electronics manufacturing is the structured list of every component, quantity and reference designator needed to build a PCB assembly. It tells the assembler exactly what to buy and where each part goes. A complete, consistent BOM is one of the biggest factors in whether prototype assembly starts on time or stalls for clarification.
For engineers moving from prototype to NPI, the BOM is more than a parts list. It links the schematic, the placement data and the purchasing process. The questions below cover what it should contain, how errors cause delays, and how to check it before ordering.
What information must a PCB BOM contain?
A PCB BOM must contain, for every line, the reference designators, quantity, manufacturer name, manufacturer part number (MPN), component description and package or footprint. Together these identify each component unambiguously, so the assembler can source the correct part and place it in the right position with the right orientation.
The manufacturer part number is the most important field. A description such as “100nF 0402 capacitor” matches thousands of parts, while an MPN identifies one specific component. Useful additional fields include:
- Value and tolerance for passives, such as 10 kΩ, 1%
- Voltage, power or temperature ratings where they matter to the design
- Mounting type, so SMT and through-hole parts are clearly separated
- Do not fit (DNF) flags for parts that are on the schematic but not populated
- Approved alternatives, if substitutions are acceptable
The BOM must also agree with the placement (centroid) data. Every reference designator in the BOM should appear in the placement file, and vice versa, apart from deliberately unfitted parts.
How do BOM errors delay PCB assembly?
BOM errors delay PCB assembly because the assembler cannot safely start purchasing, kitting or machine programming until every line is clear. Each ambiguity, missing field or mismatch triggers a clarification cycle with the engineer, and the order waits until it is resolved.
Typical causes include:
- Missing or incorrect manufacturer part numbers
- Part numbers that do not match the intended package, for example a different footprint size
- Reference designators in the BOM that are absent from the placement data, or the reverse
- Quantities that do not match the number of designators listed
- Obsolete, unavailable or long-lead-time components with no approved alternative
- Ambiguous polarity or orientation information for diodes, LEDs, ICs and connectors
The consequences range from lost days during preparation to assembly errors that only appear during testing. Incomplete or inconsistent BOM information can cause engineering clarification, preparation delays and assembly errors, and each avoidable round of questions adds to the development schedule. This is a particular problem in prototyping, where the schedule is already tight.
How should a BOM be formatted for a manufacturer?
A BOM should be supplied as a clean, structured spreadsheet file, typically CSV or Excel, with one row per unique component and clearly labelled columns. Consistent column headers, one MPN per line and reference designators separated predictably make the file easy to read, whether by an engineer or by automated import tools.
Practical formatting tips:
- Use one header row with clear names such as Reference, Quantity, Manufacturer, MPN, Description and Package.
- Group identical components on a single line, with all designators listed in one cell using a consistent separator.
- Keep one part per line. Avoid merged cells, notes squeezed into value fields and multiple part numbers in one cell.
- Export directly from your EDA tool where possible, then enrich it with MPNs rather than retyping data manually.
- Match naming exactly between the BOM, schematic and placement file.
- Flag DNF parts explicitly instead of deleting them silently, so the assembler knows the omission is intentional.
Avoid decorative formatting, hidden columns and comments that carry essential information. Anything the assembler needs should sit in a visible, labelled column.
What is the difference between an engineering BOM and a manufacturing BOM?
An engineering BOM (EBOM) reflects the design as the engineer conceived it, usually generated from the schematic. A manufacturing BOM (MBOM) reflects what is actually needed to build and assemble the product, including sourced part numbers, packaging, alternatives and any non-electronic items required for production.
Engineering BOM
The EBOM is organised around design intent. It lists components by function and designator, often with generic values and descriptions. It changes frequently during development as the design evolves, and it may not yet specify a sourced MPN for every line.
Manufacturing BOM
The MBOM is organised around building the product. It specifies exact manufacturer part numbers, approved alternatives and the items needed for assembly, such as hardware, labels or other mechanical parts. It must stay consistent with placement data and assembly documentation.
For prototypes, the two are often close. As a project moves into NPI, the BOM stabilises and the gap closes, with component selections confirmed and documented. A stable, verified BOM is also a prerequisite if production later transfers to an EMS provider.
How does the BOM affect PCB assembly cost and sourcing?
The BOM affects PCB assembly cost and sourcing because it defines every purchased part, its availability and its price. Component choices usually drive a large share of assembly cost, and a BOM with scarce, obsolete or over-specified parts raises price, extends lead time or forces redesign.
Several BOM decisions have a direct commercial impact:
- Component availability. Parts with long lead times or limited stock can hold up the whole build, however fast the PCB itself is made.
- Specification level. Tighter tolerances or higher ratings than the circuit needs add cost without adding value.
- Standardisation. Reusing common values and packages reduces the number of unique lines to purchase and handle.
- Package choice. Very small or unusual packages can affect assembly effort and handling requirements.
- Alternatives. Pre-approving equivalent parts gives the assembler room to keep the build moving if a first-choice part is unavailable.
Total development cost also includes engineering time and repeat builds. A cheap component choice that causes a sourcing delay or an assembly rework can cost more than it saves.
How can a BOM be checked before ordering assembly?
A BOM can be checked before ordering assembly by comparing it systematically against the schematic, the placement data and the PCB footprints, and by verifying each component’s identity, package and availability. The goal is to catch data problems while changes are still cheap and digital.
A practical pre-order checklist:
- Confirm every line has a valid MPN and that it matches the intended component and package.
- Cross-check designators between the BOM and placement data, so no part is missing or duplicated.
- Verify quantities against the number of designators on each line.
- Check footprints against the datasheet package dimensions for each component.
- Confirm polarity and orientation for diodes, LEDs, electrolytic capacitors, ICs and connectors.
- Review availability and lifecycle status for each part, and note approved alternatives.
- Mark DNF components and confirm they are excluded consistently across all files.
- Re-export the BOM after any design change so it never lags behind the layout.
This kind of component verification is part of broader pre-production verification, which analyses PCB and assembly data before physical production begins. It reduces avoidable clarification cycles, but it cannot confirm that a design will work electrically. Functional validation still belongs to prototype testing.
How Eurocircuits helps with BOM preparation and assembly
Eurocircuits combines in-house PCB prototype manufacturing and assembly with digital tools that help engineers prepare clean, consistent data before production starts. Its component engineering infrastructure and Verified Component Database support BOM checks, so component data problems can be identified before assembly rather than during it.
- Component verification against the BOM and placement data
- PCB Visualizer for analysing how your design data is interpreted for manufacturing
- Pre-production verification aimed at reducing avoidable iterations, in line with the Right First Time approach
- PCB manufacturing and assembly under one roof, which simplifies engineering communication
If you are preparing a BOM for a prototype or an NPI build, contact the Eurocircuits team to discuss your project and get your data production-ready.