Quick answer
A turnkey PCBA BOM should identify one released assembly and variant, then state each fitted or DNP item with reference designators, quantity, manufacturer and full MPN. Add approved alternates, sourcing ownership, packaging or programming needs and project-specific lifecycle or traceability fields. Reconcile the BOM with placement data and drawings, and never let availability silently authorize a substitute or revision change.
A turnkey BOM is not only a shopping list. It is a controlled release that tells sourcing and assembly teams which product configuration to build, which exact items are approved, which locations are fitted, what may not be substituted and who can decide when supply conditions change. If those decisions are absent, availability can silently redefine design intent.
PCBArise publishes component sourcing as part of a coordinated project route, including BOM review, exact part identity, approved alternatives, packaging, receiving and project-specific traceability discussions. The actual quotation and released BOM define the scope. No alternate is automatically approved because a similar part is available.
Start with one controlled assembly identity
Place the assembly part number, BOM revision, active variant, release status and date where they cannot be confused with line-item data. Name the owner or authority for the release. If fabrication data, BOM, Pick & Place and assembly drawings use different revision or variant identifiers, reconcile them before sourcing begins.
The companion manufacturing file guide explains why a data format does not settle release completeness. The BOM owns component identity and population decisions; fabrication data defines the bare board; placement data supplies coordinates and rotation; drawings carry visual or process intent. A file manifest should state which revision of each is authoritative.
Essential turnkey BOM fields
Column names can vary, but the released BOM should make each decision explicit. At minimum, include the item or line number, reference designators, quantity per assembly, description, manufacturer, full manufacturer part number and package or footprint. Add a fitted/DNP state and variant information where more than one configuration exists.
For controlled purchasing, also identify the approved alternate state, source or ownership rule and any do-not-substitute restriction. Packaging, programming, date/lot, lifecycle, compliance or traceability fields should be included where the product or project actually requires them. Do not add generic columns that no owner will maintain; every field should close a sourcing, assembly or acceptance decision.
MPN, manufacturer, internal part and distributor SKU are different
The full manufacturer part number (MPN) identifies the orderable item intended by the design. Pair it with the manufacturer name because descriptions alone can hide changes in package, grade, tolerance, voltage, temperature range or other ordering details. Do not truncate meaningful suffixes.
An internal company part number can connect the design to an approved item master, but it should not replace the manufacturer and full MPN unless the controlled internal system resolves them unambiguously for every recipient. A distributor SKU identifies a seller's listing, not the manufacturer item itself, and can change by region or packaging. Treat it as sourcing metadata rather than the sole design identity.
Reference designators, quantities, variants and DNP
Reference designators tell assembly where each line applies. Quantity per assembly should reconcile with the number of fitted references for the active variant. When grouped values or non-fitted positions are used, the BOM, placement data and assembly drawing must express the same state.
DNP, DNI, NF and similar labels are not self-explanatory across organizations. Define the approved term, record the affected references and keep the quantity consistent. Do not omit non-fitted references if their absence could be mistaken for missing data. For variants, generate or clearly filter the released BOM so the assembler does not infer population state from an uncontrolled master list.
BOM fields and the risk created by ambiguity
| Field or group | Decision it closes | Risk when missing or ambiguous | Release check |
|---|---|---|---|
| Assembly ID, revision, variant | Which product configuration is being priced and built | Files from different releases may be combined | Match the file manifest, BOM, placement and drawing |
| Reference designators and quantity | Which locations are fitted for the active variant | Population count and placement cannot be reconciled | Count fitted references and resolve DNP entries |
| Manufacturer and full MPN | The exact orderable component | Similar descriptions can hide package, grade or rating changes | Preserve complete ordering suffixes and manufacturer |
| Package or footprint | Expected physical implementation | A sourcing candidate may not match land pattern or assembly route | Compare against design library and placement data |
| DNP/DNI and variant state | What must not be placed | Master BOM and active build can diverge | Use one defined status and active-variant filter |
| Approved alternates and authority | What substitution is permitted and by whom | Availability can silently alter design intent | Record approval and update controlled BOM or AVL |
| Sourcing, packaging and traceability | Who buys, in what condition, with which retained evidence | Ownership, handling and receipt records become unclear | State project-specific requirements and evidence |
How to control approved alternates
Availability, lifecycle or commercial pressure may justify an alternate proposal, but it does not grant approval. Record the proposed manufacturer and exact MPN, the reason for the proposal and the named technical authority. Evaluate form, fit and function plus electrical, mechanical, footprint, polarity, thermal, firmware, qualification and regulatory impact as applicable to the product.
The decision can be approve, reject or defer. If approved, update the controlled BOM or approved-vendor/alternate list and state whether the approval is global, variant-specific, build-specific or temporary. If a new source, packaging form or date/lot condition changes the agreed risk, reopen the decision. The prototype-to-production checklist shows how sourcing findings must flow back to the production baseline.
Lifecycle, packaging, traceability and procurement context
Lifecycle and availability checks are time-specific observations, not promises of future supply. Record when the check was made and what source or evidence informed it. ECIA's current authorized-channel guidance reinforces why source identity and traceability matter; project rules should state when authorized distribution, manufacturer documentation or other evidence is required.
Packaging data can distinguish tape-and-reel, cut tape, tray, tube, bulk or other forms and may affect handling, setup or minimum order conditions. Moisture sensitivity, bake, electrostatic protection, serialization, lot/date information or certificates should be stated only when required by the product or agreed route. PCBArise's turnkey assembly page describes the coordinated model; the project BOM and quotation decide which controls apply.
BOM release and alternate approval flow
Keep sourcing feedback connected to configuration control. A proposed substitute should not live only in a supplier email, and an approved decision should not remain absent from the BOM or AVL. The purchase record, receiving evidence and built assembly must be traceable to the state that was actually approved.
Printable BOM release checklist
Assembly and version control
- □ Assembly part number, BOM revision, active variant, release date and authority are stated.
- □ BOM, fabrication data, Pick & Place and assembly drawing belong to the same release.
- □ Superseded or duplicate spreadsheets have been removed from the package.
Line-item identity and population
- □ Every fitted line has references, quantity, description, manufacturer and full MPN.
- □ Package/footprint and meaningful ordering suffixes are preserved.
- □ Fitted and DNP/DNI states use one defined convention and reconcile with placement data.
- □ Internal part numbers and distributor SKUs do not obscure the exact manufacturer item.
Sourcing and approval
- □ Customer, manufacturer or assembler purchasing ownership is clear for every special line.
- □ Approved alternates, do-not-substitute rules and the approving authority are explicit.
- □ Lifecycle and availability evidence has a date and does not imply guaranteed supply.
- □ Packaging, programming, traceability, date/lot or compliance inputs are stated where required.
- □ Proposed alternates have a form/fit/function and project-impact disposition before purchase.
Print this page or use the browser's Print to PDF option for the BOM release review. The checklist supports configuration control; the approved BOM, AVL, drawings and purchase requirements remain authoritative.
Send a controlled BOM for turnkey review
For a PCB assembly review, provide one current BOM with the active variant, full MPNs, population state, approved alternates and sourcing ownership, together with placement data, drawings, quantity and build stage. PCBArise can then identify open sourcing and assembly questions without guessing design intent. Use the project review page when the controlled package is ready; this guide does not require a form submission.
Engineering review
Prepared and reviewed for project use
Engineering Director
Senior Quality Engineer
Review scope: technical accuracy, evidence wording, standards references, internal links and release readiness. Project requirements remain subject to the released files, applicable acceptance criteria and agreed test documentation.
FAQ
Questions engineers ask before release
What fields should a BOM include for turnkey PCB assembly?+
Include the assembly part and revision, active variant, item or line, reference designators, quantity per assembly, description, manufacturer, full MPN, package or footprint and fitted/DNP state. Add alternate, sourcing, packaging, programming and traceability fields where the project requires them.
Is a distributor part number enough for a PCBA BOM?+
Usually not as the sole identity. A distributor SKU identifies a seller listing and may vary by region or packaging. Preserve the manufacturer name and complete manufacturer part number, then use distributor data as sourcing metadata.
How should DNP or DNI parts appear in the BOM?+
Define one status convention, list the affected reference designators and keep the fitted quantity consistent with the active variant. Reconcile that state with placement data and assembly drawings so absence is not mistaken for missing information.
Can the assembler choose an alternate when the specified part is unavailable?+
Only through the approval route defined for the project. Availability can trigger a proposal, but the designated technical authority should evaluate applicable form, fit, function, firmware, qualification and regulatory effects before the controlled BOM or AVL is updated.
What should be checked before releasing a BOM for sourcing?+
Confirm one assembly revision and variant, reconcile references and quantities with placement data, verify full MPNs and packages, resolve DNP states, name sourcing ownership and alternate authority, and state any required packaging, lifecycle or traceability evidence.
Reference points
Sources and verification starting points
External standards and industry references help frame the decision. Confirm current supplier evidence and project-specific requirements before release.