Obsolete & EOL Component Sourcing
Support legacy equipment, service inventory, lifetime demand, and redesign planning with an order-specific review of the exact part number, lifecycle context, available supply, source condition, lot information, evidence, alternatives, and delivery requirements.
Start With the Actual Status, Not a General “Old Part” Label
NRND, an EOL notice, obsolete status, allocation, and a long-lived approved design can create different purchasing actions. Current status and notice details should be checked against current manufacturer information when available.
NRND
The device may remain available, but a new design may be directed toward another family. Existing programs still need exact part, lifecycle, forecast, and replacement planning.
EOL Announcement
Review notice dates, affected ordering codes, last-order or last-shipment context, remaining demand, internal approvals, and the program horizon.
Obsolete Component
Available supply may depend on remaining inventory. Source basis, condition, packing, lot context, traceability, evidence, and exceptions become central to approval.
Legacy Approved Part
A currently active replacement may still require validation against the board, firmware, package, pinout, qualification, documentation, and service requirements.
Define the Program Need Before Evaluating Supply
A one-time repair, five-year service commitment, lifetime purchase, and recurring production requirement should not be evaluated on the same quantity, timing, evidence, or alternate basis.
Complete Part Identity
Manufacturer, full ordering code, package, suffix, revision, grade, packing format, and approved-description context.
Demand Horizon
Immediate quantity, minimum usable quantity, forecast, repair rate, project lifetime, and required dates.
Installed-Base Context
Board or equipment revision, host, firmware, qualification, approved bill of materials, and change authority.
Acceptance Requirements
Date or lot preference, condition, packaging, traceability, documents, inspection, testing, and exception limits.
Alternate Authority
Whether replacements may be reviewed, which differences are prohibited, and who owns validation and approval.
Four Sourcing Routes for a Mature or Discontinued Part
The practical route depends on lifecycle status, remaining demand, current market search, source condition, evidence, timing, replacement authority, and the cost of system change.
Search Remaining Supply
Review the complete ordering code across available supply routes without reducing the search to a similar family name.
- Exact MPN and package
- Available quantity and timing
- Supply condition and lot context
Plan a Lifetime or Staged Buy
Segment immediate, service, safety, and forecast quantities so the purchasing decision reflects the program horizon.
- Immediate and reserve quantities
- Full, partial, or staged release
- Storage and replenishment context
Evaluate an Approved Alternate
Compare a candidate replacement without assuming that a similar function, description, or footprint makes it interchangeable.
- Electrical and timing limits
- Package, pinout, and software
- Qualification and validation owner
Combine Supply and Redesign Timing
Use available exact-part supply to support the installed base while a replacement, board revision, or product transition is reviewed.
- Bridge quantity and target dates
- Priority equipment or customers
- Transition checkpoints and exceptions
A Reviewable Obsolete Component Sourcing Process
Each stage creates a buyer checkpoint so an available quantity is not treated as an approved supply before identity, condition, evidence, terms, and exceptions are understood.
Requirement Intake
Record the exact MPN, quantity, timing, program horizon, destination, alternates, and evidence requirements.
Lifecycle Review
Check current status, notices, affected ordering codes, approved BOM context, and available manufacturer information.
Supply Search
Review available quantities, source basis, condition, packing, lot or date information, timing, and open questions.
Evidence Scope
Agree identity, labels, packaging, visual, marking, traceability, documentation, and suitable testing requirements.
Buyer Approval
Compare quantity, price basis, validity, timing, quality scope, alternate differences, and exceptions.
Release & Delivery
Confirm packing, labels, documents, carrier, destination, tracking, and receiving handoff.
Make Condition and Exceptions Visible Before Approval
Older supply can vary by source, storage history, packaging, lot, labels, and available records. The appropriate inspection and evidence plan should be agreed for the actual component and risk—not copied from a generic checklist.
Identity & Packaging
Complete MPN, manufacturer, package, quantity, labels, packing format, seals, and external condition.
Lot & Traceability Context
Available lot or date information, photos, records, documents, source context, and stated limitations.
Inspection & Testing
Visual, marking, microscopic, X-ray, electrical, functional, or other suitable methods when available and agreed.
Exceptions & Release
Results, deviations, open questions, customer acceptance criteria, and approval before shipment.
What an Obsolete Component Quote Should Make Clear
The decision should not be reduced to unit price. Quantity, supply condition, evidence, timing, commercial validity, alternate differences, and exceptions can materially change the usable value of an offer.
| Decision Field | What Should Be Visible | Buyer Question |
|---|---|---|
| Complete Identity | Manufacturer, full MPN, package, suffix, revision, grade, and packing format | Is this the exact approved ordering code? |
| Lifecycle Context | Current status, notice context, affected codes, and available manufacturer information | Which program action does the status require? |
| Quantity & Supply | Offered quantity, full or partial basis, condition, source basis, and availability assumptions | How much usable demand can this offer cover? |
| Lot & Evidence | Available date or lot information, packaging, traceability, records, photos, inspection, and tests | Is the evidence suitable for this source and risk? |
| Commercial Terms | Currency, unit basis, price breaks, validity, payment, taxes, freight, and exceptions | Can the offer be approved before conditions change? |
| Timing & Delivery | Lead-time basis, dispatch estimate, carrier, destination, documents, and split-delivery options | Does the supply support the actual program schedule? |
| Alternate Proposal | Technical differences, validation scope, qualification, lifecycle, and approval owner | What must be tested and approved before substitution? |
Treat a Cross-Reference as a Candidate, Not an Automatic Substitute
A replacement decision belongs to the customer's engineering and approval process. Compare the details that can affect system behavior, manufacturing, qualification, service, and documentation.
Function & Electrical Limits
Architecture, ratings, tolerance, timing, analog behavior, protection, and operating conditions.
Package & Pinout
Footprint, pin assignment, dimensions, thermal path, assembly, and board compatibility.
Software & Platform
Registers, firmware, drivers, controller, initialization, memory, and validation context.
Qualification & Lifecycle
Grade, temperature, approvals, change records, documentation, and expected product horizon.
Turn a One-Time Search Into a Managed Legacy Supply Plan
Segment demand by urgency and purpose. A repair buffer, committed production, safety reserve, and redesign bridge can have different quantities, dates, evidence, storage, and release requirements.
Protect Immediate Requirements
Prioritize line-down, repair, service, and confirmed production quantities.
Cover the Program Horizon
Review forecast, failure or usage rates, reserve policy, lifetime demand, and staged purchasing.
Approve the Transition Path
Coordinate exact-part supply with replacement evaluation, redesign timing, validation, and documentation.
Questions Before Sending a Legacy Requirement
Start with the complete part number and the program need. The actual sourcing, evidence, alternate, commercial, and delivery response depends on the available supply and your acceptance criteria.
Can I submit one obsolete part number?
Yes. Include the full MPN, manufacturer, package or suffix, required quantity, minimum usable quantity, target date, destination, installed-base context, and evidence requirements.
Does EOL always mean no stock is available?
No single assumption fits every part. An EOL notice concerns the manufacturer's product lifecycle, while actual remaining supply depends on the current search, ordering dates, inventory, source condition, and market situation.
Can YURUNOX support a legacy BOM with many manufacturers?
Yes. Submit the BOM with quantities, priority lines, forecast, approved manufacturers, alternate authority, target dates, destination, and quality requirements so each line can follow the appropriate route.
Is an available lot automatically acceptable?
No. Review the exact identity, source basis, condition, packaging, available lot information, traceability, evidence, inspection scope, commercial terms, and exceptions against the actual requirement.
Can a newer part be used as a direct replacement?
Not automatically. A candidate replacement should be compared for function, electrical limits, timing, package, pinout, software, qualification, lifecycle, documentation, and customer engineering approval.
Can obsolete components be shipped in partial quantities?
Full, partial, staged, and split delivery can be reviewed when available. Confirm the minimum usable quantity, release priority, packing, documents, carrier, destination, freight basis, and receiving plan.
Send the Obsolete MPN, Legacy BOM, or Lifetime Demand
Include the full ordering code, quantity, required date, program horizon, installed-base context, approved alternatives, destination, and evidence requirements. YURUNOX will organize the sourcing questions around the actual continuity decision.