An engineering bill of materials says what the product is designed to contain. It does not say which manufacturer part procurement may buy, which seller is approved to supply it, what paperwork must come with the order, or which revision a quotation covers. A sourcing plan adds those answers in layers that sit beside the EBOM, so the engineering definition stays clean while purchasing gets everything it needs.
The structure that works for most new products is simple to describe. Start from a released EBOM baseline with unique internal item numbers. Link each item to one or more approved manufacturer parts, link each approved part to one or more approved sources, keep prices and stock as dated records in their own table, and control every change by effectivity. The rest of this guide fills in the detail.
Where the EBOM ends and the sourcing plan begins
PTC describes the EBOM as a hierarchical representation of the assemblies, subassemblies and components that describe the finished product, created at the start of design and updated as the design changes. It feeds engineering, sourcing, manufacturing, quality, regulatory and service work. Siemens draws the line to the manufacturing BOM (MBOM): the MBOM lists what the factory needs to build the shippable product and is distinct from the EBOM, though the two must stay consistent.
For a PCB assembly, the EBOM holds the bare board, fitted parts, connectors and mechanical items engineering has defined. The MBOM adds solder paste, panel quantities, labels, trays and packing material. Do not force those manufacturing details into the EBOM just to get a complete quote. Send the EBOM baseline with a separate note of manufacturing assumptions, so that different EMS providers can propose their own process without editing the product definition.
Four linked tables
A small team can run this in controlled spreadsheets; a larger one will use PLM and ERP. The tool matters less than stable identifiers, edit permissions and change history.
1. Engineering item master
One row per internal item. These fields cover most electronics products:
| Field | Why it is there |
|---|---|
| Internal item number | Stable company identifier, independent of any supplier |
| Revision and status | Working, in review, released or obsolete |
| Description and specification | Value, tolerance, rating, material, package |
| Parent, quantity, reference designators | Where it is used and how many |
| Criticality | Safety, compliance, quality or continuity class |
| Data link | Schematic, datasheet or drawing that controls it |
"10k resistor" is not a specification. Power rating, tolerance, temperature coefficient, voltage rating and package all decide whether two parts can be swapped.
2. Approved manufacturer parts
Each internal item maps to one or more exact, orderable manufacturer part numbers (MPNs), each in its own record with the manufacturer, full MPN including suffixes, qualification state, lifecycle status, the date that status was checked, package, material declarations and any agreed deviation. Mark alternates as approved, conditionally approved, under test or rejected.
Lifecycle status is a dated fact. Texas Instruments, for example, labels each product preview, active, not recommended for new designs (NRND), last time buy or obsolete, and for the last three it advises new designs to consider an alternate. IEC 62402:2019 places obsolescence management across the whole life of an item, including design. Store the status, its source and the check date, not just a coloured cell.
3. Approved vendors for each part
Part approval and seller approval answer different questions. Engineering approves an MPN; quality and procurement approve who may sell it and on what conditions. For each part-and-vendor pair, record the supplier's legal name and approved site, whether it is franchised for that manufacturer and territory, the traceability and certificate documents required, the warranty and failure-analysis route, approved ship-from locations and the controls for any non-franchised purchase. The approved vendor list guide covers how to maintain this table, and checking a distributor's authorisation explains what evidence to file.
4. Commercial and risk records
Never overwrite engineering data with today's price or stock. Create a quote record linked to the MPN, the vendor and the EBOM revision, holding currency, unit price by quantity, duty and tax basis, MOQ, standard pack, lead time, validity, stock location, cancellation terms and the date captured. Keep a separate risk log with severity, likelihood, owner, due date, mitigation and residual approval.
This separation mirrors electronics data standards. IPC-2581 can carry BOM content, change history, logistics headers and an approved vendor list as distinct data objects alongside the design data. IPC's revision table lists Revision C, dated November 2020, as the current IPC-2581 revision (checked October 2026). You do not need to adopt IPC-2581 to copy the idea, but confirm the revision before naming it in a contract.
Eight steps to build the plan
Step 1: Define the configuration
Name the model, hardware revision, regional variants, options and build quantity. A quote for "the controller" is ambiguous if the India and export versions use different radios, power supplies or labels. Decide whether variants get separate EBOMs, a configurable BOM or effectivity rules, and write it down before any supplier sees a file.
Step 2: Clean the design export
Export from the controlled EDA or PLM source. Remove placeholder values, duplicate items, obsolete alternates and inconsistent manufacturer names. Check that reference-designator counts match quantities, and that fitted, not-fitted and variant-only positions are explicit. Close every "to be decided" line before a production RFQ, or define the technical envelope and the person who will decide.
Step 3: Normalise identifiers
Keep internal item numbers, MPNs and supplier stock codes in separate fields. Spreadsheets quietly turn part numbers into dates or scientific notation and drop leading zeros, so format those columns as text. Use controlled lists for manufacturer names, units and lifecycle states, and check package and grade suffixes against the datasheet. A family-level entry cannot be ordered or traced.
Step 4: Add sourcing quantities
For each line, calculate extended quantity per build, then add approved allowances for attrition, samples, destructive tests and service stock. Model prototype, validation, pilot and production builds separately. Engineering may need four screws per unit while the pilot order rounds up to a full bag; keep the two numbers apart so purchasing assumptions never alter the design. Planning components for EVT, DVT and PVT builds covers the stage-by-stage quantities.
Step 5: Qualify alternates
Engineering compares electrical, mechanical, thermal, firmware and qualification requirements, then classes each alternate as drop-in, layout-supported or redesign-required. A cross-reference tool listing a part is a lead, not an approval. Record the test evidence and the EBOM revision the approval applies to.
Step 6: Map compliance evidence
Start from the finished-product compliance plan, then attach the component evidence it needs. In India, check whether the finished product falls under the BIS Compulsory Registration Scheme (Scheme-II) and which standard applies. Component certificates support the technical file; they are not product approval. Record MPN, document revision, issuer and verification date so expired declarations can be replaced.
Step 7: Release a controlled RFQ package
The package states the EBOM number, revision and release date; build quantities and schedule scenarios; approved MPNs and whether substitutes are allowed; the quote template, currency and commercial basis; traceability, date-code and packaging rules; delivery point and Incoterm; manufacturing assumptions and fabrication files; and the deadline and clarification route. Send it through a controlled link and log who received which revision. Emailing a changed BOM under the same filename invites suppliers to quote the old one. For PCB and PCBA work you can also describe the requirement on forUdyog's QUICK RFQ page.
Step 8: Analyse and approve the baseline
Compare total landed cost, including MOQ and pack rounding, freight, non-creditable duties and taxes, programming, test, tooling and excess stock. Flag lines with one approved MPN, one approved source, a lifecycle concern, a long lead time or a high extended value, and give each an owner before pilot purchasing. The approved baseline references the EBOM revision, the approved-parts revision, vendor approvals and quote dates.
Revisions and effectivity
A change record states what changed and why, which assemblies are affected, what happens to existing stock, what qualification is needed, who approved it and the build, lot, date or serial number from which it applies. Released baselines stay readable and are never edited to look like the new one.
When an MPN changes, look beyond the BOM line: schematic, footprint, firmware, test limits, compliance evidence, drawings, labels, work instructions and open purchase orders may all move. Decide whether existing stock is usable, reworkable, returnable or scrap. Keep a single owner for EBOM release, role-based edit rights, frozen released revisions and formal approval for every substitution.
Release checklist before pilot buying
- Every fitted item has a unique internal number and a controlled specification
- Quantities agree with reference designators and variants
- Each MPN has a qualification state and a dated lifecycle status
- Approved vendors are linked to specific parts, not held as a general company list
- Every quote names the revision, quantity, validity, MOQ, pack and lead time
- Compliance documents are tied to exact MPNs and revisions
- Critical lines have an owner and a mitigation action
- MBOM additions and EMS assumptions are documented separately
- Supplier transmittals and changes can be traced
Questions teams ask about EBOM sourcing plans
Can a startup run this in spreadsheets?
Yes, provided it keeps stable IDs, restricted editing, revision history, validation rules and backups. As variants and team size grow, moving to PLM and ERP reduces the manual reconciliation that causes most errors.
Is an approved manufacturer list the same as an approved vendor list?
No. The manufacturer list says which part can fulfil an engineering item. The vendor list says who may sell that part to you, with what traceability and on what terms. Some software merges them on screen, but the two approvals still have different owners.
When is the EBOM ready to send out?
When the configuration and revision are clear, quantities reconcile, every line has an exact MPN or a controlled specification, substitution rules are written and open items have owners. A prototype enquiry can carry stated assumptions; a production RFQ should not. Once quotes come back, use the method in comparing component quotes to put them on equal terms.
Sources
Each source was opened and checked on the date shown. Rules, rates and company details change, so confirm anything time-sensitive before you act on it.
- What is an Engineering Bill of Materials (eBOM)?
- Manufacturing bill of materials (MBOM)
- IPC Standards Revision Table
- IPC-2581B: Generic Requirements for Printed Board Assembly Products Manufacturing Description Data and Transfer Methodology (scope and contents)
- IEC 62402:2019 Obsolescence management
- Product life cycle
- Scheme-II: Compulsory Registration Scheme
Continue on forUdyog
- Component distributors
- Components and electronics sourcing
- Prototype vs production manufacturing
- Post a QUICK RFQ
Have a specific requirement? Describe it on the QUICK RFQ page.
