How Amazon's FBA Storage Fees Calculator Actually Works

What the calculator is actually multiplying

Amazon's monthly storage fee has nothing to do with how well your product is selling. It is cubic feet occupied × a rate per cubic foot for that month × the fraction of the month you stored it. Cubic feet comes from your package dimensions, not your product dimensions — a bulky poly bag or an oversized box adds real cost even if the item inside is small. The rate itself has two variables: the size tier (standard vs. oversize) and the season (non-peak, roughly January through September, and peak, October through December, when the rate steps up).

This is exactly what trips people up on Amazon's own seller forums: a seller with 525 units in an FC saw a report showing several different numbers — a per-unit rate, an average units-stored count, an estimated units-sold figure, and a per-unit-sold cost — and reasonably assumed sales must be part of the formula. They're not. Amazon confirmed it plainly: the fee is about the space your inventory occupies, full stop.

A worked example, using real reported numbers

Take that same real case, because it shows the mechanism better than a made-up one. The seller's Amazon-generated report showed a monthly storage cost per unit of $0.05, average inventory of 525 units, and an estimated 1 unit sold that month. The actual bill is the first two multiplied together: $0.05 × 525 = $26.25. That is the number that shows up on the invoice.

The report also showed a fourth figure — storage cost per unit sold, $23.85 — which is not a separate charge. It's the same $26.25-ish total divided by the 1 unit the calculator estimated would sell that month. It answers a different question: if this SKU only sells one unit this month, how much storage cost did that one unit absorb? It's a profitability warning signal, not a line item. Read it as a bill and you'll think Amazon is charging you nearly $24 per unit; read it correctly and you'll see the real charge is $26.25 total, with a sell-through problem sitting underneath it.

The table below breaks down what each of the four numbers on that kind of report actually measures, because the labels alone don't make the distinction obvious.

The mistake that makes the fee look wrong (or right) when it isn't

Monthly storage fees are not the only storage-related charge. Units that sit in an FC past a certain age trigger an additional aged-inventory surcharge, billed on top of the standard monthly fee, not instead of it. The exact day count and the surcharge rate are things Amazon revises, so this page won't print a number that will be stale in a quarter — check the current thresholds on the Fee Preview or Inventory Age reports inside Seller Central, because they move.

The mistake, including one we've made ourselves: reading the current month's storage line as the whole risk and missing that the same SKU is two months from crossing into the aged-inventory surcharge — a second, larger charge landing right after the first one looked manageable. A calculator run once gives you a snapshot. The surcharge risk is a trend, and it needs to be watched, not calculated once and filed away.

What to do once you have the number

A high storage fee on its own is rarely the real problem — it's usually the symptom of cash sitting in a SKU that isn't moving. The actual decision is removal versus liquidation versus a targeted promotion to move the units before the aged-inventory surcharge hits, and that decision depends on unit economics that a fee calculator doesn't have: landed cost, current sell-through, and what the units are actually worth if pulled and resold outside Amazon.

Full Circle has managed more than $500M in revenue across 100+ brands, and across that book the removal-versus-liquidation call is almost always about cash timing, not the fee line itself. A $26 monthly charge on a slow SKU is tolerable for a month. The same SKU still sitting there at month four, now carrying a surcharge on top, is a different conversation — and it's one that needs to happen before the surcharge lands, not after.

What this calculator can't tell you

A storage fee calculator, Amazon's or anyone else's, answers one question well: what will this SKU's stated inputs cost to store this month. It doesn't watch your whole catalog for units approaching the aged-inventory cutoff. It doesn't check whether Amazon has misclassified a SKU's dimensional weight and is charging the wrong fulfillment tier. It doesn't reconcile a shipment discrepancy or file a reimbursement claim for lost or damaged units. And if the number that's actually hurting you is cost-per-click or ACOS rather than a warehouse line item, that's an ad account problem — Dr. PPC's territory, not a storage calculator's.

Third-party calculators, including Yotpo's, are genuinely useful for the pre-launch question — what will this product cost to sell before I commit inventory to it — because they bundle referral fee, fulfillment fee, and a storage estimate with margin and ROI in one place. Treat the storage figures inside them as directional, though: they're built-in estimates, not pulled live from your account, and Amazon updates its own rate tables on its own schedule. For the number that will actually appear on your invoice, Amazon's own Revenue Calculator inside Seller Central, tied to your real account and real inventory, is the more accurate source — it just doesn't explain the terms on its own report, which is the exact confusion the seller forum thread shows.

Dr. Stock, from Full Circle, is built for the part none of these tools cover: watching storage, aged-inventory, and fee-classification issues across a whole catalog continuously, flagging the removal-versus-liquidation call before the surcharge lands, and catching FBA fee errors and shipment discrepancies as they happen rather than when a seller notices the total looks off. It doesn't store or ship anything itself — that's a 3PL's job — and it doesn't replace an ERP. Inventory purchasing decisions always go to a human. There's a demo and a first 30 days free; pricing is handled on the call, not published, because it's scoped to the account.