The Amazon FBA Calculator: What It Gets Right, and Where It Quietly Gets It Wrong

What the calculator actually does

The FBA Revenue Calculator is Amazon's own tool. You can reach a public version without an account, or a fuller one inside Seller Central once you're enrolled. It takes a product — an existing ASIN, or one you define from scratch with dimensions and category — and estimates what you'd net selling it through FBA versus fulfilling it yourself.

It's free to use in either location. Seller Central access requires a selling plan: the Individual plan runs $0.99 per item sold plus additional selling fees, the Professional plan is $39.99 a month plus additional selling fees. The calculator itself doesn't cost extra on top of that — it's a feature of the plan, not a separate product.

What it's not: a forecasting tool for sales volume, a replacement for your accounting system, or a guarantee of what Amazon will actually deduct next month. It's a per-unit estimate built from the inputs you give it, at the moment you give them.

The six inputs that decide the number

Every output the calculator produces traces back to a small set of inputs. Get one of these wrong and the profit figure is wrong in the same direction, every time.

• Referral fee — a percentage of the sale price, set by category, not by product.
• FBA fulfillment fee — driven by size and weight tier, including dimensional weight for large-but-light items.
• Monthly storage fee — charged per cubic foot, and it changes with the season.
• Long-term storage surcharge — not built into the base calculator; you have to add it yourself under 'other costs' if a SKU is sitting past the aging threshold.
• Cost of goods and inbound freight — the calculator doesn't know this; you supply it.
• Everything else — returns processing, prep, labeling — lumped into a single miscellaneous field, which is exactly where it gets forgotten.

A worked example

Say you're pricing a kitchen item at $25.00. For illustration only — not live Amazon fee figures — assume a 15% referral fee ($3.75), an FBA fulfillment fee of $6.50 for its size tier, and average monthly storage of $0.40 per unit. Cost of goods is $8.00, inbound freight $1.20.

Add those up: $3.75 + $6.50 + $0.40 + $8.00 + $1.20 = $19.85 in costs against a $25.00 sale price. That leaves $5.15, a 20.6% margin — before you've added anything in the miscellaneous field for returns or long-term storage.

That last part matters more than it looks. A product that's fine at 20% margin on paper can be break-even or worse once a realistic return rate and a quarter of long-term storage surcharge get added in. The calculator won't flag that gap for you. You have to go looking for it.

The mistakes that make the number wrong

The tool is arithmetic. Almost every bad number comes from a bad input, not a bug. The most common ones we see, including ones we've had to correct in our own early modeling:

• Using last quarter's fee schedule. Amazon updates fulfillment and storage fees on a schedule; a number that was right in January can be wrong by spring.
• Measuring the box, not the tier. Amazon measures dimensional weight, and a product that's technically small but awkwardly shaped can land in a heavier tier than the seller assumed.
• Leaving long-term storage and returns out entirely. Both are real costs on real SKUs, and neither is automatic in the base calculator.
• Copying a competitor's cost structure. Cost of goods and freight are yours alone — pulling someone else's assumed COGS from a listicle or a forum post produces a fictional margin.

When your actual payout doesn't match the calculator

If your Seller Central settlement report shows a different number than the calculator predicted, work backward in this order: check the size and weight tier Amazon actually assigned versus what you estimated; check whether a long-term storage surcharge landed on the unit; check the referral fee category Amazon applied against the one you assumed; and check the fee schedule date the calculator used against today's.

Across managed accounts — Full Circle has managed more than $500M in revenue across 100+ brands — the single most repeated cause of a mismatch isn't a calculator error at all. It's a dimensional-weight reclassification that happened after a packaging change, quietly moving a SKU into a more expensive fulfillment tier without anyone updating the model.

If the gap is on the ad side rather than the fee side — spend climbing while margin per unit stays flat for reasons that trace to bidding, not fulfillment — that's a different diagnosis, and it belongs with Dr. PPC, not a fee calculator.

Where other calculators fit

Third-party research tools — Jungle Scout's version is the one most people mean by 'scout fba calculator' — build their own fee estimators on top of the same public Amazon fee data. They're genuinely useful for a different job: scanning many potential products before you've sourced any of them, as part of product research. That's what they're built to do, and it's not what Amazon's own calculator is for.

The tradeoff runs the other way too. A research suite estimates fees on products you don't sell yet; it isn't built to reconcile a live SKU's actual settlement against what was promised. For that, the official calculator plus your settlement report is the right pair of tools, not a research platform.

Where the pattern is a one-off SKU or a single pricing decision, the official calculator is enough, used carefully with current inputs. Where the pattern is recurring — the same category of fee error showing up across dozens of SKUs, month after month, without anyone catching it in time — that's closer to what Dr. Stock exists to check: fee errors, dimensional-weight misclassification, and the storage and reimbursement decisions that a per-SKU calculator was never built to track at scale. Orbit, included with it, keeps the profitability view live at the ASIN level instead of as a one-time snapshot. Whether or not that's the right tool for you, the calculator itself is worth trusting for what it actually measures — a single estimate, at a single moment, from the inputs you gave it.