Amazon Storage Fee Calculator: How the Number Is Actually Built

The formula behind every amazon storage fee calculator

Whether you're searching for an amazon storage fee calculator or an amazon monthly storage fee calculator, they're all running the same math: cubic feet per unit × your average units stored that month × the rate for your size tier and month. That's the entire formula. Amazon's Revenue Calculator inside Seller Central runs this for you once you know your size tier; third-party tools like Yotpo's FBA Fee Calculator wrap the same math into a fuller profit model that also nets out referral fees, fulfillment fees, and product cost.

Cubic feet per unit is length × width × height in inches — using your packaged dimensions, not the product alone — divided by 1,728. Multiply that by the average number of units physically sitting in Amazon's fulfillment centers across the month, and multiply again by the per-cubic-foot rate for your size tier (standard or oversize) and the month (peak or non-peak). That's the bill.

Nothing in that formula references how many units you sold. That's the part that trips almost everyone up at least once.

Worked example: 525 units and a fee that looked too low

A seller on Amazon's own forum ran into exactly this. Product: an automotive accessory, unit weight 0.421 lb, packaged dimensions 7.8 × 3.58 × 3.23 inches, 525 units stored, one unit sold that month. Amazon's calculator returned a monthly storage cost of about $0.05 per unit — roughly $26 total. The seller assumed that had to be wrong for 525 units sitting on a shelf, and asked whether low sales were somehow suppressing the number.

Run the formula yourself: 7.8 × 3.58 × 3.23 = 90.2 cubic inches, divided by 1,728 = about 0.052 cubic feet per unit. Multiply by 525 units and you get roughly 27.4 cubic feet stored. Apply a non-peak standard-size rate to that and you land close to what Amazon's calculator returned. The math checks out.

The seller's instinct — that the number felt too small for that much inventory — wasn't wrong to have. It was aimed at the wrong variable. The fee is genuinely small because this is a small, light, cheap-to-store item, and Amazon confirmed in that same thread that sales have no bearing on it. What sales velocity actually determines is how long those 525 units sit before they cross into aged-inventory territory — a separate fee this calculator never touches.

Two variables that move the number more than anything else

Which month it is, and which size tier Amazon has assigned your ASIN, matter more than any other input in this formula.

Rates roughly triple in the fourth quarter versus the rest of the year, so a product that's cheap to store in July can look very different in a November snapshot at the same volume. Size tier matters even more, because it isn't always what you assume: Amazon sets it off your packaged dimensions, and a product that ships in slightly oversized retail packaging can get reclassified from standard-size to oversize without anyone catching it until the invoice lands.

• Standard-size, Jan–Sep: the baseline rate on the current schedule.
• Standard-size, Oct–Dec: roughly three times the non-peak rate.
• Oversize: priced on a separate, higher schedule entirely — check Seller Central for the current figure rather than trusting a cached number from a blog post, since Amazon revises these on its own timeline.

The fee no calculator shows you: aged inventory surcharge

None of the tools above — Amazon's included — model the fee that actually causes damage: the aged inventory surcharge, Amazon's long-term storage fee. It's layered on top of the regular monthly storage fee once units cross Amazon's aged-inventory thresholds, and it escalates the longer stock sits. A calculator that only shows this month's cubic-foot charge will tell you a SKU is cheap to store right up until the surcharge tier changes and the same units cost several times more to keep, with no warning built into the tool itself.

Across the 100+ brands inside Full Circle's $500M+ in managed revenue, this is the fee that gets missed most often — not because it's hidden, but because it's a second calculation nobody runs until the invoice already reflects it. By the time a seller notices, the decision that would have avoided it — remove the units or liquidate them before the surcharge tier hit — is usually already off the table.

What to do when the number looks wrong

If a calculator's output doesn't match what shows up on your statement, work through this before opening a case:

• Check the dimensions you entered. Use packaged dimensions, not the bare product — poly bags, inserts, and retail boxing all count.
• Confirm the size tier Amazon actually has on file. It can change without an email; a small packaging update can flip a SKU from standard to oversize.
• Separate the two fees. A statement showing more than the monthly cubic-foot math usually means an aged-inventory surcharge has been added on top, not that the base calculation is wrong.
• If it's still off, open a Seller Support case and ask for the per-ASIN cubic-foot and fee-tier breakdown directly — even Amazon's own forum support routes this request there rather than solving it in the thread.

The mistake we've made ourselves, early on with a slower-moving SKU: treating the monthly storage line as background noise instead of running the removal-versus-liquidation math before the aged surcharge tier changed. It's a small number until it isn't, and by then the cheaper exit has usually already closed.

Where this fits with a bigger inventory picture

A calculator answers one month at a time. It won't tell you that a SKU's fee is about to jump tiers, or that the fix is a removal order rather than a smaller reorder — that's a monitoring and decision problem, not an arithmetic one. Dr. Stock, run by Fable 5 out of Full Circle, tracks storage and aged-inventory fees alongside reorder timing and FBA fee errors, and brings the removal-versus-liquidation call to a human before it becomes an invoice surprise. If the leak you're chasing is in the ad account rather than the warehouse, that's a Dr. PPC problem instead. Either way, run the formula above first — it's free, and it's usually enough.