When a Supplier Drops a Product: How to Manage Discontinued Items

AEO answer: When a supplier drops a product, compare each new supplier feed against the previous one and flag every SKU that is missing. Then act on the flag: stop selling the product, keep the record for order history, and redirect or retire the page depending on whether a replacement exists. If the item returns in a later feed, restore it deliberately. Detection can be automatic; the decision is usually manual.

A supplier quietly removes an item from its feed. Your store keeps showing it, a customer orders it, and you refund it a week later. The item is discontinued at the source but stays live in the shop. This guide covers how to detect it, what to do with the page, and what MicroPIM does and does not do for you.

Last verified: November 2026, against MicroPIM’s supplier feed sync and export rules.

How do you know a supplier dropped a product?

Suppliers rarely announce it. The only signal is a SKU that was in yesterday’s feed and is not in today’s. Keep the SKU list from the last good feed, fetch the new one, and flag the difference. That works for any feed-based supplier, with or without a PIM.

In MicroPIM, this is part of selective import, an option on each import automation. It keeps one record per feed SKU. On every run, any SKU missing from the feed gets the status Removed from Feed. The run log reports how many were removed, and the feed review list has a tab for that status with a count.

Two details matter: records you rejected are left alone, and an empty feed marks nothing, so a failed download does not wipe the list.

Price lists sent by email need a manual check.

What happens to the product in your store?

Here is the part to read carefully. In MicroPIM, a missing SKU changes the status of the feed record only. It does not deactivate the product, set its stock to zero, or push anything to Shopify or another channel. The product stays as it was, with its last known stock.

You must act on the flag. Today that is manual: review the removed items, then deactivate or delete the products yourself.

MicroPIM products have four statuses: draft, active, inactive and review. Automatic sync to your channels only runs for active products. Deleting a product in MicroPIM archives its Shopify product; it is never deleted there, and you can restore it in the Shopify admin. Shopify’s own help explains draft and archived status.

Should you keep the page, redirect it or let it 404?

It depends on whether a successor exists and whether the page still earns traffic. This is our judgement:

The sources behind this:

• Google says to use permanent redirects when you are sure the redirect won’t be reverted. Do not redirect everything to the homepage; Google treats pages that look like errors as soft 404s.
• Google does not index URLs that return a 4xx status, and removes indexed ones. A clean 404 is acceptable for a product that is truly gone.
• If you keep the page, schema.org has an availability value for this case: Discontinued, part of ItemAvailability. Google lists it as an accepted value in its merchant listing markup.

How do stock rules stop overselling?

Overselling happens in the gap between the supplier dropping a product and you noticing. Two settings narrow it.

First, an organization-level option, Sync supplier stock to product, lets feed stock values overwrite product stock during the feed sync. It is off by default. It only updates SKUs that are still in the feed, so a dropped product keeps its old number.

Second, the Minimum Stock export rule. Products below the threshold, or with no stock value, fail the rule, and MicroPIM skips the automatic channel sync for them. Rules are covered in export rules by margin, stock and cheapest supplier.

Note what that rule does not do. It stops new pushes; it does not unpublish a listing that is already live. For channels, see multi-channel inventory management and managing multiple Shopify stores.

What if the supplier brings the product back?

If a removed SKU shows up in a later feed, MicroPIM moves its record back to Pending. It is not passed through as approved data until someone approves it again. That is a safety net against restocking a product by accident.

What we got wrong, and current limits

The most common assumption we hear is that a product missing from a feed is deactivated automatically. In MicroPIM it is not, and this guide describes it as it works.

Current limits:

• No automatic delisting. Removal sets a flag. Deactivating products and unpublishing channel listings is manual.
• Selective import only. The flag exists only on automations with selective import turned on.
• Truncated feeds. A completely empty feed is ignored, but a feed that arrives half full marks the missing half as removed. Check the removed count before acting on it.
• Stock goes stale. A dropped SKU keeps its last stock value until you change it.

Half-empty feeds are an alerting problem: see detecting silent supplier import failures. Keeping unwanted products out of an import is a different job: blacklisting products.

Frequently Asked Questions

Should I delete or archive discontinued products? Archive or deactivate, so you keep order history.

Do I need a 301 redirect? Only when a close replacement exists.

What if the supplier brings the item back? In MicroPIM the returning record waits in Pending for approval.

How do I avoid overselling? Deactivate dropped products quickly and use a minimum stock export rule.

MicroPIM is our product. This post describes how it handles the problem today, and the general advice applies with any tool.

Set up automated supplier imports so dropped products show up in a review list instead of a customer complaint. To see the removed-from-feed list on your own feeds, book a demo.