Stranded, suppressed or unfulfillable: get this right first

Every seller I've worked with eventually tells me their "inventory is stuck", and that sentence can mean three different things. The confusion costs days, because each situation has a different fix. Before you change anything in Seller Central, work out which of the three you are dealing with.

Stranded inventory is Amazon's term for units sitting in a fulfillment center with no active, buyable listing attached to them. The listing has been deleted, deactivated or broken in a way that cuts the link between the ASIN and the offer. The stock itself is healthy and sellable. It just has nowhere to be bought from, and without a listing there is no buy box, no traffic and no sales.

A suppressed listing is a different problem. The listing still exists and is technically live, but Amazon has pulled it from search and browse, or blocked purchases, because of a content issue: missing required attributes, a flagged image, an expired compliance document, or a price that tripped an automated check. Until you fix that content problem, the listing is invisible or can't be bought.

Unfulfillable inventory has nothing to do with the listing. The problem is the physical units: damaged in the warehouse, expired, defective or otherwise unsellable as they are. The listing can be healthy and selling other units perfectly well while these particular units cannot ship.

Why the distinction matters

Fix a suppression issue and stranded units still won't sell, because the link between listing and inventory is still broken. Try to "reactivate" unfulfillable units and you will find nothing to reactivate, because the problem is the stock itself. Diagnose the wrong category and you can spend a week on the wrong fix while storage fees keep running.

Seller Central keeps these in separate places for that reason: the Stranded Inventory report, the listing quality and suppressed section under Manage Inventory, and the Unfulfillable Inventory report. When a SKU goes quiet, check which of those it appears in before you decide what caused it.

How inventory ends up stranded

Nobody strands inventory on purpose. It is nearly always a side effect of other work, which is why it is so easy to miss. These are the triggers I see again and again.

  • A listing was deleted or deactivated by mistake. Usually someone on the catalog team cleaned up "duplicate" or "old" SKUs without realizing units were inbound or already in a fulfillment center under that listing.
  • The listing lost buy box eligibility altogether. It was not suppressed; it was pulled from the catalog because of a category gating issue, an IP complaint or an account-level restriction that removed the offer's ability to sell.
  • A parent-child variation broke. Someone edited a variation theme, removed a child ASIN, or a bulk update detached a child from its parent, leaving inventory tied to a variation that no longer leads to a page anyone can buy from.
  • A bulk upload set price or availability wrong. A flat file with a blank price field, a "0" quantity override or a status column that switched dozens of listings to inactive at once, and nobody noticed until sales stopped.
  • The listing was matched to the wrong catalog item. A new product attached itself to an existing ASIN, or the reverse, and the connection between your inventory and the offer you meant to sell it under was lost.
  • A brand or compliance issue took the ASIN down. A trademark complaint, a restricted-category flag or an expired certification pulled the listing while the stock was already in FBA, with nothing wrong with the product.

Most of these are self-inflicted and come from routine catalog work. Sellers underestimate that. You don't need an enforcement action to strand inventory; a junior team member tidying a spreadsheet can do it in thirty seconds.

One more cause is worth knowing because Amazon itself warns about it. In Seller Forums threads, Amazon staff have advised against closing or deleting a listing straight after you sell through your stock. If a return comes back or a late inbound unit is received, it has no listing to attach to and lands in stranded inventory.

Finding it: the Stranded Inventory report

Seller Central has a report built for this problem, and most sellers I talk to either don't know it exists or only open it after a sales dip sends them looking. It sits under Inventory, then Manage Inventory, in the inventory health or "Inventory Planning" area, listed as Stranded Inventory. Amazon moderators on Seller Forums also point sellers to Inventory, then Fix Stranded Inventory. Bookmark whichever route your account shows.

The report gives each affected SKU a "stranded reason", and those reasons line up roughly with the causes above.

  • Listing not available on Amazon.com means the offer was deactivated or removed. It is the most common reason and usually the easiest to fix.
  • Item not in catalog means the ASIN the inventory is tied to no longer exists as a purchasable catalog entry, often after a bad catalog match or merge.
  • Fix price alert means a pricing error, often from a bulk upload, is keeping the listing from going live until you correct it.
  • Missing item dimensions or another required attribute means the listing is technically active but lacks data Amazon needs before it will show the offer as buyable.

The report also shows how many units are affected and how many days they have been stranded. That second number should set your priorities. A SKU stranded for two days is an annoyance. A SKU stranded for six weeks is a pile of storage fees you have been paying for nothing.

The habit that matters is checking this report on a schedule instead of waiting for a reason to. Inventory can strand silently the moment someone edits a live listing, whether that is a title change, a variation update or a routine bulk price refresh. The edit may not throw any error. You simply stop selling that SKU until somebody notices the flat sales line, and by then the storage fees and lost sales usually cost more than the fix would have.

What you can do from the Fix Stranded Inventory page

Each stranded line has a drop-down on the right with the actions Amazon offers for it. The ones you will use most are these.

  • Relist puts the existing listing back up without leaving the page. Amazon staff have described this as a one-click relist, and you can choose Edit first if the listing needs a correction before it goes live.
  • Edit opens the listing so you can fix the price, condition or missing attribute that stranded it.
  • Create removal order sends the units back to you or has Amazon dispose of them.
  • Delay removal 30 days, which Amazon moderators have pointed sellers to, buys time when you are still working on a fix.

Amazon also announced automated fixes for some stranded reasons. In that Seller Forums announcement, inventory stranded because the listing was closed, the listing was closed with an inventory error, or the item was discontinued is relisted automatically, and inventory stranded as "Merchant fulfilled" is switched to FBA. The default wait is 30 days. You can shorten it with Edit automatic-action settings on the same page, or opt a listing out with the drop-down. The announcement is several years old, so check that the setting still appears in your account before you rely on it. If you closed a listing on purpose and do not want it back, opt it out or set a future offer start date.

Fixing a deleted or deactivated listing

This is the most common case and, thankfully, usually the simplest. If the listing was deactivated rather than deleted, reactivating it in Seller Central is often enough to reconnect the offer to the stock. Amazon matches inbound and on-hand units to a listing by SKU and FNSKU, not by whether the listing happened to be live, so units don't disappear when a listing goes inactive. They just sit there unsold.

If the listing was deleted outright, recreate it with the same SKU, or at minimum make sure the same FNSKU is assigned to the recreated listing. People get this step wrong. They recreate the listing under a new SKU, and then the physical units have to be relabeled with a new FNSKU before they can sell. That is a relabel project, extra fees and extra delay you did not need. Match the original identifiers and the labels already on the units in the warehouse stay valid.

Before you recreate anything, find out why the listing was removed. If it was an accident, recreate it and move on. If it was removed for cause, such as an IP complaint, a policy violation or a compliance issue, recreating the identical listing without dealing with that reason just gets it pulled again. A repeated pattern tends to draw more scrutiny, not less.

If a recreated listing still will not pick up the stranded units after a day or so, open a Seller Support case. Give the SKU, ASIN and FNSKU, the stranded reason shown on the page, and what you have already tried. Amazon staff on the forums have suggested exactly this when the usual steps fail, and a case with all three identifiers gets handled much faster than "my inventory is stuck".

Broken variations, compliance holds and knowing when to cut losses

A broken parent-child relationship needs a different repair. If a child ASIN was detached from its parent, or a theme change orphaned a size or color, rebuild the relationship instead of treating it as a standalone reactivation. Use the Add Products or listing template flow to reattach the child to the right parent with matching variation attributes. Then check that the variation theme (size-color, size only, style only) matches what the parent expects. A mismatched theme can fail to attach without any error, even when everything else looks right.

With a compliance or content-related strand, reactivating the listing will never bring the inventory back, because the listing status was not the problem. Resolve the cause first: submit the missing certification, respond to the IP complaint, fix the flagged content, whatever triggered the takedown. Once that clears, the listing can go live again, and the stranded units become sellable as soon as it does. Trying to force a listing live around an open compliance flag wastes time.

When to stop trying to fix it

Some stranded SKUs are not worth rescuing. If a listing is stranded because of a permanent category restriction, a discontinued product line, or a compliance issue you can't realistically clear (an expired cert you no longer qualify for, a brand that withdrew your authorization), stop trying to relist it. Issue a removal order instead and either have the units returned to you or have Amazon dispose of them. Every extra week spent on a listing you cannot win is another week of storage fees on units that were never going to sell. Decide honestly which group you are in before you spend more time on it.

A quick triage by stranded reason

When the report lists dozens of SKUs, these rules keep the work moving.

  • If the reason is that the listing is not available and you closed it by mistake, relist from the page and confirm the offer is live within a day.
  • If the listing was deleted, recreate it with the original SKU before anyone creates a new one.
  • If the reason is a price alert, check the price against your recent selling price and minimum and maximum price settings, correct it, then relist.
  • If an attribute is missing, open Edit, fill the field Amazon flags, save and recheck the next day.
  • If the item is not in the catalog, look for a merge or a wrong match first; our guide to ASIN merge errors covers that route, and a Seller Support case is usually needed.
  • If the cause is a compliance or IP hold you cannot clear within a few weeks, create a removal order now instead of paying storage while you wait.

Work the list in order of units multiplied by days stranded. A small SKU with a few units can wait; a pallet that has sat for a month should not.

The money you lose while it sits there

Stranded inventory costs you the missed sales, and it also costs money every day it stays in the warehouse, because monthly storage fees don't care whether a unit can be sold. Amazon charges by the cubic foot whether the listing behind the unit is live, broken or gone. A stranded SKU is stock you are paying rent on with no chance of revenue until someone fixes it.

Then add the aged inventory surcharge, which starts once units have sat in a fulfillment center past a set age threshold. A pallet stranded for three or four months is likely picking up aged inventory charges on top of normal storage, and it may be getting close to the long-term storage cutoff as well. That is three separate charges stacking on the same dead stock.

Amazon's storage fee rates roughly double to triple during the Q4 peak season compared to the rest of the year, so a stranded SKU that goes unnoticed from October to January is one of the most expensive mistakes on a seller's calendar.

That is what sets stranded inventory apart from many other Amazon problems. It is not a one-off cost you absorb and forget. It keeps growing for as long as nobody notices. A listing broken for a week is a nuisance. The same listing broken for a full quarter can become one of your worst SKUs on a cost basis, even if the product sells well everywhere else in your catalog.

Habits that keep it from happening again

You can't remove stranded inventory entirely. People make mistakes, and Amazon's systems sometimes misfire on their own. A few operating habits will cut how often it happens by a lot.

  • Put a change-control step on anyone who can edit live listings. A second person reviewing bulk edits, deletions and variation changes before they go live catches most accidental strandings.
  • Read the processing report for every flat-file upload. A bulk upload can partly fail, skipping rows with formatting errors while the rest go through, so check the report each time and not only when something looks wrong.
  • Review the Stranded Inventory report on a fixed schedule: weekly for larger catalogs, monthly at the least for smaller ones. By the time a sales dip is obvious you have usually lost a couple of weeks of sales and storage fees to something a five-minute check would have caught on day one.
  • Write down who is allowed to deactivate or delete listings. The "someone deleted it without knowing stock was inbound" case almost always comes from unclear ownership of the catalog.
  • Before closing a listing you have sold through, wait until no inbound shipments or open returns remain against it.

None of this needs new software or a big process change. It means treating a listing edit with the same care as a price change or a PPC budget shift, because the downside is about the same size.

Stranded inventory is also one of the few Amazon problems that is fully within your control. There is no policy team to wait on, no appeal queue and no algorithm to satisfy. Once you know a listing is stranded and why, the fix is usually a same-day task. Compare that with an IP complaint or an account suspension, where you are on Amazon's timeline however quickly you respond. The sooner you find stranded stock, the sooner it stops costing you, and the only thing between you and the fix is opening the report.

Frequently Asked Questions

What's the difference between stranded, suppressed and unfulfillable inventory?

Stranded means healthy, sellable units sitting in a fulfillment center with no active listing attached. Suppressed means the listing still exists but Amazon pulled it from search or blocked purchases over a content issue. Unfulfillable is about the physical units: damaged, expired or defective. Seller Central has a separate report for each one.

Why did my inventory go stranded when nobody touched the listing?

Most strandings are side effects of routine catalog work rather than enforcement. A teammate deleting a 'duplicate' SKU, a broken parent-child variation, a bulk upload with a blank price or a zero quantity, a listing matched to the wrong catalog item, or a compliance flag can each cut the link between your units and a buyable offer.

How do I fix a stranded listing that got deleted by mistake?

If it was only deactivated, reactivating it usually reconnects the offer, since Amazon matches units by SKU and FNSKU rather than by whether the listing was live. If it was deleted outright, recreate it with the same SKU so the existing labels stay valid. A new SKU forces an unnecessary relabel project and extra fees.

How much is stranded inventory actually costing me while it sits there?

More than the lost sales. Monthly storage fees are charged by the cubic foot whether the listing is live, broken or gone, and units past a certain age pick up the aged inventory surcharge, with long-term storage fees beyond that. Storage rates roughly double to triple during Q4 peak, so a strand running from October to January hurts most.

Will Amazon relist stranded inventory for me automatically?

For some reasons, yes. Amazon announced automatic relisting for inventory stranded because the listing was closed or the item was discontinued, after a default of 30 days, with settings under Edit automatic-action settings on the Fix Stranded Inventory page. Check that the option still appears in your account, and opt out any listing you closed on purpose.

Not sure how much of your catalog is quietly stranded right now?

SellerVine's team can run a full inventory health check across your account, flag every stranded, suppressed, and unfulfillable SKU, and get the fixable ones back live fast.

Get your free audit →