A BOM for PCB assembly is more than a spreadsheet of parts. It is the sourcing and assembly control document that tells a PCBA manufacturer what to buy, what to populate, what to leave off, and which substitutions are allowed. If the BOM is unclear, the RFQ stalls before production ever starts.
Many PCBA RFQ delays begin with small BOM problems: a generic “10k resistor,” a missing manufacturer part number, unclear DNP status, no approved alternates, or a BOM that does not match the CPL. For a complete file package, pair the BOM with Gerber files, CPL, stackup, quantity, and test requirements.
For the broader file relationship, see our guide to Gerber, BOM, CPL, and stackup files. This article focuses on the BOM itself: required fields, preparation steps, substitution rules, and the final RFQ checks before you send files to a manufacturer.
Key Takeaways
- A clean PCB assembly BOM should include designators, quantities, exact MPNs, packages, values, DNP status, and approved alternates.
- BOM/CPL designator matching connects component sourcing to SMT placement and prevents avoidable clarification loops.
- The best BOMs define sourcing rules clearly enough that every supplier quotes the same build scope.
What Is a BOM in PCB Assembly?
A BOM affects PCB assembly quality and quote accuracy because it controls which components enter the assembly process. If part numbers, quantities, alternates, or DNP instructions are unclear, the supplier has to pause before sourcing, SMT setup, and pricing can move forward.
A BOM, or bill of materials, is the component sourcing and assembly list for a PCBA. It tells the manufacturer which parts to buy, which reference designators to populate, which alternates are allowed, and which parts should not be installed.
A PCB-only order may focus on Gerber and drill files. A PCBA order needs more. The supplier must source parts, check availability, prepare SMT placement, review substitutions, and understand the exact population scope. That work starts with the BOM.
BOM as a sourcing contract, not just a parts list
The most useful way to treat a PCB assembly BOM is as a sourcing contract. It defines what the supplier may purchase, what they may substitute, and what they must leave uninstalled. A vague BOM creates quote assumptions. A clean BOM creates quote control.
There are several BOM types. An engineering BOM may describe the design intent. A manufacturing BOM may include production packaging, labels, fixtures, or process notes. An RFQ BOM should be clean enough for sourcing and RFQ review, even if production documentation comes later.
Revision control matters here. The BOM should match the Gerber and CPL revision sent with the RFQ. If the BOM is older than the layout export, the supplier may quote the wrong components, wrong quantities, or wrong placement workload.
A PCB assembly BOM is the sourcing and assembly control list for a PCBA. It should identify exact components, allowed alternates, DNP parts, and designators clearly enough for the manufacturer to price sourcing and assembly scope confidently.
For the broader file relationship, see how Gerber, BOM, CPL, and stackup files work together.
What Fields Should a PCB Assembly BOM Include?
A quote-ready PCB assembly BOM should include reference designator, quantity, manufacturer, manufacturer part number, package or footprint, value, description, DNP status, approved alternates, and notes. These fields let the supplier understand what to source, what to assemble, what to skip, and what substitutions are acceptable.
The exact fields depend on project complexity. A simple prototype may only need basic part identity and quantity. A production PCBA usually needs tighter sourcing control, lifecycle notes, compliance notes, approved alternates, and customer-supplied part status.
| BOM field | Example | Why the manufacturer needs it |
|---|---|---|
| Reference designator | R1, C5, U2, J1 | Connects the component to the schematic, PCB layout, and CPL |
| Quantity | 12 | Confirms sourcing count and designator count |
| Manufacturer | Murata, TI, Molex | Reduces ambiguity during sourcing |
| MPN | GRM188R71C104KA01D | Defines the exact purchasable component |
| Package / footprint | 0603, QFN-32, SOIC-8 | Helps compare BOM data with CPL and PCB pads |
| Value / rating | 10 kΩ, 1%, 16 V | Prevents wrong generic substitutions |
| Description | Ceramic capacitor, X7R | Gives sourcing context when checking alternates |
| DNP / DNI | Do not populate | Prevents optional parts from being installed |
| Approved alternates | Alternate MPN list | Gives the supplier controlled sourcing options |
| Notes | Customer supplied, critical part | Flags handling, approval, or sourcing rules |
Minimum BOM fields for a PCBA quote
At minimum, include designator, quantity, manufacturer, MPN, package, value, and description. If you do not know the exact MPN yet, label the line as “engineering approval required” instead of leaving the supplier to choose silently.
Package and value are especially important for passives. “10k resistor” is not enough for controlled sourcing. The supplier needs package size, tolerance, power rating if relevant, and any approved manufacturer or part family preference.
Recommended fields for production builds
For production builds, add approved alternates, lifecycle status, preferred distributor, customer-supplied status, compliance requirements, and revision notes. If a part is safety-related, RF-related, firmware-related, or mechanically constrained, mark it clearly.
DNP and DNI instructions deserve their own column. Do not hide them in color formatting or side comments. The assembler should be able to filter the BOM and immediately know which parts should not be populated.
A clean PCBA BOM should separate required identity fields from sourcing-control fields. Required fields tell the supplier what each component is. Sourcing-control fields tell the supplier what substitutions, compliance constraints, and population rules are allowed during RFQ review.
Use these fields with the broader PCBA RFQ file checklist when preparing a complete package.
How Do You Prepare a BOM for Turnkey PCB Assembly?
For turnkey PCB assembly, prepare the BOM so the supplier can source parts with clear rules. Use exact MPNs, group identical parts clearly, mark DNP lines, include approved alternates, and export the BOM from the same design revision as the Gerber and CPL files.
Turnkey assembly adds sourcing responsibility to the manufacturer. That means the BOM must support pricing, purchasing, substitution review, receiving inspection, SMT setup, and final assembly population. A casual engineering parts list is not always enough.
Step-by-step BOM preparation workflow
First, export the BOM from the CAD tool after the design revision is ready for quote. Use the same revision that produced the Gerber and CPL files. Add the project name, board revision, export date, and contact person near the top or in separate metadata columns.
Second, normalize the column names. Use plain labels such as Designator, Qty, Manufacturer, MPN, Package, Value, Description, DNP, Approved Alternates, and Notes. Avoid merged cells, hidden columns, and color-only instructions because suppliers need to sort and filter the data.
Third, check the quantities against the designators. If one row lists R1, R2, R3, R4, the quantity should be 4. This sounds simple, but quantity mistakes can change sourcing cost and assembly assumptions.
Fourth, mark DNP or DNI lines clearly. Keep optional parts in the BOM, but mark them as not populated. Removing DNP parts entirely can create confusion if the CPL, schematic, or silkscreen still contains those designators.
Fifth, add approved alternates and substitution rules. If exact MPNs are required, say so. If equivalent passives are allowed, define the package, tolerance, voltage, temperature, and approval limits.
LEADHUI engineering note
LEADHUI PCB engineering reviews usually move faster when the BOM has exact MPNs, visible DNP instructions, and a BOM/CPL pair exported from the same CAD release. The file does not need to look complex. It needs to be consistent.
For turnkey builds, identify customer-supplied parts separately. If you will consign a programmed module, a rare IC, or a pre-purchased connector, mark the quantity supplied, expected delivery date, and whether the supplier should source backup parts.
A turnkey PCB assembly BOM should make sourcing and assembly scope explicit. Exact MPNs, clean quantities, visible DNP status, approved alternates, consigned-part notes, and revision alignment make the RFQ easier to quote and easier to compare.
Use the same file-package logic from the PCBA quote preparation checklist when preparing the BOM.
Why Do BOM and CPL Designators Need to Match?
BOM and CPL designators need to match because the BOM identifies each component, while the CPL tells the SMT machine where that component goes. The reference designator is the shared key between sourcing and placement. If it breaks, the RFQ slows down.
A BOM line might say U3 is a specific microcontroller. The CPL line for U3 should then give the X/Y position, rotation, side, and package for that same component. If the CPL lists U4 instead, the supplier has to determine whether the BOM, CPL, or layout export is wrong.
BOM vs CPL in one sentence
The BOM identifies components. The CPL places components. The designator connects the two files, so the supplier can verify that every sourced component has matching placement data and every placed component has a BOM identity.
Common mismatch patterns are easy to miss. A BOM may include R12, but the CPL may show R13. A CPL may include bottom-side parts that are missing from the BOM. A DNP component may remain in the CPL even though it should not be installed.
These mismatches do not always mean the design is wrong. Sometimes the files were exported at different times. Sometimes designators changed after layout cleanup. Sometimes optional circuits were removed from the BOM but not from the placement export.
Before sending an RFQ, sort the BOM and CPL by designator. Compare total designator count, top-side parts, bottom-side parts, and DNP items. Then check rotation-sensitive components such as LEDs, diodes, ICs, connectors, and electrolytic capacitors.
BOM/CPL matching is the simplest way to connect component sourcing with SMT placement. A clean match helps the supplier price parts, program placement, and review polarity without reconciling conflicting file exports.
For more context, see the BOM/CPL section in Gerber, BOM, CPL, and stackup explained.
BOM Mistakes That Delay PCBA Quotes
The BOM mistakes most likely to delay a PCBA quote are missing MPNs, generic descriptions, unclear DNP lines, unavailable or obsolete parts, no approved alternates, quantity errors, package mismatches, and BOM/CPL designator conflicts. Each one forces the supplier to pause and confirm what should be priced.
Most BOM problems are not dramatic engineering failures. They are small gaps that create sourcing or assembly uncertainty. A supplier can often identify the issue quickly, but the quote still waits for the customer to confirm the correct part, quantity, substitution rule, or population instruction.
| BOM mistake | Quote consequence | Fix before sending |
|---|---|---|
| Missing exact MPN | Supplier must guess or request part identity | Add manufacturer and manufacturer part number |
| Generic description only | Multiple parts may match the same description | Add value, package, tolerance, rating, and MPN |
| Quantity mismatch | Sourcing count may not match designator count | Compare quantity against listed designators |
| Package mismatch | Part may not fit the footprint or CPL package | Check footprint, package, and datasheet package name |
| DNP status unclear | Optional parts may be quoted or assembled incorrectly | Use a dedicated DNP/DNI column |
| No approved alternates | Quote stops when exact part is unavailable | Add approved alternate MPNs or approval rule |
| Obsolete or long-lead part | Quote cost and delivery become uncertain | Review lifecycle and availability before RFQ |
| BOM/CPL mismatch | Sourcing and placement data disagree | Sort both files by designator and compare |
| Compliance notes missing | RoHS/REACH or customer requirements may be missed | Add compliance and material notes where required |
How each mistake affects the quote
Missing MPNs are usually the biggest problem. A supplier can price “10k resistor” several different ways depending on package, tolerance, power rating, temperature range, brand preference, and availability. If you need a specific part, name it.
Generic descriptions can work for early estimates, but they should be labeled clearly. For example, “0603 10k 1% resistor, supplier equivalent allowed” is much safer than “10k.” It gives the sourcing team boundaries instead of forcing a guess.
DNP ambiguity can create assembly risk. If optional parts are removed from the BOM, but still appear in the CPL or silkscreen, the assembler may need clarification. Keep DNP lines visible and mark them clearly as not populated.
Approved alternates prevent avoidable quote delays. If the exact MPN is unavailable, the supplier can quote an approved substitute instead of waiting for engineering approval. If alternates are not allowed, state “exact MPN required.”
LEADHUI PCB RFQ reviews often slow down when the BOM looks complete at first glance but hides important sourcing rules. The most useful BOMs do not just list parts. They tell the supplier which choices are fixed and which choices can be proposed.
A clean BOM speeds RFQ review by removing sourcing uncertainty. Exact MPNs, clear DNP instructions, approved alternates, matching quantities, and compliance notes help every supplier quote the same PCBA scope.
Use the complete PCBA RFQ package checklist to confirm the BOM, Gerber, CPL, stackup, quantity, and test requirements before sending files.
How Should You Handle Alternate Parts and Substitutions?
Alternate parts should be listed as approved substitutions with clear rules. Do not leave substitutions entirely to the supplier unless the component is non-critical and the required package, value, tolerance, voltage, temperature, lifecycle, and compliance limits are already clear.
Substitutions can be helpful. They can reduce sourcing delays when the exact MPN is unavailable or expensive. But they can also create risk if the alternate changes electrical performance, mechanical fit, firmware behavior, certification status, or long-term availability. Alternate part decision tree for PCB assembly BOM review Alternate Part Decision Tree Use approved rules so sourcing can move quickly without uncontrolled substitutions. Exact MPN available?Quote exact part Approved alternateQuote listed substitute No approved alternateAsk engineering approval Exact MPN requiredDo not substitute Table view: quote the exact MPN when available; otherwise use approved alternates, request approval, or block substitution. Figure 4: Alternate-part rules let the supplier know when to quote exact parts, approved substitutes, or engineering approval.
Suggested alternate-part rule language
Use clear language in the BOM notes. For fixed components, write “exact MPN required.” For controlled substitutions, write “approved alternates only.” For lower-risk components, write “supplier may propose equivalent for engineering approval.”
Passive components may allow more flexibility, but only within defined limits. A resistor alternate should still match package, resistance, tolerance, power rating, temperature range, and any special requirement. A capacitor alternate should match package, capacitance, voltage, dielectric, tolerance, and derating needs.
ICs, connectors, modules, sensors, crystals, relays, and power components usually need stricter control. A substitute may fit the BOM description but fail the footprint, firmware, timing, mechanical, regulatory, or reliability requirement. When in doubt, require engineering approval.
Preferred, approved, and proposed substitutes
A preferred MPN is the part you want quoted first. An approved alternate is a part your team already accepts. A supplier-proposed substitute is only a suggestion until engineering approves it.
Keep those categories separate. If you mix them in one note, the supplier may not know whether the alternate is pre-approved or only a possible option. That can slow review or create sourcing assumptions you did not intend.
Approved alternates make a PCB assembly BOM more quote-ready because they define sourcing flexibility before parts are purchased. The best BOMs separate preferred MPNs, approved alternates, and approval-required substitutes so cost and lead-time decisions stay under engineering control.
For broader build-scope planning, use the PCB assembly quote file checklist alongside your BOM.
BOM Format for PCB Assembly Manufacturers
Send the BOM as a spreadsheet-friendly file such as XLSX or CSV, with clear column headers and one component line per unique item or designator group. A PDF can be useful as a reference, but it should not be the only BOM file for RFQ review.
Manufacturers need to sort, filter, count, compare, and sometimes import BOM data into sourcing or quoting systems. A clean spreadsheet is easier to review than a locked PDF, screenshot, image, or exported document with merged cells.
Recommended BOM file structure
Use simple column names and consistent formatting. Put designators in one column, quantity in another, and part identity fields in separate columns. Do not combine manufacturer, MPN, value, and package into one long description if those details can be separated.
A practical BOM file can use one row per unique component, with grouped designators such as R1, R2, R3. That format is compact and easy to quote. If your CAD tool exports one row per designator, that can also work, but quantities and grouping should be checked before sending.
Avoid hidden columns, merged cells, color-only instructions, and comments that disappear when exported to CSV. If a part is DNP, mark it in a visible DNP column. If a part is customer-supplied, add a visible consigned or customer-supplied column.
BOM file naming recommendation
Use a file name that shows the project, file type, revision, and date. For example: ProjectName_BOM_RevA_2026-07-14.xlsx. Use the same revision style for Gerber, CPL, stackup, and assembly drawings so the supplier can see which files belong together.
If you send multiple BOM versions, make the active version obvious. Do not send BOM_final.xlsx, BOM_final2.xlsx, and BOM_latest.xlsx in the same RFQ package. That creates exactly the kind of revision confusion the BOM is supposed to prevent.
| Format issue | Why it causes problems | Better approach |
|---|---|---|
| PDF-only BOM | Hard to sort, filter, or import | Send XLSX or CSV as primary file |
| Merged cells | Breaks filtering and import | Use one clear header row |
| Color-only notes | Notes may be missed or lost | Use visible text columns |
| Hidden columns | Supplier may quote incomplete data | Keep required data visible |
| Ambiguous file names | Revision confusion | Use project, BOM, revision, date |
A PCB assembly BOM should be editable, sortable, and revision-labeled. XLSX or CSV files with clear headers help the manufacturer review quantities, MPNs, DNP lines, alternates, and CPL matches without retyping the file.
For the full set of files that should travel with the BOM, see the Gerber, BOM, CPL, and stackup file guide.
BOM Review Checklist Before Sending an RFQ
Before sending an RFQ, check that each BOM line has a designator, quantity, exact MPN or approved description, package, value or rating, DNP status, and alternate rule. Then compare BOM designators with the CPL and confirm the revision matches the Gerber files.
This final check does not need to be complicated. It just needs to catch the small mismatches that stop a supplier from quoting confidently. A clean BOM lets the manufacturer price the same build you intended, not a guessed version of it.
| Checklist item | Pass check | Why it matters |
|---|---|---|
| Revision alignment | BOM, Gerber, CPL, and stackup use the same board revision | Prevents quoting mixed design releases |
| Designator coverage | Every populated designator appears in the BOM | Avoids missing sourced parts |
| Quantity check | Quantity equals the number of listed designators | Prevents underbuying or overbuying |
| Exact MPNs | Critical parts have manufacturer and MPN | Reduces sourcing ambiguity |
| Generic parts | Any generic line has clear package, rating, and approval rule | Keeps supplier equivalents controlled |
| DNP / DNI | Optional parts are clearly marked | Prevents accidental population |
| Approved alternates | Allowed substitutes are listed or approval rule is stated | Reduces sourcing delay |
| Customer-supplied parts | Consigned parts are identified with quantity and delivery notes | Prevents duplicate purchasing |
| Compliance notes | RoHS, REACH, or customer requirements are visible where needed | Keeps quote assumptions aligned |
| CPL match | BOM designators match CPL designators, side, and placement scope | Connects sourcing to SMT programming |
Pre-send checklist for engineers
Engineers should confirm that the BOM was exported from the same design release as the Gerber and CPL files. Check designator count, footprint names, DNP lines, and polarity-sensitive parts. Pay special attention to LEDs, diodes, IC pin 1, connectors, modules, and electrolytic capacitors.
Also review parts that affect firmware, timing, RF performance, high voltage, safety, or mechanical fit. These components should not be substituted without approval. If an alternate is allowed, list it clearly in the BOM.
Pre-send checklist for buyers
Buyers should confirm exact MPNs, approved alternates, quote quantity, lead-time target, customer-supplied parts, and compliance requirements. If a part is difficult to source, flag it before the supplier starts quoting. That helps separate true build cost from avoidable sourcing delay.
If several suppliers are quoting the same project, send the same BOM package to each supplier. Otherwise, you may receive quotes based on different substitution rules, different DNP assumptions, or different sourcing scope.
Engineering CTA: Need a faster PCBA quote? Send LEADHUI PCB your BOM, Gerber, CPL, stackup, quantity, and test requirements for engineering review.
A final BOM review should answer one question: can the supplier price the intended build confidently? If the answer is yes, the BOM is ready to support sourcing, SMT setup, and PCBA RFQ review.
Final BOM Check Before PCB Assembly RFQ
A clean BOM for PCB assembly controls sourcing, pricing, assembly population, substitutions, and quote speed. It should identify exact components, approved alternates, DNP parts, and designators clearly enough that the supplier does not need to guess.
Before sending an RFQ, check that the BOM matches the Gerber and CPL revision. Confirm quantities, MPNs, DNP lines, alternate rules, customer-supplied parts, and compliance notes. Small fixes here can prevent long quote delays later.
Send LEADHUI PCB your BOM, Gerber, CPL, stackup, quantity, and test requirements for engineering review before PCBA sourcing and assembly.
Next, review the full PCBA quote file checklist or compare how BOM, CPL, Gerber, and stackup files work together in the PCB assembly file package guide.
Frequently Asked Questions
What is a BOM in PCB assembly?
A BOM in PCB assembly is the component list used for sourcing, pricing, and assembly population. It tells the manufacturer which parts to buy, which reference designators to install, which parts are DNP, and which alternates are approved for the PCBA build.
What fields are required in a PCBA BOM?
A PCBA BOM should include designator, quantity, manufacturer, MPN, package or footprint, value, description, DNP status, and approved alternates where allowed. Production BOMs should also include lifecycle notes, customer-supplied status, compliance notes, and revision information.
Can I send a BOM without exact manufacturer part numbers?
You can send a BOM without exact MPNs for an early rough estimate, but it will usually slow RFQ review. Exact MPNs reduce ambiguity. If the exact part is not chosen yet, state the required package, value, rating, tolerance, and approval rule.
What is the difference between BOM and CPL?
The BOM identifies components. The CPL places components. The BOM tells the supplier what U3 is, while the CPL tells the SMT program where U3 goes, which side it is on, and how it should be rotated.
What does DNP mean in a BOM?
DNP means do not populate. DNI means do not install. Both tell the assembler that the listed component should not be mounted on the PCBA unless the instruction changes. Keep DNP parts visible in the BOM so they can be checked against the CPL.
