By the time a bill of materials (BOM) is released, most of the sourcing outcome has already been decided. A scarce microcontroller, a single-source connector or an awkward package is now designed into the PCB, the firmware, the enclosure and the certification plan. Swapping it is no longer a purchasing task; it means redesign and retesting.
The work described here happens earlier, while the architecture is still flexible. It turns product requirements into a preliminary sourcing BOM, screens the critical parts for lifecycle and supply risk, decides what kind of alternate each one needs, checks the package against your assembler's capability, and ties component choices to the compliance the product will need. The output is a set of constraints engineering designs within, not a purchase list.
Why the decision belongs to the design phase
A part is more than its datasheet function. It comes with an orderable part number, a package, an MOQ, a lead time, one or more factories, a lifecycle status, compliance documents and a set of authorised channels. All of those affect cost, schedule and how long you can keep building.
IEC 62402:2019, the international standard on obsolescence management, includes developing strategies to minimise obsolescence during design as part of the process (checked October 2026). The point holds even for a short-life consumer product: design choices decide how many options remain when supply changes.
Early sourcing work should answer four questions while they are cheap:
- Can the chosen parts support prototype, pilot and production quantities?
- Could engineering swap a part without changing the PCB or the firmware?
- Will the buying route give traceability and change notices?
- Will the architecture meet the product's obligations in India and any export market?
Start with a one-page brief and named owners
Before anyone picks a part, write a short product and supply brief that engineering, product, quality and purchasing all approve: markets, operating environment, service life, annual volume range, pilot quantity, target launch, planned build location, warranty period and cost target. Add technical constraints such as temperature range, ingress protection, radio interfaces, isolation, battery chemistry and how long software will be supported. The forUdyog industrial sourcing brief is a useful template for the commercial half.
Then name who decides what:
- Engineering: functional suitability and alternate qualification.
- Purchasing: supplier evidence, quotes and commercial limits.
- Quality: traceability, inspection and change control.
- Compliance: the standards and market-access list for the product.
- Product or programme management: volume scenarios and decision dates.
Without that split, you end up with an alternate that is available but never technically approved, or one that is approved but has no valid source.
Nine pieces of pre-development work
1. Map functions before part numbers
Divide the product into functions: processing, memory, power conversion, sensing, connectivity, protection, user interface, electromechanical parts and the power source. For each, write the minimum requirement and the room for flexibility. For a controller, that might be the interfaces, memory headroom and temperature range. Doing this first stops a favourite development board from quietly setting the production architecture.
2. Draft a sourcing BOM
Add candidate MPNs as full orderable codes, including package and packing suffixes. A family name is not enough: temperature grade, reel quantity, plating and memory size can all change with the suffix. Useful columns are function, manufacturer and MPN, package and critical ratings, lifecycle status with the date checked, alternates and their status, estimated annual usage, authorised sources, compliance documents needed, quoted lead time and MOQ with the quote date, and the risk owner. Keep assumptions visibly separate from verified facts; "should be available" is not a dated status.
3. Screen lifecycle before technical approval
Reject obsolete and last-time-buy parts for a new design unless an exception is documented. Treat "not recommended for new designs" as a real warning. TI's lifecycle definitions steer new designs away from NRND and last-time-buy products towards alternates, and its change-notice policy gives 12 months for last orders after a discontinuance notice (both checked October 2026). Twelve months is short when requalification takes six.
For products that must stay in production for years, look for part-specific longevity commitments. NXP's Product Longevity programme, for example, lists participating products with a minimum availability of 10 or 15 years, counted from each product's launch date (checked October 2026). Check the exact part, its start date and the conditions; never read a programme as a brand-wide guarantee.
4. Decide the alternate level for each critical part
Choose one of three levels before layout:
- Drop-in: same footprint and pinout, with electrical and firmware compatibility verified.
- Layout option: the PCB carries a second footprint or a stuffing option for a different package or circuit.
- Architecture fallback: a different subsystem could meet the requirement, with planned redesign effort.
A distributor's "equivalent" flag is not an engineering approval. Compare absolute maximum ratings, operating limits, timing, tolerances, package dimensions, thermal behaviour, firmware dependencies and qualification grade. Passives and connectors need the same discipline: a resistor alternate must match resistance, tolerance, power, voltage, temperature coefficient and package, and a connector must also match the mating part, keying, plating and retention. The cross-referencing guide goes further.
5. Check packages against assembly capability
A very small or highly integrated package saves board area but can narrow your alternate options, raise the assembly capability you need, and make inspection and rework harder. Ask the intended EMS partner to review fine-pitch BGAs, bottom-terminated parts, moisture-sensitive devices, board finish, impedance control and anything needing special storage or programming. Weigh the smaller board against stencil, X-ray, rework and yield costs. The guide to selecting PCB assembly capability lists the questions.
Where electrical and reliability needs allow, prefer common footprints and ratings that several manufacturers support.
6. Tie compliance to the BOM
Compliance belongs to the finished product, but component choices decide whether it can be met. Build a matrix by market and product category before you choose power supplies, batteries, radio modules, plastics and safety parts.
For India, check whether the finished product is on the BIS Compulsory Registration Scheme list and which Indian Standard applies (checked October 2026). Depending on the product, radio approval, telecom certification, battery rules, e-waste obligations or energy labelling may also apply; the guide to planning an electronics supply chain in India sets out the import-side gates. For the EU, the European Commission's RoHS page states that the directive currently restricts ten substances in covered equipment, subject to scope and exemptions. Ask for declarations tied to the MPN and revision; a logo on a website is not evidence.
7. Turn demand into ranges
Give suppliers ranges, not one unsupported annual number. Define prototype, validation, pilot and steady-production scenarios with ramp dates. For each critical part, work out usage per unit, yield loss, service quantity and engineering samples, then model low, base and high demand. The high case shows capacity and cash needs; the low case shows MOQ and excess risk. Time long-lead orders against design maturity so you are not buying for an unstable revision without a deliberate decision.
8. Line up sources before asking for production stock
For active parts, start with the manufacturer or its authorised distributors. ECIA describes buying from authorised distributors as the best guard against counterfeit components. Confirm authorisation for the manufacturer, product line and territory. Ask each candidate whether the quote is for the exact MPN, where the stock physically is, what lot and date-code traceability will ship, what the MOQ and quote validity are, whether manufacturer warranty survives, and how change and end-of-life notices reach you.
9. Set up change monitoring
Register critical parts for manufacturer change and discontinuance notices, and route them to engineering, quality and purchasing together. Record each decision, the BOM revisions affected, the validation needed and the date it takes effect. A notice sitting in one buyer's inbox is not monitoring.
Score the parts the same way every time
Rate each part low, medium or high on lifecycle and longevity, number of approved alternates, number and type of approved sources, lead time against the build plan, package difficulty, inventory exposure, compliance or qualification impact, and the consequence of a field failure. The high-rated parts form the critical-parts list, and each needs an owner, a mitigation, a decision date and a sign-off on residual risk. A single-source MCU can be a sound choice when it gives essential function and strong lifecycle support. What should never pass is a single source nobody examined.
Gates during development
Concept gate. Product, market, volume and service-life assumptions are written down. Each critical function has candidate architectures, rather than one favourite part. Compliance categories and the main tests are identified.
Schematic gate. Exact MPNs and packages have a dated lifecycle check. Critical parts have an alternate level or an approved exception. Authorised sources, MOQ and indicative lead times are recorded, and the EMS has reviewed assembly constraints.
Layout gate. Footprints and stuffing options keep the agreed flexibility. High-risk parts have quotes and samples. Compliance-sensitive parts have their document requirements, and someone owns change monitoring.
Pilot gate. BOM revision, approved vendor list and firmware revision agree. PO terms define lot and traceability evidence. Demand scenarios and cancellation exposure are approved, and incoming inspection is ready.
Once the pilot gate is passed, the founder-level pre-PO checks in the electronics procurement checklist take over.
Three questions teams ask
Should purchasing choose components before engineering does?
No. Engineering approves technical suitability; purchasing brings lifecycle, availability, source and commercial evidence. Critical parts should be a joint decision with quality and compliance in the room.
How many alternates does a part need?
There is no fixed number. One fully qualified drop-in is worth more than several unchecked cross-references. Concentrate on parts with serious failure consequences, long lead times, unusual packages or weak lifecycle support.
When should production parts be ordered?
When lead time, design maturity, cancellation terms and inventory exposure together justify it. Samples and constrained parts may need early action, but committing to production stock against an unstable BOM needs explicit approval.
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.
Continue on forUdyog
- Product design and prototyping
- Electronics engineering services
- Selecting PCB assembly capability
- Industrial sourcing brief
Have a specific requirement? Describe it on the QUICK RFQ page.
