Before you delete a listing on Amazon: what disappears for good, and what gets stranded

Every few months, someone on your team opens Seller Central, sees three SKUs for the same product and two pack sizes you stopped making, and starts deleting. It feels like housekeeping. On Amazon, one delete can strand stock you paid to ship in. Another can take a product page down with its reviews and history. With Black Friday a few weeks out, that is an expensive way to tidy up.

Three things you are really deleting

Seller Central tends to show these as one row. Before you delete anything, pull them apart.

• The ASIN is the ID Amazon gives a product page. There is one page per product, and every seller who offers that product shares it.
• The SKU (stock keeping unit) is your own code for the product. Several SKUs can point at the same ASIN, usually by accident: an old upload, a relabelled batch, a SKU created when the barcode changed.
• The offer is the price, quantity and fulfillment method attached to a SKU. Units you send to FBA (Fulfillment by Amazon, where Amazon stores and ships your stock) are tied to the SKU that sent them in.

Closing a listing switches the offer off and keeps the SKU, its settings and its link to your FBA units. Deleting removes the SKU from your inventory. In our experience, most catalogue damage comes from pressing delete when close would have done the job.

Delete a SKU with stock behind it and the units are stranded

Stranded inventory is FBA stock sitting in a fulfillment centre with no active offer to sell it. Delete a SKU that still holds units and those units become stranded. Shoppers cannot buy them, and they stay on the shelf.

Amazon's published policy on required removals allows it to ask you to remove units that have no active offer, with 30 days' notice. If you neither relist them nor remove them in that window, Amazon may dispose of them. Items with an expiration date get 7 days' notice. The Fix stranded inventory page in Seller Central lists the units at risk.

The trap is that the SKU you delete often looks empty. When two or more SKUs share one ASIN, the inventory screens we work with can mislead you. Sometimes each SKU shows the whole shared pool, so adding them up doubles your stock. Sometimes one SKU holds its own separate batch and a summary view shows it at zero. We have seen a SKU reported at zero that was holding a full batch. Delete it on that basis and the batch is stranded.

If it has already happened, act inside the notice window. In our experience, recreating the exact same SKU as an FBA offer on the same ASIN reconnects the stranded units. A SKU with a different code will not pick them up.

Delete the last offer on a page you created and the page can go too

This is the one we warn every brand about. If you created the ASIN yourself and you are its only seller, your offer is what keeps that page alive. We have seen Amazon drop a page like this from its catalogue after its only SKU was deleted. It went from Amazon.com and Amazon.ca at the same time.

There is no simple undo. When we tried to add a fresh offer to the old ASIN, Amazon first accepted it and then rejected it because the product was no longer in the catalogue. ASIN numbers are assigned by Amazon, so you cannot ask for the same one back. Rebuilding gives you a brand-new page with no history, or a match to another page for the same product.

That second case is the safe path. When another page for the exact same product already exists, often an older one with the same barcode, we move the content and the offer onto it instead of rebuilding. Two cautions from doing this: the new title and bullets can take a day or two to show publicly, and FBA units still labelled for the lost page will not move across. Those need a removal order, which is a request for Amazon to ship units back to you or dispose of them.

Amazon.ca and Amazon.com do not clean up together

If you sell in both, you have two sets of offers and two pools of FBA stock, one in Canadian fulfillment centres and one in US ones. A clean-up on Amazon.com leaves Amazon.ca as it was, and the reverse. What we watch for:

• A SKU can be empty in the US and still hold units in Canada. Check stranded stock in each marketplace on its own.
• If your offers are linked across North American marketplaces, a SKU you delete in one store can reappear from the other. Check how the link is set before you delete.
• The lost page is the exception. When a self-created ASIN was purged, it went in both marketplaces at once.

A delete on Amazon is hard to reverse, and the damage tends to show up weeks later as a disposal notice or a missing page. Before peak, the safe order is simple: close first, count stock by ASIN and then by SKU in both marketplaces, remove units on purpose, and keep one live offer on every page you own. Delete last, and only what is truly empty.