A prototype can power up perfectly on the bench and still become expensive, delayed or impossible to build in volume. The difference is often in the documentation, not the circuit. This guide to bill of materials explains how to create a BOM that gives engineering, purchasing and assembly teams the same clear definition of what must be built.
For electronic products, a bill of materials is not just a parts list exported from a CAD package. It is the commercial and manufacturing record of the design. It identifies every component required to produce an assembly, specifies approved parts and alternatives, supports accurate costing, and provides a controlled baseline when the design changes.
What a bill of materials should achieve
A production-ready BOM answers practical questions before they become production issues. Which 10 kΩ resistor is required? Is the connector supplied with a mating part? Can a substituted capacitor affect performance? Does the enclosure require inserts, fasteners or a printed label? Is the specified integrated circuit active, available and within budget?
For a PCB assembly, the BOM connects the schematic and PCB layout to the physical supply chain. For a complete product, it also brings together PCBAs, cables, mechanical parts, fasteners, packaging and purchased subassemblies. Its level of detail should match the stage of the project, but ambiguity should never be treated as flexibility.
At an early feasibility stage, a preliminary BOM may be enough to estimate cost and lead times. Before production, each line item needs sufficient information for a purchaser and assembly team to source, inspect and fit the correct item without relying on assumptions.
Core fields in a production BOM
The exact columns depend on the product and ERP or procurement system, but several fields are fundamental. A useful BOM normally includes:
- Item number and reference designators, such as R1, R2 and C14-C18 for PCB components.
- Quantity per assembly, including any wastage allowance managed separately by the manufacturer.
- Clear component description, value, package or relevant mechanical specification.
- Manufacturer name and manufacturer part number, commonly called the MPN.
- Supplier part number where purchasing channels have been selected.
- Approved alternates, lifecycle status, lead time and pricing where relevant.
- Design revision and assembly notes, particularly for polarity, fitment, programming or special handling.
The manufacturer part number is usually the most valuable field. A description such as “1 µF capacitor” is not adequate because it leaves voltage rating, dielectric, tolerance, package size and temperature performance undefined. “1 µF, 25 V, X7R, 10%, 0603” is far better, but an MPN provides the final traceable definition.
Reference designators matter for PCB assembly because they connect the BOM to placement data, drawings and inspection records. A line containing a quantity of 12 should state every relevant designator or refer to a controlled grouping rule. This prevents a buyer from treating identical-looking parts as interchangeable when they are allocated to different functions or performance grades.
How to build a bill of materials that can be manufactured
Start with the design source, not a manually typed spreadsheet. Schematic capture tools such as Altium and KiCad can generate an initial BOM directly from assigned component data. This is efficient, but it is only the first pass. Library fields are often incomplete, and generic symbols can conceal missing procurement decisions.
First, verify that every schematic component has an assigned and valid MPN. Then compare the exported list against the PCB layout, mechanical design and intended assembly method. The BOM needs to reflect what will be built, rather than only what appears electrically on the schematic.
For example, a product may require a PCB-mounted terminal block, a cable assembly, an enclosure, four mounting screws, heat-transfer material and a product label. Those items may sit outside the electronic CAD BOM but remain essential to the finished unit. A top-level BOM should account for them, while subassembly BOMs can separately define the PCBA, cable loom and enclosure assembly.
Specify components for the real operating environment
Choosing the cheapest available part at design time can create unnecessary risk later. Electrical rating, package availability, mechanical fit, service life and assembly compatibility all affect the correct selection.
A capacitor selected for a compact footprint may lose effective capacitance under DC bias. A connector may meet current requirements but lack adequate mating-cycle life. A plastic enclosure may be suitable for a desktop unit but not for industrial exposure, vibration or elevated temperatures. The BOM should capture the selected part and, where needed, the reason a substitute is not acceptable.
This is especially relevant for high-speed digital and RF designs. Equivalent values do not guarantee equivalent performance. Controlled-impedance connectors, RF passives, oscillator specifications and component package parasitics may be critical to the design outcome. In these cases, alternates should be approved through engineering review, not selected only on stock availability.
Include alternatives, but control them
An approved manufacturer list, or AML, reduces exposure to shortages and obsolescence. It is useful when alternatives are genuinely form, fit and function compatible. For a standard resistor or indicator LED, several approved options can protect production schedules. For a microcontroller, switching regulator or sensor, the alternate may require firmware, layout or validation changes.
A practical approach is to classify parts by substitution risk. Low-risk passive components can have pre-approved alternates. Medium-risk parts should require engineering confirmation before use. High-risk or sole-source components should be flagged early, with a supply strategy agreed before production release.
Avoid filling a BOM with unverified alternates simply to make it look supply-chain ready. An alternate that has not been checked against the circuit, footprint, assembly process and qualification requirements may create more risk than it removes.
Make revision control part of the BOM process
A BOM without revision control can lead to a mixed build: the latest PCB, an older firmware image and components purchased for a previous circuit revision. That is difficult to diagnose and costly to rework.
Each release should have a unique revision and date, with matching references across the schematic, PCB files, fabrication data, assembly drawings, pick-and-place files and firmware. When a component changes, record what changed, why it changed, and whether existing stock can still be used.
Engineering change orders do not need to be bureaucratic for low-volume work, but they need to be visible. A simple controlled change record can identify the affected BOM lines, old and new MPNs, required validation and effective build date. This gives purchasing and production teams a reliable decision point rather than relying on email history.
For products with variants, do not maintain separate spreadsheets that slowly drift apart. Use a structured BOM with fitment rules. A single platform might have different radio modules, display options or regional power supplies, while sharing most of the PCB and mechanical parts. Variant-aware BOM management reduces duplicate effort and makes the differences auditable.
Check supply, cost and assembly before release
A BOM review should take place before ordering long-lead parts or committing to a production schedule. Availability is not only about whether a distributor shows stock on a particular day. Check lifecycle status, factory lead time, minimum order quantity, supplier concentration and the possibility of counterfeit exposure for scarce components.
Cost should be reviewed at the assembly level. A lower-cost component may increase placement complexity, require an extra assembly process or raise test time. Conversely, a modestly more expensive part can reduce the number of fitted components or simplify the mechanical assembly. The best BOM cost is the total delivered manufacturing cost, not the lowest unit price on an individual line.
Assembly requirements also need clear notes. Examples include moisture sensitivity level handling, polarity markings, selective soldering, press-fit hardware, programmed devices, conformal coating exclusions and test requirements. These instructions may live in supporting documents, but the BOM should point to the correct controlled reference.
Common BOM failures and how to avoid them
Most BOM problems are preventable. Generic descriptions, missing MPNs, obsolete parts and unapproved substitutions are frequent causes of purchasing delays. Another common issue is a mismatch between the BOM and the design files after a late change.
A disciplined release check helps catch these faults. Confirm that quantities match the schematic and mechanical assembly, all components have traceable sourcing data, no duplicate or contradictory lines remain, and special-process notes are included. Then have someone outside the design task review the package as if they must buy and build it. If they need to ask a question, the release package needs more definition.
For complex electronic products, involving PCB assembly and mechanical manufacturing early is often more efficient than correcting documentation after the design is complete. Jefi Electronic Services can support this handover across PCB design, prototyping, mechanical integration and small-to-medium volume assembly, helping teams identify manufacturability and sourcing issues while changes are still manageable.
A well-managed BOM gives a product team more than a shopping list. It creates a practical agreement between design intent and manufacturing reality. Treat it as an engineering deliverable from the first prototype onward, and each build becomes easier to quote, source, assemble, test and repeat.
