Sourcing guide / Sourcing insights

How to source obsolete electronic components with confidence

A practical workflow for identifying an obsolete component, reviewing possible replacements, and requesting documentation without skipping engineering judgment.

Editorial view of semiconductor components prepared for a sourcing review
Illustrative editorial image for a component sourcing review.Alamo / Field notes
On this page

The short version

What to take away.

  • Confirm the complete part identity and application context before asking for supply.
  • Distinguish NRND availability for existing designs from an obsolete product that is no longer in production.
  • Treat replacements as an engineering review item and request traceable evidence without making suitability guarantees.

Introduction

When a familiar component is no longer easy to order, the first instinct may be to search for the same part number and ask for a price. A better approach is to create a clear record of the requirement, the lifecycle status, and the evidence needed for a responsible sourcing decision. This keeps procurement, engineering, and quality teams aligned while the part conversation develops.

Confirm the part identity

Start with the exact manufacturer part number, including suffixes, package codes, temperature or grade designations, and any ordering characters. A near match can have a different electrical, mechanical, or documentation profile. Capture the information from the approved bill of materials, drawing, prior purchase record, or device label, then compare those records for inconsistencies.

A useful request also includes the intended application context. Note the assembly or board reference, required quantity, target use date, package, environmental conditions, and any customer or internal requirements. If the original record is incomplete, say what is known and what still needs confirmation instead of filling gaps with assumptions.

  • Confirm manufacturer and complete ordering code.
  • Preserve package, grade, revision, and suffix details.
  • Record the source document and the person or team confirming the requirement.

Separate NRND from obsolete

Manufacturer lifecycle language matters. A product marked not recommended for new designs, often called NRND, may still be available for existing designs. An obsolete product is no longer in production. Those labels lead to different conversations, so do not treat every difficult-to-find part as obsolete without checking the manufacturer’s current product page and lifecycle information.

This distinction is especially important when a line is still supported for an existing design but is not a good choice for a new design. Ask the sourcing team to preserve the exact status wording and the date of the page or notice reviewed. Consult the manufacturer’s exact product-change notices for any part-specific information that may affect the requirement. Do not infer a notice period or an availability window from a general rule.

Build a replacement review path

If the original device is obsolete, a replacement may be worth evaluating, but it is not automatically interchangeable. Compare the proposed device against the actual design need: electrical ratings, pinout, package dimensions, thermal behavior, operating range, timing, programming, and related application requirements. Review the full datasheet and relevant manufacturer documentation, not just a distributor description.

Create a simple comparison table with one row for each requirement and a source reference for the proposed answer. Mark open items clearly. Engineering should approve the replacement path, including any testing, board changes, firmware work, or customer review that the design requires. Procurement can then request the specific item that engineering has reviewed rather than asking a supplier to decide equivalence.

For aerospace-specific work, this workflow is not approval or airworthiness advice. The responsible engineering, quality, and regulatory teams must make those determinations under their own procedures and records.

Ask for evidence and traceability

A sourcing request should explain what documentation is needed for evaluation. Depending on the program, that may include a manufacturer datasheet, lot or date information, packing details, certificates or declarations requested by the buyer, and a clear chain of custody. State which documents are required before a purchase decision and which can follow for review.

Use precise language around inspection. A supplier may describe its incoming checks or available records, but no sourcing conversation should promise that a component is genuine or suitable before the buyer’s own acceptance process. Ask what evidence is available, who issued it, and whether the document identifies the exact manufacturer part number and lot.

Keep the request consistent across suppliers. If one response uses an alternate package, a different suffix, or a substitute document, place it in a separate review row rather than blending it into the original line.

A few useful answers

Common questions.

Is every hard-to-find part obsolete?

No. A part may be difficult to locate because of channel, regional, or documentation issues while the manufacturer still supports it. Check the manufacturer’s current lifecycle wording for the exact ordering code.

Can a supplier choose a drop-in replacement?

A supplier can suggest a candidate, but engineering should compare and approve it against the design requirements. A similar package or headline specification does not establish interchangeability.

What should be in the first sourcing request?

Include the complete manufacturer part number, quantity, timing context, application or assembly reference, package and grade details, documentation needs, and any known lifecycle concern. Identify open questions instead of guessing.

Sources & further reading

  1. Texas Instruments product life-cycle categories
  2. Texas Instruments product change notifications

About the author

Alamo Direct Editorial

The Alamo Direct Editorial team creates practical context for electronic component sourcing conversations.

About Alamo Direct

Your next sourcing conversation

Bring us the part. Keep the context.

One MPN or a complete BOM, start with the information you already have.

Request sourcing support