What Amazon's Long-Term Storage Fee Actually Is (And How to Stop Paying It)

What the 'long-term storage fee' actually is now

The long-term storage fee is Amazon's old name for what's now called the aged inventory surcharge. Same idea, different label: Amazon charges it on top of your regular monthly storage fee for any unit that has sat in an Amazon fulfillment center for 181 days or more.

Amazon checks this on a snapshot taken on the 15th of each month. It doesn't average your inventory age continuously — it looks at what's sitting in the network on that one day and charges based on that. Miss the snapshot by pulling stock out on the 16th, and you've paid for another month you thought you'd avoided.

Age is calculated first-in, first-out across your entire fulfillment network, not per shipment and not per warehouse. That detail matters more than most sellers realize, and it's the source of almost every "why did this suddenly spike" ticket sellers open in the forums.

Worked example: why one seller's bill went from $469 to $1,507

One seller on Amazon's own forums lived through this exactly. Their long-term storage fees ran $210.94 in January, $347.74 in February, and $469.16 in March — a steady, predictable climb. Then, in that same month, a separate charge of $1,507.24 landed on top. Same fee category, wildly different number.

That jump usually isn't a billing error. It means a large batch of units crossed the 181-day line between the February 15th snapshot and the March 15th snapshot. Amazon doesn't phase the surcharge in gradually per unit — it applies once a unit's age crosses the threshold, and if a few thousand units all landed in the network in the same inbound window, they all cross that line in the same month. Across the $500M+ in managed revenue we've managed for 100+ brands, this exact pattern — a quiet few months followed by a spike — is one of the most common tickets we open.

The fix starts with the Aged Inventory Surcharge report, not the invoice. The invoice gives you a total. The report gives you the ASIN, the quantity, and the age band that caused it.

How the charge actually stacks

There's no single "long-term storage fee" number — it's layered on top of the standard storage fee, and it changes stage by stage. Here's the structure, without guessing at rates that vary by marketplace, size tier, and time of year:

Does filing a removal order stop the fee right away?

This is the exact question the seller above was asking, and it's a fair one: you've submitted the removal order, units are on their way out, are you still on the hook?

Partially, and for a specific reason. Amazon's own answer is that the aged inventory surcharge is based on the average number of units stored in FBA during the month, minus the average number of units pending removal. That's an average across the whole month, not a light switch. If you submit the removal order on the 20th, units sitting in FBA from the 1st through the 20th still count toward that month's average. The earlier in the billing cycle you request removal, the less of the month counts against you.

Practically: if you're already past 181 days, get the removal order in as soon as you decide. Expect one more month of exposure while units clear the network before the average actually drops.

The mistake almost every seller makes with FIFO

The natural assumption is that Amazon ships whichever unit is closest to the door, so sending fresh stock "refreshes" the aging problem. It doesn't work that way. Amazon deducts from the oldest recorded inventory in the network first, regardless of which physical unit actually left the shelf. Send a new shipment of the same SKU into a fulfillment center, and the units already sitting there don't get rotated out by the new arrivals — they keep aging toward 181 days undisturbed.

We've made this exact misread ourselves early in an engagement: a client's inbound team kept topping up a slow SKU to avoid a stockout, assuming it would rotate the older stock out faster. It didn't. Sales eventually worked through the oldest units, but not before that batch crossed 181 days and a surcharge landed anyway. The lesson wasn't "stop replenishing" — it was separating the reorder decision from the aging clock, because they're not the same problem and one doesn't fix the other.

What to do if the number looks wrong, or the fee just hit

• Pull the Aged Inventory Surcharge report in Seller Central before disputing anything on the invoice — it breaks the total down by ASIN and age band.
• Check the snapshot date against your actual inbound dates. A batch that feels "recent" to you may have entered the network months earlier than you remember, especially if it moved between fulfillment centers.
• Decide removal versus liquidation SKU by SKU, not as a blanket rule — a low-value item with slow velocity often nets more from liquidation than from paying to ship it back and store it yourself.
• File removal orders as early in the month as possible once you've decided, since the fee is based on a monthly average, not a single cutoff date.
• If the same SKUs surcharge every quarter, the real problem is usually reorder timing upstream, not the fee itself — that's a forecasting fix, not a fee dispute.

Where this fits if you're managing it across dozens of SKUs

Everything above is something you can do yourself in Seller Central with the surcharge report and the removal tool. For a handful of SKUs, that's usually enough.

Dr. Stock is a managed product built by Fable 5, from Full Circle, for the version of this problem that doesn't stay small: storage fees, aged-inventory surcharges, and the removal-versus-liquidation call tracked across a full catalog, alongside the reorder timing that caused the aging in the first place. Purchasing decisions still go to a human either way — the platform doesn't buy inventory on its own, whatever autonomy level you set. There's no published price; it's a demo and a call, with the first 30 days free. If the leak you're actually chasing is in ad spend rather than the warehouse, that's a different conversation — Dr. PPC handles that side.