HARD-TO-FIND & OBSOLETE COMPONENT SOURCING
When a component is hard to find, the next decision matters more than the search.
- Keep the exact MPN, revision and package visible
- Separate exact-match sourcing from alternative evaluation
- Set the approval point before a material change moves downstream
Keep an approved design or service build moving.
Use this route when the requested manufacturer part number must remain unchanged and the immediate task is to investigate a sourcing path for that identified line.
Explore options without treating them as automatic replacements.
Use this route when your team may evaluate an alternate, provided electrical, mechanical, lifecycle and approval constraints are made explicit first.
Make the current buy fit the wider program decision.
Use this route when a discontinued component affects future builds, maintenance demand or a redesign conversation beyond one purchase.
START WITH THE ACTUAL CONSTRAINT
“Hard to find” and “obsolete” are not the same sourcing question.
A part can be difficult to source because the available routes are uncertain, while an obsolete part creates a lifecycle decision even when inventory may still be found. Naming the situation helps the RFQ ask for the right next step.
Availability, price, lead time, condition and route suitability are order-specific questions. They should be confirmed for the actual part, quantity and requirements—not assumed from a general page.
The exact MPN is required for this build.
Share the full manufacturer part number, revision or suffix, package, quantity, target date and the reason an exact match matters. This keeps a constrained-part enquiry tied to the actual requirement.
An alternative may be possible—but needs technical review.
State which parameters, interfaces, software dependencies, approvals or lifecycle conditions cannot change. A proposed substitute remains a candidate until your responsible team evaluates and approves it.
The component creates an ongoing program exposure.
Describe whether the line supports a repair, a one-time build, recurring production or a redesign decision. That context helps distinguish a short-term procurement task from a longer lifecycle conversation.
MAKE THE CONSTRAINED-PART REQUEST DECISION-READY
Three pieces of context make a scarce or discontinued part easier to evaluate.
The goal is not to turn every request into a long form. It is to provide the details that prevent the search from drifting away from the decision your team actually needs to make.
Identify the exact line
Include the manufacturer, complete MPN, suffix or revision, package and any approved equivalent references. A partial description can be useful, but it should not be presented as a confirmed match.
Protect the non-negotiables
Record the requirements that cannot move: application, critical parameters, firmware or interface dependencies, form factor, condition requirements and required documentation.
Define the commercial decision
Set quantity, delivery destination, timing priority, whether alternatives may be discussed and the person or team who must approve a material difference.
A CONTROLLED SOURCING PATH
Investigate supply without losing the original requirement.
For a hard-to-find or obsolete electronic component, a clear path keeps availability investigation, alternate discussion and buyer approval from becoming one unstructured conversation.
Preserve the original identity.
Capture the requested MPN, revision, package and quantity before discussing a source. For a BOM, flag the constrained lines rather than letting them disappear inside a generic parts list.
Set the permitted sourcing route.
Decide whether the enquiry is exact-match only, whether technically reviewable options may be surfaced, or whether the immediate task is simply to document the gap.
State the evidence and condition requirements.
Where condition, packaging, date-code, records or an inspection scope matter to your approval process, include them in the request before an order-specific decision is made.
Escalate a material difference for approval.
A change in part identity, condition or other critical requirement should lead to the buyer’s defined approval step. It should not be treated as an unspoken substitute.
CHOOSE THE RIGHT REQUEST TYPE
Different situations call for different questions.
Use the structure below to make the request precise. It is not a compatibility decision or a promise that any route, alternative or stock position will be available.
| Situation | Include in the Request | Next Decision |
|---|---|---|
| Exact component required |
Full MPN, revision or suffix, package, quantity, target date and exact-match restriction. | Assess an order-specific sourcing route without changing the requested identity. |
| Alternate may be evaluated |
Exact MPN plus non-negotiable electrical, mechanical, interface, lifecycle and approval limits. | Route technically relevant candidates to your designated reviewer; do not assume equivalence. |
| Obsolete line affects future builds |
Expected demand window, maintenance or production use, current BOM context and redesign or change-control constraints. | Decide whether the need is a current buy, a continuing supply question or a separate redesign discussion. |
| High-consequence order |
Condition, packaging, date-code, documentation, inspection and escalation requirements that your own process requires. | Define the evidence and approval conditions before progressing to an order decision. |
KEEP THE NEXT STEP RELEVANT
A constrained component problem can lead to three different conversations.
Need to identify the part or family?
Use the Line Card to organize the manufacturer, category or partial-MPN context before you send the sourcing request.
Need to assess a possible alternative?
Use Technical Advisor to frame the design-fit question and define which constraints must remain under your team’s control.
Ready to source the identified line?
Send the MPN or BOM with quantity, timing, destination and the exact-match or alternative boundary that applies to the purchase.
HARD-TO-FIND & OBSOLETE PARTS FAQ
Questions buyers ask when the approved part is constrained.
These answers help separate an exact-match sourcing request from an alternative or lifecycle decision before the inquiry reaches the RFQ stage.
Can you help with an obsolete electronic component?
Provide the complete manufacturer part number if it is known. Otherwise describe the function, input range, output voltage and load, package or footprint limits, application, required quantity and target timing. Add a schematic, datasheet or package photo whenever it can clarify the requirement.
Should I ask for an exact match or an alternative?
A functional request can be reviewed more effectively when it includes the power-tree context and the boundaries an alternative must respect. State the input source, rail targets, current profile, control or sequencing needs, package constraints and who can approve a different part.
Does a proposed alternative mean it is compatible?
Start with the parameters that would make a substitute unsuitable: input and output range, peak and steady load, package, pin compatibility where relevant, protection behavior, battery architecture, thermal limits and start-up or control requirements.
What quality or documentation details should I include?
Yes. Keep each line clear and state whether the parts work within one system. A short note on the battery, USB or adapter input, system load and any shared approval conditions helps prevent unrelated lines from being evaluated without context.