What an approved alternate actually means
An alternate component is not approved merely because it has the same nominal value, package name, or distributor description as the released part. It becomes an approved alternate only after the responsible product authority defines the scope, reviews the relevant differences, accepts the qualification evidence, and updates the controlled product record.
This article presents a risk-based manufacturing workflow. The exact approval authority, tests, sample sizes, and records must follow the product contract, application risk, customer requirements, quality system, and applicable standards. It does not authorize substitutions or replace product-specific engineering review.
Why alternate-part control matters before the shortage occurs
Shortages turn a data-quality problem into a production problem. If the BOM identifies only one manufacturer part number and the team begins evaluating candidates after material is unavailable, the schedule is already exposed. The opposite failure is equally dangerous: an unreviewed “equivalent” is accepted to protect the schedule, then silently becomes the default part for later lots.
A useful alternate strategy therefore separates four states:
- Released production part: the part currently authorized by the controlled BOM or approved vendor list.
- Approved alternate: a defined manufacturer part number authorized for a stated product, revision, site, and operating scope.
- Qualification candidate: a technically plausible option still awaiting evidence or approval.
- Lot-specific deviation: a temporary authorization limited by quantity, lot, work order, date, or another explicit boundary.
The distinction is important because “we used it once” is not evidence that the part is suitable for every product revision, environment, supplier lot, or future build.
1. Start with an exact identity, not a generic description
The decision record should identify the full original and candidate manufacturer part numbers, manufacturer names, package or case codes, approved source, lifecycle status, and the affected BOM line and reference designators.
Do not use a distributor category such as “10 kΩ 1% 0402” as the identity of an approved alternate. Two components sharing that description may differ in temperature coefficient, voltage rating, pulse capability, terminal finish, height, moisture sensitivity, qualification status, marking, or manufacturing location.
IPC’s parts-list data model distinguishes BOM items from approved-vendor/manufacturer-part data, which is a useful reminder that a BOM position and an approved source are related but not interchangeable records. IPC-2588 parts-list schema
2. Classify the reason for the change
The required evidence depends partly on why the alternate is being considered. Record whether the trigger is:
- allocation or lead-time risk;
- end-of-life or product discontinuance;
- manufacturer product or process change notification;
- quality containment or source restriction;
- cost reduction;
- approved second-source strategy;
- regional compliance or material declaration;
- design correction or performance improvement.
A shortage-driven candidate should not bypass the product authority. It may justify an expedited review, but the approval scope and evidence still need to be explicit.
3. Compare form, fit, function—and the limits behind them
Create a side-by-side comparison using current manufacturer documentation. At minimum, consider:
- electrical limits and tolerances across the required operating range;
- absolute maximum ratings and recommended operating conditions;
- timing, startup, leakage, quiescent current, noise, accuracy, or switching behavior relevant to the circuit;
- package drawing, pinout, exposed-pad geometry, height, mass, and polarity or marking;
- thermal resistance, power dissipation, derating, and temperature grade;
- materials, terminal finish, moisture-sensitivity level, reflow limits, and storage conditions;
- required regulatory, environmental, automotive, or customer-specific status;
- lifecycle and notification status.
The review should identify both matches and differences. A table containing only green check marks hides the engineering decision. For every difference, record why it is acceptable, which test covers it, or why the candidate is rejected.
Semiconductor manufacturers use formal change-notification processes when changes can affect fit, form, function, quality, or reliability. NXP, for example, describes risk assessment, qualification planning, success criteria, and change-board approval as part of its process. NXP change management
4. Review assembly-process compatibility
An electrically acceptable component can still create assembly risk. Manufacturing engineering should review:
- land-pattern and stencil compatibility;
- package coplanarity and bottom-termination behavior;
- placement-nozzle and feeder requirements;
- component orientation and machine-recognizable marking;
- baking, floor-life, dry-pack, or storage requirements;
- reflow, wave, selective-solder, press-fit, or cleaning compatibility;
- AOI, X-ray, ICT, programming, and functional-test coverage;
- mechanical clearances, coating, heatsinking, and depanelization exposure.
If a candidate requires a different stencil aperture, reflow window, inspection rule, fixture, or work instruction, the change is larger than a simple AVL entry. The affected production documents and programs must move through change control with the part decision.
5. Check software, calibration, and test interaction
Hardware teams sometimes approve a pin-compatible device without checking behaviors that are visible only after power-up. Review whether the alternate changes:
- device identification or programming algorithm;
- boot timing, reset thresholds, or power sequencing;
- register defaults or firmware configuration;
- sensor offset, gain, linearity, or calibration coefficients;
- communications timing and protocol behavior;
- diagnostic thresholds or functional-test limits;
- electromagnetic, thermal, acoustic, optical, or battery performance.
When a difference can reach the user or product safety case, the evidence must extend beyond assembly inspection. AOI cannot qualify firmware interaction, and a functional test cannot prove every environmental or lifetime requirement unless its scope was designed to do so.
6. Confirm source authorization and traceability
Technical equivalence does not compensate for uncertain origin. Record the approved supplier route, purchase order, manufacturer and distributor identities, lot or date code where required, quantity, receiving evidence, and chain-of-custody documentation.
Texas Instruments recommends purchasing through the manufacturer or authorized distributors because material from unauthorized sources can introduce authenticity, handling, warranty, and reliability risk. TI anti-counterfeit guidance
If business conditions require another sourcing route, treat that as a separate risk decision with documented authentication, inspection, test, and approval requirements. Do not let an alternate-part approval imply automatic approval of every supplier.
7. Build a qualification plan around the actual differences
Avoid two extremes: repeating every possible product test for a low-risk passive change, or approving a higher-risk semiconductor based only on datasheets. Use the difference analysis and application risk to select evidence.
Possible evidence includes:
- current datasheet and package-drawing comparison;
- manufacturer PCN, qualification report, material declaration, or lifecycle notice;
- incoming inspection and marking review;
- solderability or process trial;
- X-ray or cross-section when hidden-joint risk warrants it;
- parametric bench comparison across relevant operating limits;
- programming and functional-test comparison;
- thermal, EMC, environmental, mechanical, or reliability testing;
- pilot-lot monitoring and first-article approval;
- customer, design authority, quality, or regulatory approval.
Define acceptance criteria before testing. “No issues found” is weaker than a record stating the test conditions, measured limits, sample identity, result, and approver.
Infineon’s supplier change-notification guidance illustrates the type of evidence a controlled change may require: affected parts and sites, before/after comparison, risk assessment, qualification plan and results, date-code planning, and compliance updates. Infineon supplier change notification
8. Approve a scope, not just a part number
The approval record should state where the alternate may be used. Useful scope fields include:
| Scope field | Decision to record |
|---|---|
| Product | Assembly part number and revision range |
| BOM position | Item number and reference designators |
| Original part | Manufacturer and full manufacturer part number |
| Alternate | Manufacturer and full manufacturer part number |
| Approved source | Manufacturer-direct or named authorized distributor route |
| Manufacturing scope | Site, line, process, or contract manufacturer restrictions |
| Product scope | Region, option, customer, or end-use restrictions |
| Effective boundary | Start date, revision, work order, quantity, or lot |
| Qualification evidence | Comparison, tests, reports, and sample identity |
| Approval | Named engineering, quality, customer, or regulatory roles as required |
If the evidence supports only one build, issue a deviation with an expiry or closure condition. Do not enter the candidate as a permanent alternate merely to simplify purchasing.
9. Keep lot control visible on the production floor
Once approved, the material decision must reach planning, purchasing, receiving, kitting, setup, inspection, test, and traceability records. At minimum:
- update the controlled BOM/AVL and revision history;
- prevent mixing where the product or test plan requires lot separation;
- identify the issued manufacturer part and lot in the work order or material record;
- connect the first-article and test evidence to the actual alternate lot;
- update AOI, X-ray, ICT, programming, or functional-test instructions if needed;
- define whether unused deviation material can move to another order;
- monitor early production and close any temporary controls.
The purpose is to make the approved decision reproducible. A buyer’s email or handwritten feeder note is not a substitute for the released manufacturing record.
A practical alternate-part decision matrix
Use one row per BOM position and candidate. The review should make gaps visible rather than compressing the conclusion into “equivalent / not equivalent.”
| Review area | Evidence | Result choices | Required action when open |
|---|---|---|---|
| Identity and source | Manufacturer P/N, source, lifecycle, lot traceability | Match / Difference / Unknown | Resolve exact identity and source |
| Electrical performance | Datasheet comparison and circuit limits | Pass / Test / Reject | Define bench or product test |
| Mechanical fit | Package drawing, height, mass, pinout | Pass / Test / Reject | Land-pattern or enclosure review |
| Assembly process | MSL, finish, reflow, feeder, inspection coverage | Pass / Trial / Reject | Process trial and instruction update |
| Firmware and test | Programming, defaults, timing, calibration, limits | Pass / Test / Reject | Update software or test package |
| Compliance and quality | Required declarations, grade, PCN/qualification data | Pass / Approval / Reject | Obtain evidence or authority approval |
| Product validation | FAI, functional, thermal, EMC, environmental, reliability | Complete / Planned / Not required | Record rationale, criteria, and result |
| Change control | Scope, revision, deviation, approvers | Approved / Conditional / Rejected | Release or close the decision record |
Use the editable companion workbook: PCBA Alternate-Part Qualification Decision Matrix. It includes owner, due date, evidence link, decision, approval, risk-flag and readiness fields.
When should an approved alternate be reviewed again?
Define review triggers in the change record. Common triggers include:
- a manufacturer PCN or process/site transfer;
- a new product revision or changed operating condition;
- package, die, material, terminal-finish, or test-flow change;
- a new supplier route or loss of traceability;
- lifecycle status change or discontinuance notice;
- test escape, field failure, quality alert, or abnormal yield signal;
- customer, regulatory, or end-use requirement change;
- use outside the originally approved product, site, region, or lot scope.
Manufacturer PCN programs are useful inputs, but the product owner still decides whether and how the change affects the assembled product. TI recommends beginning impact analysis as soon as a PCN is received so that teams can assess the notified change before it disrupts production. TI product change notification guidance
Final approval questions
Before releasing an alternate to production, confirm:
- Are the original and alternate identities exact and controlled?
- Are all meaningful differences visible, with an acceptance rationale or test?
- Does the source provide the required authorization and traceability?
- Have assembly, firmware, inspection, and functional-test impacts been reviewed?
- Are acceptance criteria, sample identity, results, and approvers recorded?
- Is the approval scope permanent, conditional, or limited to a defined lot?
- Did the updated decision reach purchasing and the production release package?
An alternate-part program is successful when supply flexibility increases without making the product baseline ambiguous.