Amazon Moved the Storage Fee Cliff 90 Days Closer

Quick answer: Amazon's aged-inventory surcharge now starts at 181 days in the US, not 271, a 90-day-earlier threshold change most sellers are still tracking against outdated numbers.

Go looking on the Seller Central forums for "long-term storage fee" and you'll find the same post over and over, just with different numbers in it. One from a couple months back has a seller watching their charge climb: a few hundred dollars in January, a bit more in February, more again in March. Then a jump that doesn't fit the pattern at all. They asked, reasonably, which products did this and why. Nobody in the thread had a clean answer, because the honest answer is boring. The inventory had been sitting long enough to cross into a worse tier, and nothing on their dashboard told them that was coming.

That's the actual failure mode here. Not that the fee is high. That there's no moment before it posts where you'd think to go look.

The number everyone's still using is wrong

If you learned "271 days" as the point where aged-inventory surcharges start, that was correct for 2025. As of 2026, Amazon's own aged inventory surcharge documentation confirms the first surcharge tier moved back to 181 days, ninety days earlier than before. The full ladder now runs 181, 211, 241, 271, 301, 331, and 365+, with a newer 15-month (455-day) tier added on top for the longest-sitting stock. The 271 and 365 marks are still real, they're just not the first fence anymore. They're the second and third.

Ninety days is not a rounding error. It's a whole extra sales cycle's worth of inventory that's now exposed that wasn't before. A title that would've cleared the old threshold with three more months to sell through is now already inside the surcharge window, and there's no grandfathering clause that protects stock that was already in a fulfillment center before the change took effect.

Why the gap between "policy changed" and "seller noticed" is so wide

This isn't really about anyone being careless. Storage-fee policy changes get announced in a seller-news bulletin, sit there for a quarter, and then quietly become "how it's always worked." Nobody re-reads the fee schedule every time it updates, because nobody has time to. The forums back this up. Browse the FBA storage threads and it's less outrage than fatigue, sellers describing it as one more fee that shows up "one way or another" regardless of what they do differently.

Catalogs with a lot of distinct titles feel this hardest, not because anyone's mismanaging inventory, but because there's more of it to individually lose track of. A slow-moving cookbook that sold three copies in its first month and nothing since isn't wrong to have in stock. It's just the exact profile that ages past a threshold nobody's actively watching, because it already had its moment and stopped being interesting to check.

There's a second, quieter reason this gap exists: the monthly snapshot itself. Amazon assesses long-term storage fees based on inventory present in the fulfillment network on a specific day each month, not on a rolling daily basis. That means the fee isn't really about "how long has this been sitting," it's about "was this still sitting there on the one day Amazon looked." A unit that sells four days before the snapshot never gets charged. The identical unit, from the identical batch, sold four days after the snapshot instead, gets charged for the entire month. Two units, same age, same title, wildly different outcomes, and the only variable is which side of one specific date they happened to land on.

What actually happens once a title crosses the line

The mechanics of the charge itself are simple once you know them: it's assessed per cubic foot of the unit's dimensional footprint, not per unit sold, and it accrues every month the inventory remains past the threshold. That distinction matters more than it sounds like it should, because two products with wildly different price points but similar physical size get charged similarly. A $4 paperback and a $40 hardcover of similar dimensions pay close to the same surcharge, which means the fee eats a much larger share of margin on the cheaper item. This is part of why book resellers specifically talk about long-term storage fees more than almost any other seller category: low price points paired with real physical volume is the worst possible combination for this fee structure.

Catching it before the snapshot, not after the invoice

The only real lever here is time: knowing which units are approaching 181, 271, or 365 days before the next monthly snapshot, not finding out from the fee itself. That means two things need to be true.

1. You need current age-tier data per ASIN, not just "days of stock" computed from sales velocity. Velocity tells you when something will run out, it says nothing about how old what's currently sitting there actually is. These are genuinely different questions, and most inventory dashboards only answer the first one.
2. You need to see it ranked by dollar exposure, not alphabetically or by SKU. A handful of high-value units twenty days from a tier boundary matter more than a long tail of two-dollar items that just crossed 181.

Amazon's own long-term storage fee report has this data. It's just not surfaced anywhere sellers naturally look until after the charge posts. Once you have per-ASIN age-tier and dollar-at-risk visibility ahead of the snapshot, the decision becomes simple: liquidate, discount, or file a removal order before Amazon decides for you.

There's also a decision worth making in advance rather than reactively: at what dollar threshold does it make more sense to eat a small loss on a removal order than to keep paying an escalating monthly surcharge? For a lot of low-value inventory, the answer arrives faster than people expect, and knowing the age tier ahead of time is what lets that decision happen on your schedule instead of Amazon's.

---

This is the reasoning behind EcomSanity's Storage-Fee Radar: every ASIN closing in on the 181, 271, and 365-day thresholds, ranked by what it's about to cost, updated automatically from your own SP-API data. For the week-by-week playbook on what to actually do as a threshold approaches, see the aged-inventory surcharge action plan.