How to Create a PCB BOM: Required Fields, Formats & Common Costly Mistakes

One hardware team released Gerbers for a power board on Friday and expected assembly to start Monday. The fabricator replied with 14 BOM questions: three capacitor voltages were missing, two resistor packages did not match the footprints, and the microcontroller line item listed only an internal part code. Purchasing lost four days chasing answers, and the prototype slot was gone before the file package was complete.

Another team shipped the same week with a shorter board bring-up cycle and fewer emails from the factory. Their BOM already included manufacturer part numbers, approved alternates, DNI notes, package data, and sourcing comments for long-lead parts. The difference was not board complexity. It was documentation discipline.

A PCB bill of materials, or BOM, is not just a component list. It is the document that connects design intent to procurement, kitting, assembly, inspection, and cost control. This guide explains what a good PCB BOM includes, which fields are mandatory, which fields save time later, and which mistakes create the most avoidable production delays.

What a PCB BOM actually does

A PCB BOM is the structured list of every component required to build an assembled board. In manufacturing terms, it is the purchasing and placement reference that tells the factory what each designator is, what package it uses, what exact part should be bought, and whether substitutes are allowed.

If Gerbers describe the bare board, the BOM describes the populated board. Your Gerber file package tells the fabricator where copper, solder mask, drill holes, and silkscreen belong. Your BOM tells the assembler which parts belong on those pads. Without both, the build package is incomplete.

The broader manufacturing definition of BOM appears in the standard industrial explanation of a bill of materials, but PCB work adds a few special requirements: reference designators, package consistency, approved alternates, do-not-install instructions, and close coordination with centroid data, assembly drawings, and procurement risk.

The minimum fields every PCB BOM needs

A BOM does not need to be complicated, but it does need to be unambiguous. At minimum, every production-ready PCB BOM should include these fields:

Field	Why it matters
Item number	Gives each line item a unique row reference for purchasing and ECO tracking
Reference designator	Maps the BOM entry to the PCB, such as R12, C34, U5, or J2
Quantity	Tells purchasing and kitting how many pieces are needed per board
Manufacturer name	Prevents confusion when multiple vendors use similar descriptions
Manufacturer part number (MPN)	The single most important sourcing field; identifies the exact component
Description	Human-readable summary such as 10 kOhm 1% 0603 resistor
Package / footprint	Confirms that the sourced part matches the land pattern on the PCB
Mount type	Distinguishes SMT, through-hole, press-fit, hand-insert, or other assembly method
DNI / DNP status	Marks optional or excluded parts clearly so they are not populated by mistake

If any of those fields are missing, someone downstream has to guess. In PCB assembly, guesses become delays, substitutions, or rework.

The fields that save purchasing from emailing you back

A minimal BOM can work for a lab build. A production BOM should do more than meet the minimum. The following fields are not always mandatory, but they prevent many of the common back-and-forth loops between engineering, purchasing, and the assembler.

Recommended Field	Practical benefit
Supplier part number	Makes it easier to buy from approved distributors quickly
Approved alternate MPNs	Keeps long-lead or allocation-sensitive parts from blocking the build
Lifecycle status	Flags NRND, obsolete, or single-source risk before procurement starts
Tolerance / rating	Helps buyers confirm they did not choose a look-alike part with the wrong electrical spec
Voltage / power / temp rating	Prevents dangerous substitutions on capacitors, resistors, regulators, and connectors
RoHS / compliance note	Useful for regulated products and customer compliance records
Notes	Captures special instructions such as hand solder, polarity check, or exact height limit
Internal part number	Useful for ERP alignment, but never as a substitute for the MPN

Expert Insight - Hommer Zhao: "The most expensive BOM error is not always the wrong part. Often it is the part that cannot be identified fast enough. If your assembler needs to ask what U7 or C48 actually is, the schedule is already slipping."

Manufacturer part number vs internal part number

Many teams keep internal ERP or PLM codes for stock control. That is fine, but an internal code should supplement the BOM, not replace the sourcing identity.

Good practice: include both the internal part number and the manufacturer part number.

Bad practice: include only an internal code like CAP-10UF-25V-X7R and assume the factory knows what it maps to.

The MPN is what protects you from ambiguous descriptions. A line that says "10 uF 25 V X7R 0805" may correspond to dozens of parts with different DC bias behavior, case height, temperature ratings, and lead times. A real MPN removes the guesswork.

If you plan to allow equivalents, list them explicitly as approved alternates rather than letting procurement decide on the fly.

How to group designators correctly

Grouped designators keep a BOM readable and reduce duplicate rows. If ten resistors use the same exact component, group them on one line: R1,R3,R7,R8,R10,R11,R15,R16,R21,R22 with quantity 10.

That only works when the parts are truly identical in all ways that matter:

Same value
Same tolerance
Same voltage or power rating
Same package
Same manufacturer part number
Same assembly status

The moment one capacitor needs a higher voltage rating, or one resistor package shifts from 0402 to 0603, it belongs on its own line item. Grouping unlike parts under one description is a quiet way to create assembly escapes.

Footprint mismatch is one of the most common BOM failures

A BOM line is only valid if the sourced part matches the footprint in layout. That sounds obvious, but it is one of the most common prototype blockers.

Typical mismatch cases include:

A resistor listed as 0603 in the BOM while the layout footprint is 0402
An SOIC package specified for a footprint drawn for TSSOP
A connector family described correctly, but with the wrong orientation or pin pitch
Electrolytic capacitors with correct capacitance but wrong can diameter or height

This is why the BOM should be reviewed together with the assembly drawing and the placement files, not in isolation. A good DFM package checks that description, footprint, and land pattern all point to the same physical part.

The best BOM format to send to a PCB assembler

For most PCB assembly jobs, a clean CSV or XLSX file is the safest format. It is easy to read, easy to import into ERP systems, and easy for contract manufacturers to normalize.

A good BOM export should follow four rules:

One header row only.
One component family per line item.
No merged cells, hidden columns, color-only notes, or multi-tab surprises unless your assembler asked for them.
Explicit column names like Reference, Qty, Manufacturer, MPN, Description, and Package.

PDF is acceptable as a viewing copy, but not as the working BOM for procurement. Buyers need sortable, filterable data. If you only send PDF, someone else has to rebuild your table before ordering parts.

If your CAD tool exports extra columns that are meaningless outside the design database, remove them. A shorter, cleaner BOM is usually better than a noisy one.

What to include when a part is optional or not fitted

Optional populations are common in prototypes, tuning networks, regional variants, and feature-gated products. If those parts are not managed clearly, the factory may populate them anyway or hold the job waiting for clarification.

Use a clear convention such as DNI, DNP, or NF and keep it consistent across the entire package. Do not mark one file DNI, another NC, and a third optional without explanation.

Also make sure optional parts agree across all manufacturing outputs:

The BOM should flag the part as not fitted.
The centroid or pick-and-place file should exclude it if your assembler expects that behavior.
The PCB assembly and manufacturing process guide logic should be reflected in the handoff package so placement, inspection, and test teams are reading the same intent.

If you build multiple variants from one PCB, it is often cleaner to issue separate BOMs per variant than to overload one spreadsheet with complicated conditional notes.

Approved alternates: where BOM resilience really starts

Supply risk rarely shows up where engineers expect it. A board can be electrically correct and still miss its schedule because one common regulator or connector is on a 26-week lead time.

That is why a good production BOM often includes an AVL-style approach: primary MPN plus approved alternates. The key word is approved. Procurement should not be left to substitute based only on value and package.

Alternate Strategy	When it works	Risk
No alternates	Short prototype runs with easy-to-source passives	High schedule risk if any part goes out of stock
Distributor equivalent only	Basic passives where electrical behavior is well bounded	Moderate risk if derating details are not checked
Approved alternate MPN list	Most production programs	Best balance of control and sourcing flexibility
Buyer-chosen substitute	Only in emergencies with engineer approval	Highest risk of fit, form, or function mismatch

For critical semiconductors, magnetics, connectors, oscillators, and safety components, alternates need engineering review. Similar-looking datasheets do not guarantee identical startup behavior, thermal margin, or EMI performance.

The handoff package a BOM needs to travel with

A BOM alone does not create a buildable package. It needs to travel with the rest of the manufacturing outputs:

Gerbers or ODB++ / IPC-2581 outputs for the bare board
Drill data
Pick-and-place / centroid file
Fabrication drawing when needed
Assembly drawing with polarity, orientation, and special notes
Variant instructions if multiple populations exist
Test requirements or inspection notes when relevant

If your team wants a quick sanity check before release, open the board outputs in the YourPCB Gerber Viewer and compare them against your footprint assumptions, board edge constraints, and assembly references. A short review here is cheaper than discovering a package mismatch after parts are ordered.

For broader manufacturability checks, pair the BOM with your PCB DFM design rules reference. DFM errors and BOM errors often arrive together because both come from incomplete release discipline.

The five BOM mistakes that cost the most money

1. Missing manufacturer part numbers

This is the classic delay trigger. Descriptions like "red LED 0603" or "USB connector" are not sourcing data.

2. Package and footprint disagreement

The part ordered is correct electrically but physically wrong for the board. This usually surfaces only after kitting or during setup.

3. Ambiguous passive descriptions

A capacitor is not fully specified until value, dielectric, voltage rating, tolerance, and package are clear. The same applies to resistor power rating and temperature coefficient when those matter.

4. No alternates for known risk parts

If the MCU, regulator, connector, or oscillator is hard to source, the BOM should say so before purchasing starts. Hoping the distributor has stock is not a sourcing plan.

5. Variant logic spread across emails instead of files

When the build instructions live partly in the BOM, partly in email, and partly in a screenshot, factories miss things. Put release intent in controlled files.

A practical BOM review workflow before release

A disciplined review does not need to be slow. It just needs to be systematic.

Export the BOM from CAD and remove unused or confusing columns.
Confirm every line has a valid manufacturer and manufacturer part number.
Verify that package names match actual PCB footprints.
Check quantity against grouped designators.
Mark all DNI or variant items explicitly.
Add approved alternates for long-lead or allocation-prone parts.
Review the BOM beside the assembly drawing, centroid file, and Gerbers.
Send the package for one final engineering or sourcing review before release.

The engineers who do this consistently spend less time answering procurement emails and more time debugging actual hardware.

Should you include pricing in the BOM?

For internal estimating, yes. For the manufacturing release copy, usually no unless your process specifically expects cost columns.

Pricing ages quickly and can distract from the primary purpose of the release BOM, which is unambiguous build intent. A better approach is to keep cost analysis in a separate sourcing sheet linked to the same approved MPN set.

References

Frequently Asked Questions

What should be included in a PCB BOM at minimum?

At minimum, include reference designators, quantity, manufacturer, manufacturer part number, description, package or footprint, mount type, and DNI status where applicable. Anything less forces the assembler or buyer to infer details that should have been explicit.

I already have internal company part numbers. Do I still need manufacturer part numbers?

Yes. Internal codes help your ERP system, but the manufacturer part number is what lets an external assembler or distributor identify the exact component. Use both, not one instead of the other.

What is the best file format for sending a BOM to a contract manufacturer?

A simple CSV or XLSX file is usually best because it is machine-readable and easy to normalize. PDF is fine as a viewing copy, but it should not be the only working file.

I am building two product variants from one PCB. Should I use one BOM or two?

If the differences are more than a few DNI options, issue separate BOMs per variant. That reduces ambiguity during purchasing, setup, inspection, and traceability.

If an exact component is out of stock, can purchasing substitute a similar one?

Only if engineering has already approved the alternate. Similar value and package do not guarantee equivalent behavior, especially for regulators, oscillators, connectors, relays, magnetics, and high-capacitance MLCCs.

Need help reviewing your release package?

Before you send a board to fabrication and assembly, verify that the BOM, assembly drawing, and Gerbers all agree. Use our PCB tools, inspect the board in the Gerber Viewer, or contact our team if you want a second set of eyes on a release package before purchasing starts.