AOV calculator

Average order value — and the median next to it, because the mean lies on skewed baskets.

Runs entirely in your browser — nothing is uploaded, nothing is stored. Updated 2026-09-05.

Average order value is revenue divided by number of orders. $84,200 across 1,180 orders gives an AOV of $71.36.

That mean is the number every AOV calculator returns, and on a skewed basket it is misleading. If most orders are $40 and a handful are $900, the mean sits above almost every order you actually take, and a pricing decision made from it will be wrong. Paste your order values into the second panel and the calculator gives you the median alongside the mean — when the two are far apart, the median is the number describing your typical customer.

Which revenue goes in the numerator

Three choices quietly change the answer by ten per cent or more:

• Gross or net of returns. An AOV computed before refunds describes orders placed, not orders kept.
• Including shipping and tax inflates AOV with money you never keep.
• Discounts. Order value before a discount code is not what landed in the account.

Any of these is defensible; picking a different one each quarter is not. Write the definition down next to the number.

AOV is the lever that moves your CAC ceiling

Average order value sets what you can afford to pay for a customer. At a 40% margin, an $80 AOV supports a maximum acquisition cost of $32; take AOV to $110 and the ceiling moves to $44, and campaigns that were losing money become viable without touching a single bid.

This is why AOV work — bundles, thresholds for free shipping, order-page upsells — often beats another round of bid tuning. The break-even ROAS calculator shows the same relationship from the ROAS side.

Segment before you act on it

One AOV across a whole store hides the thing you would act on. New customers and returning ones usually differ by a wide margin; so do channels, with paid social typically producing lower-value baskets than branded search.

Compute it per segment and the decision becomes obvious — which is a query, not a spreadsheet, once your order data and your channel data live in one table.

Computing this from your own accounts

Every calculator on this page takes numbers you typed. The version that keeps working is the one that reads them from the accounts themselves — which is what TableBI is: connect Google Ads, Meta Ads, GA4 or Search Console once, and aov() becomes a macro you can query from your terminal.

# connect once, then the metric is a standing query
tablebi connect google_ads
tablebi connect meta_ads   # beta: your own or test ad accounts

tablebi ask "WITH w AS (SELECT MAX(date) AS anchor FROM metrics)
   SELECT platform, aov(SUM(revenue), SUM(conversions)) AS aov
   FROM metrics, w WHERE date > w.anchor - 30
   GROUP BY platform ORDER BY aov DESC"

# pin the answer to a URL that refreshes itself
tablebi pin --title "AOV calculator by channel"
→ https://you.tablebi.com/d/dsh_…

The pinned answer is a live URL that refreshes on its own — here is one running now. No hosted model does the reasoning; your own Claude Code or Codex drives the CLI, which is why there is no inference bill attached to it.

Questions people ask about aov calculators

Related calculators

All of them are listed on the free marketing calculators page.