Electronic component buying guide
How to Prepare a BOM for Electronic Component Sourcing
A sourcing-ready BOM tells a supplier exactly what may be purchased. Pair every buyable line with the manufacturer and full orderable MPN, valid demand, approved-alternate rules, lifecycle and source controls, packaging needs, and a controlled revision. Remove DNP lines, resolve blanks, and make every exception visible before suppliers quote.
Copy the BOM Template
Manufacturer and complete orderable MPN Auditable demand Alternate authority
No substitute, approved list, or engineering review Lifecycle risk
Dated status, PCN/EOL signal, and owner Quality and packing
Traceability, evidence, handling, and lot rules Quote response
Price, availability, lead time, terms, and exceptions
Quick answer
A sourceable BOM is a controlled buying document, not a raw design export.
Engineering defines what the design needs. The sourcing BOM defines which exact parts, sources, alternatives, conditions, and delivery terms may satisfy that design.
- Use one released BOM revision for each RFQ.
- Give every blank cell a controlled meaning.
- Keep manufacturer, MPN, and supplier-source approval separate.
- Carry approved exceptions into the PO and receiving plan.
Start with the right version
Why an engineering BOM is not yet a sourcing BOM
The files are related, but each answers a different business question. The sourcing BOM bridges approved design intent and the conditions under which a part may be purchased.
Engineering
Engineering BOM
Defines design intent, reference designators, technical selection, assembly quantity, and configuration relationships.
Often missing: current source policy, alternatives, packaging, commercial fields, and receiving rules.
Procurement
Sourcing BOM
Adds exact purchasable identity, source and alternate authority, lifecycle, risk, quality, packaging, demand, and RFQ response fields.
Its job: let suppliers quote the same requirement and make deviations visible.
Production
Manufacturing BOM
Organizes build structure, consumables, process materials, kitting, and work-order context for the production flow.
It may rely on a separate controlled sourcing view for market and supplier decisions.
Receipt
As-built record
Records what arrived and was used: supplier, lot or date code, packaging, quantity, deviations, and acceptance evidence.
It records the result; it does not retrospectively approve a design or sourcing change.
Use one source of truth for each RFQ release.
Put the assembly, variant, BOM revision, release date, and owner in the file and the RFQ subject. A supplier should never have to choose between the latest email, an older spreadsheet, a drawing note, and an ERP export.
The essential fields
Build each line around eight connected information groups.
Use one row per buyable manufacturer part number. Group reference designators only when the MPN, package, revision, configuration, and sourcing rule are identical.
Configuration
BOM revision, effective date, assembly or variant, line number, reference designators, and internal part number.
Prevents stale revisions and product options from being mixed.
Part identity
Manufacturer, full MPN, datasheet reference, description, package, grade, and the technical attributes that decide acceptability.
Defines the exact device instead of a generic description.
Demand
Quantity per assembly, build quantity, total demand, unit, approved yield or scrap factor, required date, and destination.
Lets suppliers calculate usable quantity, price breaks, and delivery phases.
Approval
Approved manufacturer or source status, substitute rule, named alternatives, deviation route, and engineering owner.
Keeps flexibility controlled rather than accidental.
Lifecycle and risk
Active, NRND, EOL, discontinued, or unknown status; check source and date; PCN signal; risk tier; and mitigation owner.
Focuses early action on lines that can stop the build.
Quality and traceability
Source condition, traceability depth, certificate needs, lot and date-code rule, inspection plan, test scope, and approval authority.
Defines the evidence required before a quote can become a released shipment.
Packaging and compliance
Reel, tray, tube, full or partial pack rule, factory seal, ESD, MSL, dry pack, mixed-lot rule, and required declarations.
Protects receiving and production from technically correct but unusable stock.
Supplier response
Quoted identity, source, available quantity, lead-time basis, price, currency, MOQ, validity, freight basis, NCNR status, and exceptions.
Creates a comparable quote across suppliers.
Example: one sourcing-ready BOM lineScroll horizontally on a small screen
Line017
Ref designatorsU3
Manufacturer / MPNSTMicroelectronics STM32F103C8T6
Qty / build1
Alternate policyNo substitute without approval
Lifecycle / riskDated check required
Packing / evidenceTray or reel; labels and lot data
Exact part identity
Use the full orderable MPN, not a shortened family name.
The manufacturer part number is the most important sourcing field. Pair it with the manufacturer name and copy the complete orderable code from approved manufacturer documentation.
Do not delete a suffix because it looks like a packaging detail. A suffix may define package, temperature range, finish, speed, memory, calibration, security configuration, qualification, tape-and-reel option, or another property that changes what will arrive.
- Keep manufacturer and MPN in separate columns.
- Add a controlled datasheet or drawing reference.
- Use a description as a human cross-check, not as the purchasing key.
- List every proposed alternate as a separate manufacturer and MPN.
Too vague
“10 kΩ resistor, 0603”
What is missing
Tolerance, power, temperature coefficient, voltage, manufacturer, full MPN, grade, and alternate authority.
Sourceable line
Manufacturer + complete MPN + 10 kΩ + 0603 + approved technical attributes + quantity + delivery need + alternate rule.
Objective check
Add the datasheet or controlled specification revision used for approval so a mismatch can be raised before quoting.
Before you send the RFQ
Clean and release the BOM in nine controlled steps.
BOM cleanup is cross-functional. Procurement should not invent technical data, and engineering should not make commercial assumptions silently. Missing information needs an owner and a visible status.
Freeze the configuration
Confirm assembly, variant, revision, effective date, build stage, and delivery location.
Remove non-buy items
Exclude DNP, reference-only, tooling-only, obsolete-option, and non-purchasable lines from the RFQ view.
Normalize identity
Correct manufacturer names, complete MPNs, suffixes, legacy aliases, duplicates, spaces, and hidden characters.
Reconcile demand
Check quantity per assembly, build quantity, total demand, yield assumptions, designators, and delivery phases.
Resolve every blank
Replace silence with N/A, pending approval, no substitute, supplier proposal required, or a sourcing hold.
Set source and alternate rules
Identify authorized-only lines, named alternatives, no-substitute items, and engineering-review routes.
Add lifecycle and risk
Record the source and date of the check, PCN or EOL signals, sole-source exposure, and mitigation owner.
Add acceptance conditions
State packaging, handling, traceability, inspection, compliance, destination, and delivery requirements.
Publish the RFQ revision
Preserve the engineering source file and record every later change with its reason, owner, and effective date.
A blank cell has no shared meaning.
It can mean unknown, not applicable, not yet approved, or accidentally omitted. Use controlled values such as “N/A,” “engineering review pending,” “No substitute,” or “Supplier to propose - buyer approval required.” This makes risk visible and prevents silence from becoming permission.
Demand and authority
Get the quantity math right and make alternate rules explicit.
A supplier should be able to audit the demand and know exactly what procurement may do when the stated part is unavailable.
Demand
Show how total quantity was built
Record quantity per assembly, build quantity, total demand, approved yield or scrap factor, and separate prototype, pilot, and production dates.
Do not let DNP lines or inactive variants enter formulas.
Reference designators
Group only identical rules
Reference designators can share one row only when the MPN, package, grade, configuration, and sourcing policy are identical.
Different suffixes or qualification levels need separate buyable lines.
Delivery phases
Separate “now” from “later”
Show the useful quantity for each date and destination. One total can hide a small urgent need and a later production balance.
State whether partial, split, or scheduled delivery is acceptable.
Alternate status 01
No substitute
Quote and buy only the named manufacturer and MPN. If it is unavailable, the supplier identifies the gap rather than shipping an “equivalent.”
Best for locked designs, qualifications, software dependencies, and high application risk.
Alternate status 02
Approved alternate
Quote each approved manufacturer and MPN as a distinct option with its own source, quantity, price, delivery, and evidence.
The selected option must be confirmed in the PO and checked at receiving.
Alternate status 03
Engineering review allowed
Collect structured proposals with datasheet, package, lifecycle, source, price, and delivery information.
Written engineering and quality approval is required before purchase or shipment.
A cross-reference is not an approved alternate.
A distributor or database can suggest a useful candidate, but engineering and quality still need to accept it for the actual design, configuration, manufacturing process, qualification level, and end use.
Lifecycle, traceability, and risk
Focus the review on the lines that can stop the build.
Lifecycle status is a dated sourcing fact, not a permanent label. Traceability is the ability to connect the received part to the agreed identity, source, package or label information, and relevant records. Apply deeper controls as source and application risk rise.
Risk factor
Standard review
Elevated review
High-risk action
Lifecycle
Current active evidenceRecord source and check date.
NRND, open PCN, or uncertain statusEscalate ownership and timing.
EOL or discontinuedEvaluate LTB, alternate, redesign, and controlled market sourcing.
Source concentration
Multiple approved routesConfirm the quoted source.
Single manufacturer or routeConfirm lead time and allocation.
Broker-only or unclear historyUse exception approval, source disclosure, inspection, and quarantine controls.
Substitutability
Named approved alternatesQuote as separate lines.
Review candidates availableCollect technical and lifecycle data.
No practical alternateRaise schedule visibility and define redesign or reserve action.
Packaging and quality
Routine commercial lineConfirm identity, quantity, pack, and standard records.
MSL, full-reel, lot, or evidence needWrite the acceptance rule into BOM and RFQ.
Critical use or exposed sourceAgree sampling, inspection, testing, evidence, and release authority.
Time-stamp lifecycle and PCN checks.
Record whether the manufacturer identifies the part as active, NRND, discontinued, or affected by a product or process change. Save the source, check date, owner, and resulting action. Manufacturer portals such as onsemi Product Change Notifications show why this is a continuing review, not a one-time label.
Use date code for traceability, not as a shortcut for authenticity.
ECIA explains that manufacturers define the process event behind a date code, such as fabrication, packaging, or inspection. If your build restricts date code or lot mixing, state the acceptable range, evidence, exception owner, and whether mixed material may be separately identified.
Match traceability depth to risk.
IPC-1782B organizes manufacturing and supply-chain traceability around perceived risk. The BOM does not need every certificate in a cell, but it should name the required evidence, record location, owner, and approval status.
Standard commercial line
Exact MPN, approved source policy, packaging label, quantity, and standard program records.
Critical or high-value line
Defined source path, lot or date-code information, agreed certificates, inspection or test evidence, and release approval.
Obsolete or shortage line
Lifecycle decision, source and condition disclosure, packaging evidence, inspection plan, and alternate or redesign path.
Usable at receiving and production
Specify packaging, moisture handling, and compliance at the line level.
A technically correct part can still be unusable when the delivery format, labels, ESD protection, moisture condition, lot mix, or supporting declaration does not match the build.
Placement format
Reel, tray, tube, or cut tape
State full or partial reel rules, reel quantity, original tray or tube needs, and whether repacked material may be offered.
Protects kitting and automated placement compatibility.
Labels and lots
Factory seal and mixed-lot rules
State original-label needs and whether opened, repacked, mixed-lot, or mixed-date-code inventory may be quoted.
Supports receiving checks, traceability, and failure analysis.
Handling
ESD, MSL, and dry pack
For moisture-sensitive devices, use the product label and manufacturer documentation to define moisture barrier, caution label, dry-pack, and process requirements.
Do not impose one generic floor-life rule on every package.
From BOM rule to receiving check
Put packaging conditions where they cannot disappear.
Write reel, tray, tube, seal, label, ESD, MSL, dry-pack, and lot requirements into the sourcing BOM and RFQ. Carry the selected condition into the PO and receiving plan so inspection checks the same requirement procurement approved.
Be specific about RoHS, REACH, and material data.
State the target market, actual MPN, accepted declaration format, and approval owner. A component declaration supports the finished-product compliance file, but it does not by itself prove the whole product's compliance or export eligibility. Requirements and exemptions can change, so the responsible compliance team should confirm the current obligation.
From clean BOM to comparable offers
Turn the BOM into an RFQ package suppliers can quote.
Do not send an unfiltered export with “please quote.” Give suppliers a controlled input and a response structure that preserves the buyer's original fields.
- Release
Issue the controlled sourcing BOM, revision, owner, and response deadline.
- Define demand
Separate prototype, pilot, production, forecast, required dates, and destinations.
- State controls
Add source, alternate, packaging, quality, evidence, and compliance rules.
- Compare
Review offered identity, quantity, source, condition, price, timing, terms, and exceptions.
- Carry forward
Put accepted conditions and deviations into the PO, acknowledgment, and receiving plan.
| Quote field | Supplier should state | Buyer should confirm |
|---|---|---|
| Offered item | Exact MPN, manufacturer, package, grade, packing suffix, and every difference from the request. | Is it the exact approved identity? |
| Quantity and timing | Available quantity, MOQ, multiples, split schedule, stock basis, lead time, and dated commitment. | Does it solve the useful demand and required dates? |
| Source and condition | Supply route, new or surplus condition, factory seal, pack type, lot and date-code information, and traceability available. | Does the supply basis match the BOM risk and approval route? |
| Quality and evidence | Included documents, photos, inspection or test scope, sample basis, report timing, and exceptions. | Is the requested scope included in price and delivery? |
| Commercial terms | Price, currency, breaks, validity, payment, freight basis, warranty, NCNR, return limits, and supplier exceptions. | Are all offers compared on the same landed and contractual basis? |
Compare exceptions before discounts.
The lowest unit price can create the highest program cost when it depends on an unapproved source, arrives in unusable packaging, lacks required evidence, or misses the build date. Keep exceptions in a dedicated quote field so they do not disappear inside an email thread.
Copy-and-use structure
Start with these sourcing BOM columns.
This header set covers configuration, identity, demand, approval, risk, quality, packaging, compliance, supplier response, and the internal decision. Remove fields only when the team has decided they do not affect the purchase.
BOM Revision,Effective Date,Assembly or Variant,Line Number,Reference Designators,Internal Part Number,Manufacturer,Full Manufacturer Part Number,Description,Package,Key Technical Attributes,Quantity per Assembly,Build Quantity,Total Demand,Unit of Measure,Approved Yield or Scrap Factor,Required Delivery Date,Destination,Approved Manufacturer Status,Approved Source Status,Alternate Policy,Approved Alternates,Engineering Owner,Lifecycle Status,Lifecycle Check Source,Lifecycle Check Date,PCN or EOL Flag,Risk Tier,Mitigation Owner,Source Condition,Traceability Requirement,Required Documents,Lot or Date-Code Rule,Inspection or Test Requirement,Pack Format,Full or Partial Pack Rule,Factory Seal Requirement,ESD Requirement,MSL or Dry-Pack Requirement,Mixed-Lot Rule,Required Declaration,Target Market,Supplier Quoted MPN,Supplier Manufacturer,Offered Source,Available Quantity,Lead-Time Basis,Unit Price,Currency,MOQ,Quote Validity,NCNR,Freight Basis,Supplier Exceptions,Selected Supplier,Accepted Exception,PO Reference,Receiving Status,Change or Deviation Record
Use a controlled worksheet.
Keep manufacturer and MPN separate. Lock buyer-owned fields, ask suppliers to complete response columns, and record the release revision before distributing the file.
Before release
Six common BOM-sourcing mistakes to remove.
These are small spreadsheet problems that often become large sourcing, schedule, quality, or receiving problems later.
Raw CAD or ERP export
Inactive variants, DNP lines, partial attributes, and ambiguous names reach suppliers. Create a controlled sourcing view with a clear revision.
Description instead of full MPN
A generic value or family name can return a different package, grade, suffix, or manufacturer. Use manufacturer plus complete orderable MPN.
Substitute assumed to mean equivalent
An unreviewed alternate can change assembly, software, qualification, reliability, or compliance. State the approval route on each line.
No lifecycle or risk owner
The team finds EOL, allocation, long lead, or sole-source exposure only after a quote fails. Time-stamp checks and assign mitigation.
Generic quality note
The supplier cannot tell which source status, documents, packaging, lot evidence, inspection, or testing is required. Make it risk-based and specific.
RFQ exception disappears at PO
Receiving accepts a different source, package, date code, or delivery condition. Carry every accepted exception into the order and receiving plan.
Send the controlled BOM, demand plan, and acceptance rules.
ICNETS can review part identities, organize line-item questions, record the available source and evidence basis, and return a structured quotation response for the actual requirement.
- Complete manufacturer and MPN data
- Required quantity, target date, and destination
- Alternate and source approval rules
- Packaging, traceability, and evidence needs
Use the same requirement from quote through release.
Quality Assurance
See how source context, inspection scope, available evidence, exceptions, and release approval can be agreed before shipment.
Purchasing Experience
Follow the requirement from sourcing clarification and quote review to PO confirmation, incoming review, and release.
Delivery control
Global Shipment
Connect the accepted BOM and PO conditions to packing, shipping documents, carrier handoff, destination, and tracking.
Questions buyers ask before sending a BOM
Q: What is the difference between an engineering BOM and a sourcing BOM?
An engineering BOM defines design intent. A sourcing BOM adds the data needed to buy the right part under controlled conditions: complete manufacturer and MPN, source and alternate rules, lifecycle and risk, demand timing, packaging, traceability, compliance, supplier response fields, and revision ownership.
Q: What fields are essential for electronic component BOM sourcing?
At minimum include BOM revision, reference designators, manufacturer, full MPN, description and package, quantity, required date, destination, alternate policy, lifecycle and risk status, source and quality requirements, packaging rules, and supplier response fields for price, availability, lead time, terms, and exceptions.
Q: Should DNP components be included in a sourcing BOM?
Usually exclude DNP lines from the RFQ view unless they apply to a specific product configuration or option build. If they remain for reference, mark them clearly and make sure they do not enter quantity formulas.
Q: How should approved alternatives be handled?
List every approved manufacturer and MPN as a distinct option with the same controlled fields. If an alternate needs review, require a separately identified proposal and written engineering and quality approval before purchase or shipment.
Q: What does AML mean in component sourcing?
AML commonly means Approved Manufacturer List: manufacturers permitted for a component function. It is different from an approved supplier or vendor list, which controls where the part may be purchased. A manufacturer can be technically approved while a seller is not an approved source.
Q: Why should lifecycle status be included?
A dated lifecycle check identifies parts that may be active, NRND, EOL, discontinued, or affected by a product or process change. It gives the team time to evaluate last-time-buy, alternate qualification, redesign, allocation, storage, and sourcing actions.
Q: Do packaging and MSL information belong in the BOM?
Yes when they affect purchasing, receiving, or assembly. Reel, tray, tube, full pack, factory seal, ESD, moisture barrier, dry pack, and mixed-lot rules can decide whether an otherwise correct part is usable.
Q: When should the sourcing BOM be revised?
Revise it whenever a controlled fact changes: manufacturer or MPN, configuration, quantity, approved alternate, source policy, lifecycle decision, packaging rule, compliance requirement, demand schedule, or accepted deviation. Record the reason, owner, and effective date.
Technical references
- IPC Product Data eXchange resources - BOM, AML, approved supplier, configuration, and change-data concepts.
- IPC-1782B table of contents and scope - risk-based manufacturing and supply-chain traceability.
- NIST IR 8536, second public draft - manufacturing supply-chain traceability and linked records.
- ECIA Guideline for Date Code Marking Format - date-code data elements and traceability context.
- onsemi Product Change Notifications - a manufacturer example of current published product and process change notices.
- Infineon General Recommendations for Assembly of Packages - moisture sensitivity, packaging, and handling context.
- EU Directive 2011/65/EU (RoHS) - official legal reference for restricted substances in electrical and electronic equipment.
- ECHA Candidate List substances in articles - official overview of supply-chain information duties under applicable conditions.