For retailers and wholesalers whose ranges change faster than their listings

Discontinued Products: Stopping Every Channel at the Right Moment

Launching a product gets a project plan. Ending one usually gets an email. The buyer decides not to reorder, or the supplier quietly drops a line from its price file, and from there each channel finds out on its own schedule. The website keeps taking backorders, the marketplace listing keeps selling the last unit twice, the ad budget keeps sending traffic to a product that cannot be bought, and a trade customer’s standing order keeps arriving for something nobody will ever supply again.

The fix is rarely a clever tool. It is a small number of lifecycle statuses, one system that owns them, and a clear rule for what each status changes in purchasing, in each sales channel, in pricing and on the product page. This page sets out that model, how to detect supplier discontinuations without treating a missing feed row as zero stock, how to retire product URLs without losing search traffic, and how to keep enough history that a warranty claim three years later still resolves.

Review Your End of Life Process (03) 9003 0111

The Shape of the Problem

6 statuses

Cover most product lifecycles

Active, last buy, run out, clearance, discontinued and archived

1 owner

For the lifecycle status

Usually the ERP or PIM; every channel reads it, none sets it

7 to 10 settings

Change when a SKU winds down

Reorder, backorder, preorder, price, listing, feed, page visibility and more

2 to 4 weeks

Typical supplier silence threshold

A rough guide for acting on a SKU missing from a supplier feed

Why Discontinued Products Keep Selling

In our experience the cause is almost never one system. It is the gap between them, and the fact that ending a product is treated as an event instead of a sequence.

Discontinued is not one state

A product does not go from on sale to gone in a day. There is a period where you will not reorder but still have stock to sell, a period where you sell what remains and refuse backorders, perhaps a clearance phase at a lower price, and then a point where it is no longer sold but must still exist for returns. When the only flag available is an active or inactive tick box, staff either switch it off too early and strand stock, or too late and oversell. Most lifecycle problems start with a status model that is too coarse.

Each channel has its own off switch

Shopify has product status and per location inventory policy, the POS has its own active flag, Amazon and eBay have listing states and quantity, Google Merchant Center has availability and exclusion, and the B2B portal has price lists and customer catalogues. Each one is switched separately, often by a different person. Unless one status drives all of them, someone has to remember every switch for every SKU, and the switch most often forgotten is the one on the channel that sells least, which is exactly where the oversell happens.

Suppliers rarely announce discontinuations

Many suppliers simply stop including a SKU in their stock or price file. Integrations then do one of two wrong things. Some treat the missing row as zero stock immediately, which hides products during an ordinary feed hiccup. Others keep the last known quantity forever, which sells stock the supplier no longer holds. Neither is a decision. The useful signal is how long the SKU has been missing, measured as a last seen date, with a threshold that triggers a review rather than an automatic delisting.

Deleting a product deletes its history and its traffic

Removing a product from the store breaks its URL, its reviews and the inbound links pointing at it, and removing it from the ERP can break the link from old invoices to the item that was sold. Customers return goods, claim warranties and buy spare parts years after a line ends. A product that ranks for its model number may still bring useful search traffic long after the last unit sells. Archiving keeps all of that. Deleting throws it away to tidy a list nobody needed tidied.

How a Reliable End of Life Process Works

Six elements. A small catalogue might need only the first and a weekly report; a large multichannel range usually needs all six.

Status set once, read everywhere

One lifecycle status, one owner

Choose the system that owns the status, usually the ERP for stocked ranges or the PIM where product data is managed there, and add a lifecycle field with a small fixed list: active, last buy, run out, clearance, discontinued, archived. Each status has an effective date and a reason code such as supplier deleted, range review or superseded. Every channel and every integration reads the status from that one place. Nobody switches a listing off by hand in a channel admin, because the next sync would undo it or, worse, it would quietly disagree with everything else.

A written matrix, then automation

A rule per status, per channel

Write a matrix with statuses down the side and settings across the top. Last buy stops automatic reorder suggestions but keeps everything on sale. Run out stops backorders and preorders, so channels sell on hand stock only and the inventory policy changes from continue selling to deny. Clearance applies the clearance price and promotion labels. Discontinued sets quantity to zero on marketplaces and ends the listings, excludes the item from Google Shopping, and hides it from search and collections while the page decision is made. Agreeing this matrix on paper is most of the work.

Delistings caught, hiccups ignored

Supplier last seen detection

Every supplier feed import records, per SKU, the date it was last present. A missing SKU keeps its last stock figure for a short grace period, then is shown as unavailable from that supplier, and after a longer threshold, often two to four weeks for weekly files, it raises a task for the buyer: confirm discontinuation, find a replacement or chase the supplier. A whole feed arriving with a large share of SKUs missing is treated as a broken file, not a mass discontinuation, and stops before it changes anything.

No channel sells stock that is gone

Sequenced wind down by stock

Stock does not run out on every channel at once, so the sequence matters. As on hand quantity approaches zero, the channels with the slowest sync or the highest oversell cost come off first: marketplaces with cancellation penalties and the B2B portal, then Google Shopping so ad spend stops, then the website, with the POS last because it sells what is physically on the shelf. A safety buffer per channel holds back the final few units, so the slowest channel to sync cannot sell the unit another channel has already sold.

Search value and customers kept

URL and replacement handling

When a product reaches discontinued, its page gets a decision rather than a default. If it has search demand, reviews or useful specifications, keep it live as an unavailable page with the replacement product prominently linked. If there is a direct successor, a 301 redirect to it carries most of the value. If not, redirect to the closest category. Return 404 or 410 only when nothing useful exists. The old SKU is linked to its successor in the ERP so the relationship survives for reporting, support and future redirects.

Returns and warranty still resolve

Archive, never delete

Archived products stay in the ERP, the accounting system and the order history with their full details, costs, serial or batch records and supplier. They disappear from sale and from search, but invoices, credit notes, warranty registrations and spare parts lookups still find them. Channel listings may be removed entirely once sold out, but the ecommerce product record is archived where the platform allows, rather than deleted, so old orders keep their line details and returns can be processed against the original item and price.

End of Life Situations, Before and After

Task	Traditional	Done Properly	Notes
Buyer decides not to reorder	Email to the team	Status set to last buy in the ERP	Reorder suggestions stop immediately; every channel keeps selling until the status moves on to run out.
Supplier drops a SKU from its file	Shown as zero or never noticed	Last seen age triggers a buyer task	A short absence is treated as a feed gap; a sustained one becomes a decision with an owner.
Last units on hand	Website still takes backorders	Run out status denies backorders	Channels sell physical stock only, with a buffer held back on the slowest channel to sync.
Clearing remaining stock	Prices edited per channel	Clearance price pushed from one place	Marketplace and Google Shopping prices match the website, so feeds are not disapproved for mismatch.
Product page after sell out	Deleted, leaving a 404	Kept, redirected or retired by rule	Pages with search demand stay with a replacement link; the rest redirect to the successor or category.
Replaced by a new model	Two unrelated products	Old SKU linked to successor	Drives the redirect, the upsell on the old page and like for like sales reporting across the change.
Trade customer on a standing order	Order raised for unavailable item	Account manager alerted early	Customers with the SKU on contract lists or repeat orders are contacted before it runs out, with an alternative.
Warranty claim two years later	Item not found in the system	Archived record still resolves	Original invoice, cost, supplier and serial details are all still there for the claim to be assessed.

What to Get Right

Open orders and backorders you can no longer supply

When a SKU is discontinued, find every open order, backorder and preorder for it on every channel before the status changes, not after the complaint. Contact the customer with a clear choice, such as a substitute or a refund. Under the Australian Consumer Law, a business that accepts payment and cannot supply within the time promised or within a reasonable time should generally refund. Refund promptly to the original payment method. This is general information, so confirm your obligations with your adviser.

Mass redirects to the home page

Redirecting hundreds of retired product URLs to the home page is a common shortcut and a poor one. Search engines tend to treat it like a missing page, and the customer who searched for a model number lands somewhere irrelevant. Redirect to the successor or the closest category, keep high value pages live with a replacement, and return 410 or 404 only for pages with no useful destination. Keep the redirect map in the integration, not in someone’s spreadsheet.

Stock write down and clearance accounting

Stock that is cleared below cost, written down or written off has accounting and possibly tax consequences, and the valuation method in your ERP determines how the numbers fall. Agree with your accountant how slow and discontinued stock is reviewed, when a write down is recorded, and how clearance sales and disposals appear in the ledger. The integration should report discontinued stock on hand and its cost each month so finance sees the exposure before year end.

Marketplace listing rules

Marketplaces each have their own rules about ending, deactivating and relisting products, and some measure seller performance on cancellations caused by unavailable stock. Ending a listing can lose its history and reviews, while keeping it at zero quantity may preserve them for a return. Check the current rules for each marketplace you sell on, and decide per channel whether discontinued items are ended or held at zero, rather than applying the website’s approach everywhere.

B2B contracts and price lists

Trade customers may have the SKU on a contract price list, a standing order or an approved product list inside their own procurement system. Removing it silently can break their ordering and, depending on the contract, your obligations. Run a report of every customer with the item on a price list or recent repeat orders when the status moves to last buy, so account managers can agree substitutes and contract changes before stock is gone.

Building what a status field and a report would do

For a single store with a few hundred SKUs and no marketplaces, a lifecycle field in the ERP or product admin, a saved filter, and a weekly report of products at run out with stock and open orders may be all that is needed. Many platforms already deny overselling when inventory policy is set correctly. Automation earns its keep when there are several channels, supplier feeds or B2B price lists to keep in step, not before.

How Yes AI Approaches End of Life Management

Audit what happens today

We take a handful of recently discontinued SKUs and trace what every channel, feed, price list and report did with them. The audit usually shows which switch is forgotten and how often stock is oversold or stranded.

Status model and matrix agreed

We work with buying, ecommerce, finance and customer service to agree the statuses, their owner and what each changes per channel, and write it down before anything is built, including who may move a SKU between statuses.

Built and monitored by us

Status propagation, supplier last seen tracking, channel sequencing and redirect handling run on a managed cloud automation layer we operate, with a log of every status change, what each channel did and any channel that failed to confirm.

Handed over with clear ownership

Your team owns the statuses and the decisions. We hand over the matrix, the redirect map and weekly exception reports, and recommend the simpler option wherever a native platform setting or an existing connector already does the job well.

From Ad Hoc Delisting to a Lifecycle Process

Five steps. The status model and core channel rules are typically in place within four to six weeks, with supplier detection and SEO handling following.

Trace recent discontinuations

Follow real SKUs through every channel, feed and price list to see where they kept selling or were switched off too early.

Agree statuses and the matrix

Six statuses, one owning system, and the change each status makes in purchasing, every channel, pricing and the product page.

Propagate status to channels

Store, POS, marketplaces, Google Shopping and B2B price lists driven from the owner, with buffers and sequencing by stock.

Add supplier and order checks

Last seen tracking on supplier feeds, plus reports of open orders, backorders and B2B customers affected by each change.

Handle URLs and archive

Redirect and retention rules for product pages, successor links, archived records and a monthly discontinued stock report.

FAQ

How do we stop selling a discontinued product on every channel at once?

You usually should not stop everywhere at once. Set a lifecycle status in the system that owns your products, and let each status drive every channel. When stock is still on hand the product keeps selling, without backorders. As the last units go, the channels with the slowest sync or the harshest cancellation penalties come off first, and the POS last. The goal is that no channel can sell a unit another channel has already sold.

What statuses should a product lifecycle have?

Most businesses manage with six: active; last buy, where reordering stops but sales continue; run out, where only on hand stock is sold and backorders and preorders are refused; clearance, where a reduced price applies; discontinued, where the product is no longer sold; and archived, where it is hidden but kept for returns, warranty and reporting. Fewer statuses blur decisions. More usually means statuses nobody uses consistently, so start with six and add one only when a real decision needs it.

Should we delete discontinued products from our website?

Rarely. Deleting breaks the URL, loses reviews and can break the link from old orders to the product. Keep the page live with a replacement suggestion if people still search for it or it has useful reviews or specifications. Use a 301 redirect to the successor or closest category otherwise, and a 404 or 410 only when nothing useful exists. Avoid redirecting everything to the home page, which helps neither customers nor search rankings.

Our supplier stopped sending a SKU in its feed. Is it discontinued?

Not necessarily. A missing row may be a feed error, a temporary stock issue or a genuine delisting. Record the date each SKU was last seen in the feed. After a short grace period show it as unavailable from that supplier, and after a longer threshold, often a few weeks for a weekly file, ask the buyer to confirm with the supplier. If a large share of the feed vanishes at once, treat the file as broken.

What happens to customers with backorders on a discontinued item?

Find them before the status changes and contact them with a choice, typically a substitute or a refund. Under the Australian Consumer Law, if you have taken payment and cannot supply within the promised or a reasonable time, the customer is generally entitled to a refund, and a slow or reluctant refund turns a stock problem into a complaint. This is general information, not legal advice, so confirm specifics with your adviser.

Should reviews move from an old product to its replacement?

Only where the products are genuinely equivalent, such as a packaging change or a new supplier code for the same item. Showing reviews written about a different product as if they apply to its successor can mislead customers, and misleading representations are a risk under the Australian Consumer Law. For a new model, keep the old reviews on the old page, link to the successor, and let the new product earn its own.

Do we need an integration for this or just a better process?

If you sell through one store and one POS with a modest catalogue, a lifecycle field, correct inventory policy settings and a weekly report of run out products with stock and open orders may be enough. Integration becomes worthwhile when several channels, supplier feeds, Google Shopping and B2B price lists all need to change in step, because that is where manual switching breaks down and oversells or stranded stock follow.

Find Out Where Your Discontinued Products Keep Selling

Book a call. We trace a few recently discontinued SKUs through your channels, feeds and price lists, show you where each one kept selling or stopped too early, and give you a priced plan. If a status field and a weekly report will do, we will say so.

Book an End of Life Review (03) 9003 0111

All discussions held in confidence. Australian-based consultants.