Last-Time-Buy Windows for Discontinued Automation Parts: Why

Last-Time-Buy Windows for Discontinued Automation Parts: Why the Date on the EOL Letter Matters

By the AO Control sourcing desk. Last updated September 27, 2026. Editorial review: V.4.3.

A last-time-buy date is the only window in which factory-fresh units of a discontinued PLC, drive or HMI can be ordered at standard terms. After the LTB date passes, the only paths back to a genuine unit are surplus stock, last-resort pre-buys, and a documented cross-reference built on the successor family — and each of those paths is slower, narrower, and priced per line rather than per order. We are an independent industrial-automation desk, so we quote LTB and post-LTB requests per line, with condition disclosed on every line and lead time quoted per order; the EOL letter is the calendar that drives the whole process.

What an end-of-life letter actually states

When a manufacturer announces that a product family is being phased out, the announcement is not a single event. It is a dated schedule. Three dates matter, and they refer to three different things — buyers confuse them because all three are written on the same page.

The announcement date is the day the manufacturer publishes the phase-out. From that day, no new design-in is recommended, and the order-book begins its taper. The last-time-buy date (LTB) is the last day on which a purchase order placed through the manufacturer or its franchised channel can be accepted at standard terms. After the LTB date, the franchised channel stops accepting orders; what exists in the channel after that date is whatever was placed before the cutoff. The end-of-life date (EOL) — sometimes called "active phase-out complete" — is the last day on which the manufacturer will ship a unit that was ordered before the LTB date. Anything not already on a purchase order before the LTB date must, from that point on, be sourced from secondary-channel stock.

A fourth date sometimes appears in the same letter: the repair-support end date and parts-support end date, which govern how long the manufacturer will keep spares, sub-assemblies, and repair service available for units already in the field. Repair-support is not the same as product availability — a drive that is sold-out and no longer orderable can still be repairable for years afterward. This separation matters because a buyer who only reads "discontinued" and skips the dates will treat the product as unavailable when, in fact, repair support is still active.

The three dates that drive every EOL decision

For the maintenance planner, only two of those dates actually move decisions: the LTB date and the end of repair-support. The EOL date sits between them and is rarely the binding constraint.

The last-time-buy date drives stocking decisions. It is the only point at which new factory-fresh units can be ordered under the manufacturer's normal terms. A buyer who needs a 10-year spare-parts reserve for a machine that will run until 2034 must place the LTB order before the cutoff — after that, the only route back to factory-fresh units is a non-standard allocation request, which the manufacturer will consider only on a case-by-case basis (and not always successfully).

The repair-support end date drives the obsolescence budget. Once repair support ends, the cost of keeping a machine running shifts from "buy the failed module" to "redesign around the failed module or replace the affected subsystem." That shift happens whether or not you have spare stock on the shelf.

The end-of-life date drives documentation. After this date, the manufacturer freezes the product record for new design-in; technical advisories stop; firmware updates end. Units already shipped continue to function, but no further engineering effort is committed to the line.

For a buyer facing a phase-out, the practical question is: what do I need to do, and by when? The answer is anchored to those three dates.

Why buyers misread the last-time-buy deadline

The single most common mistake is treating the LTB date as a soft target. It is not soft. Three things go wrong when it is treated that way.

First, the LTB date is enforced by the channel, not by the buyer. Once it passes, no amount of persuasion reaches the original franchised channel. The order simply is no longer accepted. A buyer who decides in October that they want a 5-year spare reserve for a drive with a December LTB date is already too late — the December order would have to be placed in November at the latest to clear the manufacturer's order-acceptance window.

Second, LTB dates are sometimes published on a region-by-region basis. The same family can have a Q3 LTB in one sales region and a Q4 LTB in another, depending on local stock positions and channel rotation. A buyer working from a translated EOL letter that omits the region footnote will assume a date that does not apply to their order.

Third, the LTB date is set per SKU, not per family. A drive family can have a 2027 LTB on the common frames and a 2026 LTB on a rare variant — and the rare variant is often the one a maintenance planner is most likely to need. The family-wide announcement letter is the wrong place to look for variant-level deadlines. The right place is the SKU list that accompanies the announcement, and even then the right answer is to confirm against the manufacturer's regional office, because variant lists are also subject to revision before the LTB date.

A fourth trap is treating "last-time-buy" as a synonym for "last shipment." It is not. LTB closes the order book; the shipment follows weeks or months later depending on the production slot. A buyer who orders at the LTB date and expects delivery next week is using the wrong mental model.

How an independent sourcing desk quotes a last-time-buy order

We are an independent industrial-automation distributor and sourcing desk. When a customer sends us a list of part numbers and tells us some of them are at LTB, the workflow is a defined one and it does not bend around the urgency.

Step one — read the EOL letter against the part list. We map each requested SKU against the manufacturer's published LTB date, the regional office where it applies, and the variant-level SKU list. If a part number is not on the variant list — if the manufacturer never formally listed it for LTB, or has withdrawn the line without announcing it — we treat it as a normal secondary-channel search and not as an LTB order. Customers sometimes assume any line on a phase-out family is at LTB; the assumption does not hold.

Step two — separate genuine LTB lines from adjacent lines. A 30-line BOM will typically include 3-6 lines on an LTB schedule and the rest on active production. We quote the LTB lines separately because the conditions differ. Active lines can be quoted against the normal franchised-channel cost basis; LTB lines are quoted against whatever genuine stock we can locate across our supplier network, with condition disclosed per line.

Step three — quote condition per line. Every line in our quote carries a condition: new surplus (factory-fresh unit from channel stock, never installed), refurbished (bench-tested against the manufacturer's published test profile, with the test record attached), or used (removed from a known service environment, tested to power-on only). The three conditions are not interchangeable, and the warranty on each is different. A buyer who needs a true LTB equivalent must accept that the closest match may be new surplus, not new factory-fresh.

Step four — stand on a defined quotation. Lead time, price, and availability are quoted per order against the lines we have actually confirmed. We do not commit to a delivery window at the quote stage, because the channel sources for genuine stock move between quote and order — what we have today may be gone tomorrow. The buyer's commitment is to the line list and the conditions; the rest is per order.

Step five — pre-shipment checks. For LTB and post-LTB stock, every unit goes through a documented pre-shipment check: visual condition, marking legibility, firmware version where readable, and where the manufacturer's datasheet calls for it, a bench power-on or I/O loop test. The pre-shipment photo record and the test outcome travel with the unit; the customer's engineering team has something to verify against when the unit arrives.

What we cannot do with a last-time-buy quote

The boundaries are explicit and we write them into every LTB conversation so that the customer is not surprised later.

We cannot place the LTB order on the customer's behalf with the original manufacturer. LTB is an order the customer has to commit to directly with the franchised channel; we are not in that channel, and an order placed through us for an LTB unit would itself not be LTB-compliant. We can help the customer draft the purchase order, or quote parallel genuine-stock options from the secondary channel, but the LTB order itself sits with the customer.

We cannot hold stock at our facility for an indefinite period while the customer decides whether to buy. Genuine stock on the secondary channel moves quickly because the same stock is visible to every other buyer in the market; we cannot guarantee that a unit we locate today is still available next week. Reservation windows are per quote and per order, not per project.

We cannot promise a price-protection clause. If the customer orders three units at $X today and the same unit moves to $X-plus-delta next month, the second quote reflects the second market, not the first.

We cannot substitute silently. If a customer's LTB part number turns out to be unobtainable in genuine stock, we will not silently cross it to a "looks similar" SKU and ship it. We will report the gap and let the customer decide between a documented cross-reference (level 1 or 2 only, with all twelve axes reviewed), a refurbish-and-test path on a returned unit, or a redesign around the affected subsystem.

We cannot make the discontinuation go away. The deadline on the EOL letter is the manufacturer's deadline, not ours, and no commercial relationship on our side changes it.

A practical LTB scenario: an ABB drive on the cusp of phase-out

A maintenance planner running a 2009-era bottling line writes in with three ABB drive part numbers on a list. Two are still active production. The third is on a published ABB migration schedule: the family that built the original unit is being phased out in favour of the successor family, and a published LTB date sits in the calendar. The customer asks whether we can hold three units against an order that will not be placed for another six weeks.

The answer comes in three parts. The two active-production lines go through the normal route — quoted against the franchised-channel cost basis, lead time per order, condition new. The third line, the one at LTB, is a different problem. ABB's published migration documentation for that family describes the successor family as the formal replacement, with a documented migration tool and a shared parameter map. That is the documented cross-reference part of the answer, not a drop-in statement: the migration tool is a project, not a parameter-copy. Footprint, control-board architecture, parameter structure, and option-module compatibility all need to be verified per build through the ABB Drives Migration tool before any substitute is committed to, not assumed at series level.

For the genuine-stock path on the LTB line, we quote the part number against whatever surplus and pre-owned stock we can locate. The condition is disclosed per line. A bench test is offered where the unit's datasheet calls for it; the test outcome travels with the unit. The customer gets a quote with a defined expiration and a defined condition on every line, and a parallel documented-cross-reference option that lists the axes we have verified and the axes we have not.

Three practical points come out of this scenario that apply to any LTB conversation, not just ABB:

The LTB line is quoted separately from the active lines, and the conditions on each line are stated on the quote.
The documented cross-reference is offered as an option, not as the answer; the customer still owns the engineering decision about whether the migration project is acceptable in their machine's lifecycle.
The pre-shipment test record travels with the unit, so the customer's engineering team has something concrete to verify against on arrival.

How to plan around an LTB you have not decided to take

A maintenance planner who is not yet ready to commit to an LTB order still has options, but each one has a different cost shape.

Surplus and pre-owned stock — units that left the franchised channel at some earlier point and are now visible on the secondary market. Condition per line (new surplus, refurbished, or used), warranty per quote, lead time per order. This is the path most buyers end up taking when they discover the LTB date after it has passed.

Documented cross-reference — for parts where the manufacturer has published a migration guide to a successor family. The cross-reference is a starting point, not an answer; the customer's engineering team has to verify against the successor datasheet and against the machine's actual wiring, parameter set, and program before any commitment. The 12 axes we always check before recommending a cross-reference: form/fit outline and mounting; dimensions; terminal and interface assignment; electrical parameters; function and I/O specification; firmware, hardware version and engineering-software compatibility; communication protocol; mechanical parameters; environmental class and EMC; ingress protection and temperature range; materials and construction; certifications and lifecycle. On an LTB-driven cross-reference, firmware_version and certifications_lifecycle are the two axes that most often come back as unknown rather than matched — the manufacturer has not published a function-state table for the legacy product, and the customer's qualification process is the only path to closure.

Redesign around the affected subsystem — replacing the obsolete module with a more recent equivalent, accepting that the wiring, parameter set, and program will need engineering work. This is the path for a machine that has a long remaining service life and where the LTB reserve is large enough to make the engineering effort worthwhile.

No action — a planner who judges the LTB impact as low and the spare reserve as adequate may decide to do nothing, accepting that future failures will be addressed as they occur. This is a valid decision if the spare-reserve calculation is honest; it is a poor decision if it is wishful.

What is not an option is pretending the LTB date does not exist. Once it has passed, the franchised channel is closed, and any genuine unit the buyer locates thereafter is by definition secondary-channel stock.

When the documented cross-reference is the wrong answer

A maintenance planner facing an LTB will sometimes be tempted to skip the LTB order entirely on the strength of the manufacturer's published cross-reference. There are at least three situations where that decision is unsafe, and where the right answer is to take the LTB reserve even if the cross-reference looks complete on paper.

First, functional safety paths. If the obsolete module sits in a safety circuit — an emergency-stop loop, a guard interlock, a light-curtain interface — the cross-reference is not a substitute for the LTB reserve. Safety integrity levels (SIL/PL) are determined by the as-built system, not by the cross-reference document; a migration that crosses into a different safety architecture requires its own qualification, and the right body to make that call is the customer's safety engineer, not a sourcing desk.

Second, firmware-locked programs. Where the legacy module is loaded with a customer-specific program that has been validated against a known firmware revision, replacing it with a successor family means re-validating the program against the new firmware and the new parameter set. That re-validation is engineering work; the cross-reference does not perform it.

Third, certification-tied installations. Where the machine carries a third-party certification (CE machinery, UL panel listing, marine class, ATEX zone rating) that was issued against a specific module list, swapping in a successor module is a re-certification event. The cross-reference document is not the certification body.

In each of these cases the right answer is to take the LTB reserve at standard terms while the LTB window is still open, even if the cross-reference looks complete. A documented cross-reference is a tool; it is not a replacement for engineering judgement.

Always verify any cross-reference against the original manufacturer datasheet and your own qualification process. The 12 axes listed above exist because looks-similar on a cross-reference table is not the same as fit-for-purpose on a working machine. Where the verification cannot be closed inside our desk, the customer's engineering team owns the final call.

Data Notes

Market context for the LTB conversation is drawn from public product-lifecycle announcements issued by major industrial-automation manufacturers in 2024–2026, including ABB's published migration program for the ACS800 family toward the ACS880 successor. Where a specific EOL letter is referenced in the article, the verification target is the manufacturer's published product-lifecycle page for the relevant SKU, not the family-level marketing migration document. Our role is to read the letter, not to write it; we do not publish the manufacturers' letters, and we do not substitute our own judgement for the manufacturer's stated dates.

Buyer action

For LTB and post-LTB requests, the fastest path to a useful answer is to send the part number list to our procurement desk with three columns: the machine or line the parts run in, the year the machine was commissioned, and the expected remaining service life. From those three columns we can map each line against the manufacturer's LTB schedule, separate active-production lines from LTB lines, and return a per-line quote with condition disclosed on every line. Lead time is quoted per order; price is indicative on the quote and confirmed on the order; and we screen end users and end uses, classify before quoting, and decline transactions that cannot be screened.

Disclaimer

This article describes how an independent industrial-automation sourcing desk approaches last-time-buy requests. It is not legal, certification, or engineering advice. EOL letters, regional LTB dates, and cross-reference documents are published by the manufacturer; the customer is responsible for confirming the dates and the migration path against the manufacturer's current product-lifecycle page. Functional safety, third-party certification, and program-validation decisions are made by the customer's engineering team; this desk does not hold EAC/TR CU, ISO 13485, UL or other certifications, and does not perform repair, recertification, or qualification work. Conditions on every quote line are stated on the quotation; what is not on the quotation is not part of the offer.

FAQ

What is a "last-time-buy" date for an automation part?

It is the last day on which a purchase order for a factory-fresh unit can be placed through the manufacturer's normal franchised channel at standard terms. After the LTB date, the manufacturer stops accepting new orders; whatever stock remains in the secondary channel is whatever was placed before the cutoff, plus whatever was previously returned or withdrawn.

Is "last-time-buy" the same as "discontinued"?

No. "Last-time-buy" closes the order book; "discontinued" (EOL) is the last shipment date for orders already placed. Repair support and parts support typically continue for years after EOL. A buyer who reads only "discontinued" may wrongly assume the part is unavailable when, in fact, repair support is still active.

After the LTB date passes, where can a discontinued drive or PLC be sourced?

Three paths remain: surplus and pre-owned stock from the secondary channel (condition disclosed per line, warranty per quote); documented cross-reference to a successor family (a starting point for the customer's engineering team, not an automatic fit); or a redesign around the affected subsystem where the wiring, parameters, and program are reworked to accept a more recent equivalent. Each path has a different cost shape and a different engineering footprint.

Does the manufacturer guarantee spare-part availability until the LTB date?

No. The LTB date guarantees only that an order can be placed through the franchised channel on or before that date. Production slots, minimum order quantities, and lead times all still apply. A buyer who orders on the LTB date expecting immediate delivery is using the wrong mental model — the unit ships when the production slot is filled, often weeks later.

Why does the LTB window for an automation part seem so short?

The window is determined by the manufacturer's production planning and channel-rotation schedule, not by the buyer's maintenance horizon. A 12-month window is typical for industrial drives and PLC families; variant-level windows for less-popular SKUs are sometimes shorter. The window is not negotiable through a distributor; it is set by the manufacturer.

How should a buyer plan their LTB order volume?

By the machine's expected remaining service life and the failure rate of the part in question, not by gut feel. For a machine expected to run until 2034 with a drive family that has a 2027 LTB, a 7-year spare reserve is a defensible planning target. For a machine expected to retire in 2028 against the same LTB, a 1-year spare reserve is more defensible. The order volume, the condition, and the storage conditions for any genuine-stock units all follow from this calculation.

What if the part number we need is not on the published LTB list at all?

Then it is not formally on LTB, even if the family is. A part can be withdrawn from the franchised channel without ever appearing on a published LTB schedule. In that case, the right path is a secondary-channel search against the SKU and a documented-cross-reference check, not an LTB quote.