Amazon Revenue Calculator

Every Amazon goal — hiring a VA, ordering a container, quitting a day job — starts with the same question: how much revenue will this business generate? Revenue projections turn vague ambition into concrete numbers: daily sales targets, monthly run rates, and annual forecasts you can plan inventory and cash flow around. The Amazon Revenue Calculator above builds those projections from just four inputs — average selling price, daily units per SKU, selling days per month, and SKU count — and shows you daily, monthly, and annual revenue plus the unit volumes behind them.

Revenue is the top line: the total value of everything customers buy, before Amazon deducts a single fee. It is not profit — never confuse the two — but it is the foundation every other metric is calculated from. Your fee estimates, ad budgets, inventory orders, and growth targets all scale with revenue, which makes the revenue projection the first spreadsheet of any serious Amazon plan. This guide explains how to build honest projections, how to use the calculator, and how professionals sanity-check revenue forecasts against reality.

How Revenue Projections Work

A revenue projection is simple arithmetic with one difficult input. The arithmetic: price × units per day × days × SKUs = revenue. Daily revenue per SKU, multiplied by selling days, gives monthly revenue per SKU; multiply by your SKU count for total monthly revenue; multiply by twelve for the annual figure. The calculator also derives total units per year, which drives inventory planning — you cannot sell 21,600 units a year if you only ever order 5,000 at a time.

The difficult input is units sold per day. For existing products, use your actual trailing-30-day average from Seller Central's business reports — not your best day, not your launch spike, the honest average. For new products, estimate conservatively from competitor review velocity: a competitor gaining ~30 reviews a month at a typical 1–3% review rate is selling roughly 1,000–3,000 units monthly, and a new listing should assume a fraction of that until it ranks. Overestimating daily units is the single most common forecasting error, and it cascades into over-ordered inventory and crushed cash flow.

Revenue vs Profit: Keeping the Top Line Honest

A $540,000 annual revenue projection sounds life-changing until you remember Amazon typically keeps 30–40% in fees and your product, freight, and ads consume more. At a 20% net margin, $540k of revenue is $108k of profit — still excellent, but a very different number for planning a resignation letter around. Always pair revenue projections with margin assumptions: multiply projected revenue by your realistic net margin to get the profit the revenue implies.

Revenue also has quality dimensions the top line hides. Revenue from one hero SKU is fragile; the same revenue spread across ten SKUs is resilient. Revenue dependent on heavy discounting is lower-quality than full-price revenue. Revenue with 25% TACOS is more expensive than revenue with 5% TACOS. Use the calculator's SKU count input honestly — projecting four SKUs at 15 units/day each assumes all four perform equally, which is rarely true. Consider running the calculation per SKU with individual figures for your most important products instead of blending.

How to Use the Amazon Revenue Calculator

Enter your average selling price across the SKUs you are modelling (or run the calculator separately per SKU for precision). Enter units sold per day per SKU — your honest average, not your peak. Enter selling days per month (30 for always-available FBA products; fewer if you face regular stockouts). Enter your number of SKUs.

Click Calculate to see daily revenue per SKU, monthly revenue per SKU, total monthly revenue, total annual revenue, total units per year, and average daily units across all SKUs. Use the unit figures to plan inventory: divide annual units by your order quantity to see how many restocks the year requires. Invalid inputs trigger a clear error message, and Reset restores defaults.

Worked Example 1: Four-SKU Kitchen Brand

Nadia sells four kitchen SKUs averaging $24.99. Her Seller Central data shows each SKU averages 15 units per day, and her products are in stock essentially all month (30 days).

Step 1: She enters 24.99, 15, 30, and 4. Step 2: She clicks Calculate.

Daily revenue per SKU: $374.85. Monthly per SKU: $11,245.50. Total monthly revenue: $44,982.00. Annual revenue: $539,784.00. Total units per year: 21,600 — meaning at her current 3,000-unit order size she needs roughly seven restocks a year, a critical planning insight the revenue figure alone did not provide. Average daily units: 60. Nadia's next step: at her 22% net margin, this revenue implies ~$118,750 annual profit — and she now knows exactly how many units to keep in the supply pipeline to sustain it.

Worked Example 2: Single-SKU Launch Forecast

Chris is launching one SKU — a resistance band set — at $29.99. With no sales history, he estimates conservatively: competitor review velocity suggests leaders sell ~900 units/month, so as a new listing he models 8 units per day (240/month), 30 selling days, 1 SKU.

Step 1: He enters 29.99, 8, 30, and 1. Step 2: He clicks Calculate.

Daily revenue: $239.92. Monthly: $7,197.60. Annual: $86,371.20. Units per year: 2,880. Chris's read: the projection is deliberately conservative — if the launch goes well, reality beats the forecast, and his initial 1,500-unit order covers about six months at this pace with buffer. He also notes the sensitivity: if daily units reach 15 instead of 8 after ranking improves, monthly revenue jumps to ~$13,500 and his inventory plan breaks — so he negotiates a reorder lead time with his supplier now, before he needs it. The calculator did not just forecast revenue; it exposed the inventory decision hidden inside the forecast.

Deep Dive: Seasonality and the Q4 Multiplier

Flat monthly projections are a fiction for most categories — Amazon revenue is seasonal. Q4 (October–December) routinely delivers 1.5–3× normal monthly revenue for giftable categories like toys, beauty, and home goods, while January–February slump. A single annual projection divided by twelve misleads twice: it understates Q4 inventory needs (hello, stockouts during the year's biggest weeks) and overstates slow-month cash flow.

The professional fix is seasonal weighting: run the calculator with your normal daily units for baseline months, then re-run with Q4-adjusted daily units (your best estimate, often 1.5–2× baseline) to size your Q4 inventory order separately. Also remember that Q4 brings higher storage fees (October–December rates roughly triple) and fiercer ad auctions — revenue rises, but so do the costs of capturing it. Project both sides.

Deep Dive: From Revenue to Inventory and Cash Planning

The calculator's unit outputs are the bridge from revenue fantasy to operational reality. Total units per year divided by your typical order quantity tells you how many purchase orders the year requires; multiply by supplier lead time (production + freight, often 60–90 days from China) to see how far ahead you must commit cash. A business selling 21,600 units/year with 75-day lead times must perpetually have ~4,400 units either on order or in transit — cash locked up long before a single sale.

Layer in Amazon's payout delay (~two weeks plus reserves) and the picture is complete: revenue earned in November becomes December cash, while the January restock deposit may be due in November. Sellers who project revenue without projecting these lags are the ones posting "profitable but broke" stories in forums. Use the revenue projection as step one, then build the inventory and cash timeline as step two — never skip step two.

Deep Dive: Price Elasticity and Revenue Trade-offs

The calculator treats price and daily units as independent inputs, but in the real world they are inversely linked: raise the price and units usually fall; cut the price and units usually rise. This relationship — price elasticity — determines whether a price change grows or shrinks total revenue, and it is the most important dynamic the simple projection does not capture. If a 10% price increase costs you only 5% of unit volume, revenue rises; if it costs you 15% of volume, revenue falls despite the higher price.

Elasticity varies by category. Commodity products (phone cables, generic supplements) are highly elastic — shoppers compare on price and switch easily, so small increases can crater volume. Differentiated products (strong brands, patented features, loyal followings) are inelastic — buyers pay the premium and volume barely moves. Before modelling a price change in the calculator, estimate your elasticity from history: look at past price tests and compute the ratio of volume change to price change. A product that held volume through a 10% increase is telling you revenue has headroom — raise the price in the calculator, trim daily units slightly, and watch projected revenue climb.

The practical workflow is paired scenarios: run the calculator at your current price and volume, then again at a 10% higher price with 5–8% lower volume, and compare the revenue lines. Whichever scenario shows higher revenue deserves a real-world price test. Many sellers discover they have been underpricing for years — leaving revenue on the table out of fear of a volume drop that never materialises. The calculator cannot run the test for you, but it tells you exactly what is at stake before you run it.

Deep Dive: Forecasting From Competitor Data

When you lack your own sales history — new launches, new categories — competitor-derived forecasting is the best available substitute. The method has three steps. First, identify 3–5 direct competitors with similar products and price points. Second, estimate each one's monthly sales from review velocity: count new reviews over the last 30 days (tools or manual sampling both work) and divide by an assumed review rate of 1–3% — 30 new reviews at a 2% rate implies roughly 1,500 monthly sales. Third, take the median of your competitors' estimates (not the average — the leader distorts averages) and model your launch at 20–40% of that median, since new listings convert worse until they accumulate reviews and rank.

Refine the estimate with Best Seller Rank (BSR) context: products ranked #1–#20 in a subcategory sell dramatically more than those at #500, so compare yourself to competitors at the rank you realistically expect to reach in 3–6 months, not the category kings. And sanity-check the total: multiply your projected daily units by the category's visible competitor count — if your forecast implies you will capture an implausible share of category demand, trim it. Competitor-based forecasts are inherently rough (±50% is normal), which is exactly why you model scenarios rather than single numbers and keep initial inventory orders modest until real data arrives.

Tips for Accurate Revenue Projections

1. Use trailing averages, not peaks. Base daily units on the last 30–90 days of actual sales, excluding launch spikes and lightning deals.
2. Discount for stockouts. If you were out of stock 5 days last month, your true demand exceeds recorded sales — but project from availability you can actually sustain.
3. Model SKUs individually when they differ. Blending a hero SKU with slow movers produces a fictional average; run the big ones separately.
4. Build three scenarios. Conservative, expected, and optimistic daily-unit figures give you a range to plan inventory against instead of a single fragile number.
5. Apply seasonal multipliers. Re-run with Q4-adjusted daily units for giftable categories; flat annual ÷ 12 lies twice a year.
6. Validate against review velocity. Competitors gaining X reviews/month at 1–3% review rates imply a sales band — check your forecast sits inside reality.
7. Convert revenue to units immediately. Units per year is the operational number — it sizes orders, warehouse space, and cash needs.
8. Subtract fees mentally. Multiply every revenue projection by your net margin to see the profit it implies before making life decisions.
9. Revisit quarterly. Rankings shift, competitors launch, and categories evolve — a forecast older than a quarter is a historical document.
10. Track forecast vs actual. Each month, compare projected to actual revenue; systematic gaps reveal whether you chronically over- or under-estimate.

Frequently Asked Questions

1. What is revenue on Amazon?

Revenue is the total value of products sold before any deductions — price × units sold. Amazon's fees, your product costs, and advertising are all subtracted afterwards to reach profit.

2. How is revenue different from profit?

Revenue is the top line; profit is what remains after all costs. A $500k revenue business at 20% margin earns $100k profit — the revenue figure alone says nothing about earnings.

3. How do I estimate daily units for a new product?

Study competitor review velocity: monthly new reviews ÷ estimated review rate (1–3%) ≈ monthly sales. Model a new listing at a conservative fraction of established competitors.

4. Should I include all SKUs in one calculation?

Only if they perform similarly. For mixed catalogues, run the calculation separately for hero SKUs and group only the comparable ones together.

5. How does seasonality affect projections?

Q4 often brings 1.5–3× normal revenue for giftable categories, with January–February slumps. Run baseline and Q4-adjusted projections separately rather than flattening the year.

6. What are selling days per month?

The days your product is actually purchasable. Use 30 for stable FBA availability; reduce it if stockouts regularly cost you selling days.

7. How do I turn revenue into an inventory plan?

Take total units per year, divide by your order quantity for restock frequency, and multiply daily units by supplier lead-time days for pipeline stock. That is your ordering plan.

8. Why do sellers overestimate revenue?

They project from peak days, ignore seasonality, assume new SKUs match hero SKUs, and forget stockouts. Conservative inputs and scenario ranges prevent this.

9. Does the calculator account for Amazon fees?

No — it projects top-line revenue only. Apply your net margin percentage to the result to estimate the profit the revenue implies.

10. What is a healthy revenue per SKU?

It varies wildly by category and price point. More useful benchmarks: revenue per SKU should comfortably cover its inventory investment and management time — many sellers target $5k–$15k/month per mature SKU.

11. How accurate are revenue projections?

For established products with stable rankings, ±10–15% is achievable. For new launches, treat projections as scenarios, not promises, and update them monthly with actuals.

12. Should projections include Prime Day and deals?

Model baseline months without events, then add event uplifts separately. Blending deal spikes into the baseline inflates everyday expectations.

13. How does price affect the projection?

Revenue scales linearly with price in the calculator, but in reality raising prices usually reduces units sold. Adjust daily units down when modelling higher prices.

14. Can revenue projections help with financing?

Yes — lenders and investors want to see revenue forecasts tied to unit assumptions. A calculator-backed projection with stated assumptions is far more credible than a round number.

15. What should I do after projecting revenue?

Convert to units for inventory planning, apply your net margin for profit implications, map cash timing around payouts and supplier payments, and re-check quarterly.

CONCLUSION

Revenue projections turn Amazon ambition into operational numbers: daily targets, monthly run rates, annual forecasts, and the unit volumes that size every inventory order. The Amazon Revenue Calculator builds all of them from four honest inputs in seconds — but its value depends entirely on the honesty of the daily units figure you enter. Base it on trailing actuals, discount for seasonality and stockouts, model scenarios instead of single points, and always translate revenue into units, profit, and cash timing before acting. Sellers who project rigorously order the right inventory at the right time; everyone else is either stocking out or drowning in overstock.