A component End-of-Life (EOL) notice can look like a straightforward purchasing issue: find an alternative, place a last-time buy, and keep production moving. In practice, the decision can affect firmware, PCB layout, compliance work, and the product’s future.
ByteSnap Design’s 2025 ‘Futureproofing Manufacturing’ research found 88% of UK manufacturing professionals experience obsolescence issues at least annually, with 27% facing them quarterly. The cost of upgrading existing systems (61%) and component availability (37%) remain regular concerns.
Procurement teams need a route that protects supply without storing up a larger problem. There are three common options: a controlled patch, a last-time buy, or a wider re-engineering programme.
A patch needs more than matching specifications
A controlled patch is a limited design change that replaces an affected component while retaining the wider product. It suits contained changes with a credible, testable alternative.
The word ‘controlled’ matters. A part with matching headline specifications may still create problems: a capacitor too tall for a custom enclosure, or a FET with different input capacitance that changes switching behaviour. Thermal performance, MTBF, and radio behaviour can also vary between apparently similar parts.
A patch may still need a PCB respin, verification, and recertification. If it also requires broad firmware work, a new module, or a reworked enclosure, the team should assess a redesign instead.
On a battery-powered security product we worked on, the power supply component went obsolete. The circuit was contained enough to patch rather than redesign. We validated the replacement against voltage, current, power, and thermal requirements, then tested the resulting power profile. It ran cooler and cut sleep-mode current to around 75% of the previous design, extending battery life by roughly three years. It still required proper validation and recertification, but a wider redesign would have added cost without solving a problem in the core architecture.
A core module can change the whole calculation
We see the other side just as often. On an industrial product development project, the wireless module and modem reached end of life. That component sat at the centre of the architecture, so a narrow patch wasn’t realistic. We reengineered the design and got roughly 8% more wireless range, while allowing a smaller board and enclosure — a cost-saving opportunity for the client. They placed a last-time buy to keep the existing product in production while the redesigned version went through development and testing.
That last-time buy had a clear purpose and end date. It bridged the transition rather than postponing the decision.
A last-time buy works where demand, service commitments, and the delivery timetable are understood, covering remaining demand, service stock, and a risk buffer against storage conditions and possible redesign delay.
Current market conditions add urgency. Passives that would normally ship from stock are now taking 8 to 10 weeks, and some silicon has moved out to several months, as manufacturers run down built-up inventory and military demand takes priority allocation ahead of industrial and commercial orders. Rising AI data centre demand for RAM and DRAM is adding further pressure in specific categories.
Three questions for engineering
When an EOL notice arrives, procurement should establish the full commercial position and ask engineering:
- Which product or products are affected? One part may appear in several revisions or service assemblies
- How long will it take to find and qualify a replacement? Include design work, testing, documentation, and certification cycles, not just component lead time
- Do we need a controlled patch, a replacement route, or a wider redesign? This depends on the part’s role, available alternatives, testing burden, and remaining lifecycle
A practical benchmark: a 24-to48-hour initial impact assessment, followed by risk classification and a joint decision between procurement, engineering, and the product owner, with executive escalation reserved for genuinely high-risk products.
Procurement should bring demand forecasts, installed-base data, current stock, approved sources, EOL dates, lead times, and product-life expectations to that discussion. Engineering can then assess technical suitability, compliance needs, and programme duration.
Shared accountability prevents weak decisions
Procurement owns supplier information, alternatives, availability, comparative cost, and supply risk.
Engineering owns technical impact, testing, compliance route, and delivery estimate. The product owner should drive the decision, since the result affects the product roadmap and demand plan.
Regulated products need even earlier action. Medical, ATEX, aerospace, and other safety-related equipment can require more time for design change evidence and certification, so any last-time buy needs a defined transition plan from the outset.
An EOL notice should prompt that plan immediately: the affected products, the time required to prove an alternative, and whether the product is still the right platform for its next stage. Most delays come down to under-planning, not the technical decision itself.
A couple of hours spent agreeing the plan properly can save weeks, months — even a product cycle.
This article originally appeared in the Sept/Oct issue of Procurement Pro
