Amazon Aged Inventory Risk Calculator
for FBA sellers.
Project which FBA units are heading for the aged-inventory surcharge — and how much cash is on track to sit in slow movers at 90, 180, 270, and 365 days from today.
Your FBA stock, today
We'll project how much of it survives 90, 180, 270, and 365 days at your current sales pace.
Add real aged-cohort numbers (optional)
If you've pulled your aged-inventory report from Seller Central, plug the cohort numbers in here. We'll use them instead of the projection.
Estimate aged surcharge exposure (optional)
The exact aged-inventory surcharge changes — verify the current rate in Seller Central. Enter your own assumption to see a rough monthly exposure on the 180+ day cohort.
Run a velocity push (promo, price, ads) or rebalance to AWD/3PL before the aged surcharge bites.
Projected aged cohorts & cash exposure
How much of today's stock is on track to still be there at each Amazon aged-inventory threshold.
Projections assume your current sales pace holds steady and no additional inbound. Amazon's aged inventory surcharge (sometimes still called the long-term storage fee) changes — always confirm the live schedule in Seller Central before budgeting.
Don't let $5,760 sit through the surcharge
One email. Today's risk + a monthly recheck so this doesn't slip past you.
- This risk report as a PDF — cohorts, cash, recommended action
- Monthly recheck email — same projection with fresh velocity
- Multi-SKU template — run this for every SKU at once
The method, in plain English.
Two simple ideas: project how many units will still be sitting at each aged-inventory threshold, then convert those units into cash and (optionally) surcharge exposure.
Worked example
A long-tail FBA SKU that quietly slowed down after a strong launch.
Common aged-inventory mistakes.
Aged inventory rarely surprises sellers because the math is hard — it surprises them because the assumptions are wrong. Here are the patterns we see most.
Treating today's sales pace as forever
Velocity slows in Q1, after seasonal peaks, and as listings drift. A 'fine' days-of-cover number in October can be a disaster in February if you don't re-run the projection.
Counting only today's stock, ignoring inbound
Aged inventory is about what's sitting in FBA. But if you have a big PO already on the water, your real exposure 90 days from now is much higher than today's projection suggests.
Confusing slow-moving with aged
A SKU that sells once a day is slow, but it isn't necessarily aged — it depends on how long each unit has physically been in FBA. Acting on velocity alone misses long-tail SKUs that quietly cross the surcharge threshold.
Waiting for the surcharge invoice to act
By the time the aged-inventory surcharge shows up in your statement, you've already paid two months of it and dragged your IPI down with it. Reactive removals at 365 days cost dramatically more than discounts at 180.
Removing instead of discounting reflexively
Removal fees, return-to-supplier shipping, and disposal write-downs add up fast. For most categories, a 15–25% price cut moves the unit before the next surcharge tier and recovers more cost.
Using outdated Amazon fee language with finance
Calling it 'long-term storage fees' on a board deck makes the cost look like a known, capped problem. The modern aged-inventory surcharge is more aggressive and tiered, and finance partners need the current framing.
Great for one SKU.
Painful for a whole catalog.
Modeling one SKU's aged-inventory exposure is straightforward. Doing it for every SKU, every week, with inbound and AWD and seasonality factored in — that's where a spreadsheet falls over.
- Hundreds of SKUs, four cohorts eachManually tracking 90/180/270/365 buckets across a real catalog is a part-time job that nobody does consistently.
- Inbound shipments in flightAged risk depends on what's landing next month, not just what's in FBA today — a number a spreadsheet can't keep up with.
- AWD & 3PL units overlapReal cover depends on FBA + AWD + 3PL + inbound. A pure FBA aging report misses the bigger inventory picture.
- Sell-through drifts every weekRun rate changes with seasonality, ads, and pricing — and so does your aged-inventory projection.
- Surcharge tiers shiftAmazon's aged-inventory pricing has moved more than once. Your model has to follow it without you copying numbers from a memo.
- Trade-off math: discount vs removePicking the cheaper action SKU-by-SKU at scale needs margin, surcharge, and removal costs lined up automatically.
Track aged-inventory risk automatically.
Profit Hawk recomputes days of cover, aged cohorts, and projected surcharge exposure for every SKU using your real FBA, AWD, and 3PL data — and flags the ones that need a discount, rebalance, or removal before the surcharge hits.
- 90 / 180 / 270 / 365 cohort tracking per SKU
- Surcharge exposure auto-recomputed on rate changes
- Discount vs remove vs rebalance recommendations
- Replenishment alerts that respect aged risk
Aged inventory, answered.
The questions Amazon sellers actually ask us about aged inventory, surcharge changes, and when to discount versus remove.
Is this the same as the old Amazon long-term storage fee (LTSF)?
How is aged inventory different from slow-moving inventory?
What's a reasonable days-of-cover threshold before I start worrying?
Should I always remove aged units?
Do I have to enter cubic feet and surcharge assumptions?
What if I keep sending more inventory in?
Why does this matter for IPI and storage limits?
Can I use this for AWD or 3PL inventory?
More for Amazon sellers.
FBA Capacity Usage Calculator
See how much of your Amazon FBA storage capacity is used and whether your next shipment will fit.
AWD vs FBA vs 3PL Storage Estimator
Decide where overflow Amazon inventory should sit — FBA, AWD, or a 3PL.
Browse all free tools
Calculators for safety stock, reorder points, capacity, aged inventory, and more.
Want this tracked automatically across all your Amazon SKUs?
Profit Hawk recalculates aged-inventory risk, days of cover, and surcharge exposure using your real Amazon FBA, AWD, and 3PL data — and recommends a specific action SKU by SKU.