Average Order Value Calculator

What is average order value?

Average order value (AOV) measures the average amount of revenue generated by each order during a defined period or within a defined group of orders. It is one of the most widely used ecommerce metrics because it connects revenue with transaction volume in a simple way.

If a store records 50,000 of included revenue from 1,000 orders, its AOV is 50. That means the arithmetic mean value of those orders is 50. It does not mean that most customers spent exactly 50, and it does not describe how frequently customers purchased.

AOV is useful for pricing, merchandising, bundling, free-shipping thresholds, upsells, cross-sells, marketing analysis and revenue planning. But it should be interpreted together with conversion rate, order volume, margin, customer acquisition cost, purchase frequency and the distribution of order values.

How to use this AOV calculator

The calculator supports four different questions instead of limiting you to a single division problem:

• AOV: enter revenue and order count to calculate average order value.
• Required Revenue: enter order count and target AOV to find the revenue needed to reach that average.
• Required Orders: enter a revenue target and target AOV to estimate how many orders are needed.
• AOV Lift: compare a baseline AOV with a new AOV to calculate the absolute change, relative percentage lift and projected revenue difference.

The optional ecommerce analysis adds basket size, average item value, purchase frequency per customer and revenue impact from a target AOV increase when the needed inputs are available. Currency selection changes display only; it does not perform exchange-rate conversion.

Average order value formula

The word included matters. Revenue and orders must come from the same scope. If the numerator covers all online-store sales for June but the denominator contains only paid-search orders, the result is not a meaningful AOV.

Suppose an online store has 750 orders and 45,000 of revenue under a consistent reporting definition. AOV is 45,000 ÷ 750 = 60. If the next month revenue rises to 54,000 while orders stay at 750, AOV rises to 72.

What revenue should be used in AOV?

Different platforms can define the revenue numerator differently. A simple business formula often uses total order revenue divided by total orders. Ecommerce analytics systems may instead define AOV from a particular sales measure, such as product sales after discounts, while excluding taxes, shipping, post-order edits or other adjustments.

For example, Shopify's current analytics documentation defines its AOV metric as gross sales minus discounts divided by orders, excluding post-order adjustments. That is not identical to every business's idea of “total revenue.” The correct input for this calculator therefore depends on what you are trying to reproduce or analyze.

Should shipping and tax be included?

There is no universal answer because AOV definitions differ across reporting systems. If your platform excludes shipping and tax from AOV, including them in a manual calculation will make the numbers disagree. If you are measuring the average amount actually collected at checkout, you may intentionally use a broader order-total definition.

The important rule is consistency. Label the metric clearly — for example, “product-revenue AOV” or “customer-paid order value” — when multiple definitions are used inside the same business.

How discounts affect AOV

Discounts can increase the number of items or orders while reducing the revenue captured from each unit. Whether a promotion increases AOV depends on how customer behavior changes. A bundle discount might raise AOV if customers add enough extra merchandise, while a sitewide percentage discount can lower AOV if basket composition does not change.

When evaluating promotions, compare not only AOV but also total orders, conversion rate, gross margin, contribution margin and revenue. A promotion that raises AOV by encouraging larger baskets can still reduce profit if the discount is too costly.

Required revenue formula

If you expect 2,000 orders and want an AOV of 75, required included revenue is 150,000. This calculation is useful for translating an AOV target into a revenue requirement at a known transaction volume.

It also shows an important limitation of AOV planning: higher AOV does not guarantee higher total revenue if order count falls. If a price increase raises AOV but causes enough customers to stop purchasing, total revenue can decline.

Required orders formula

If your revenue goal is 250,000 and target AOV is 80, the mathematical requirement is 3,125 orders. If the calculation produces a fraction of an order, round up when the goal must be met or exceeded because real orders are normally whole transactions.

This mode can be combined with a conversion-rate estimate to create traffic plans. If you need 3,125 orders and expect a 2.5% purchase conversion rate, a simplified traffic estimate would be about 125,000 conversion opportunities under a compatible denominator.

AOV lift: absolute change and relative change

If AOV rises from 50 to 60, the absolute increase is 10 and the relative lift is 20%. Reporting both is clearer than saying only that “AOV increased by 10,” because the relative significance depends on the starting value.

If the baseline is zero, relative percentage lift is mathematically undefined. In real ecommerce reporting, a zero AOV baseline usually means there were no valid orders or the metric was not meaningfully defined for that period.

How AOV affects revenue

At a fixed order count, revenue is directly proportional to AOV:

A store with 5,000 monthly orders and a 50 AOV generates 250,000 under the selected revenue definition. If AOV rises to 55 and order count stays unchanged, revenue becomes 275,000 — an increase of 25,000.

This is why AOV is attractive as an optimization lever: it can increase revenue without requiring more orders. But the assumption that order volume stays constant must be tested rather than assumed. Price changes, shipping thresholds or aggressive upsells can affect conversion and order count.

AOV and conversion rate should be read together

AOV and conversion rate can move in opposite directions. Raising prices may increase AOV while reducing the share of visitors who buy. Heavy discounts may improve conversion while reducing revenue per order. A strong ecommerce strategy therefore looks at the combined revenue effect rather than optimizing either metric in isolation.

Suppose 100,000 sessions convert at 2% with an AOV of 60. Simplified revenue is 120,000. If AOV rises to 66 but conversion rate falls to 1.7%, revenue becomes about 112,200. The higher AOV did not compensate for the lower conversion rate.

Conversely, a modest AOV decrease may be acceptable if a promotion produces enough additional orders and profitable revenue. The right decision depends on margin and the entire funnel.

AOV vs average basket size

Average order value measures money per order. Average basket size or units per transaction measures items per order.

If a store sells 2,400 items across 1,000 orders, average basket size is 2.4 items per order. If AOV is 60, those two metrics together suggest that the average revenue per item is roughly 25 when calculated as total revenue divided by total items.

AOV can rise because customers buy more units, because the product mix shifts toward higher-priced items, because prices increase, because discounts change, or because some combination of those effects occurs. Basket size helps distinguish “more products per order” from “more value per product.”

AOV vs average selling price

Average selling price is typically measured per item or unit, while AOV is measured per transaction. A store can have an average item price of 30 and an AOV of 75 because customers buy multiple items in many orders.

If basket size rises while average item value remains stable, AOV should generally rise. If basket size stays stable but customers shift toward more expensive products, AOV can also rise.

AOV vs revenue per visitor

Revenue per visitor or revenue per session includes people who did not buy, while AOV includes only completed orders under the selected order definition. For ecommerce, the two metrics can be related approximately through conversion rate:

At a 3% conversion rate and 80 AOV, simplified revenue per session is about 2.40. Improving AOV to 88 raises that figure to about 2.64 if conversion stays at 3%. This relationship explains why AOV and conversion rate should be analyzed together.

AOV vs customer lifetime value

AOV measures a single transaction average. Customer lifetime value (CLV or LTV) measures value across a longer customer relationship. AOV can contribute to lifetime value, but the number of purchases per customer and the duration of the relationship also matter.

A simplified revenue-based relationship is:

If customers average 60 per order and place 3 orders per year, annual revenue per customer is approximately 180 before considering retention length, margin or other adjustments. Improving AOV can therefore increase lifetime value when purchase frequency and retention do not deteriorate.

Purchase frequency is different from AOV

If 1,000 orders come from 850 customers, average purchase frequency during the period is about 1.18 orders per customer. A business with modest AOV but strong repeat purchase behavior can be more valuable than one with high AOV and almost no repeat purchasing.

The optional customer field in this calculator reports this simple period-level purchase frequency when both orders and unique customers are known.

Mean AOV can hide the shape of your orders

AOV is an arithmetic mean. A small number of unusually large orders can pull the mean upward even when most customers spend much less. That is why mean, median and mode can tell different stories.

• Mean: total included revenue divided by order count — the traditional AOV.
• Median: the middle order value after sorting orders from lowest to highest.
• Mode: the order value, or range of order values, that occurs most frequently.

Suppose nine orders are 40 each and one order is 400. Total revenue is 760, so AOV is 76. But the typical small order is still 40. If you set an upsell or free-shipping strategy based only on the 76 mean, you may be targeting behavior that most customers do not exhibit.

Why median and order-value distribution matter

When your order values are highly skewed, median order value and a histogram or distribution can reveal more than AOV alone. Shopify's recent educational material specifically warns that mean AOV can be distorted by a handful of high-value orders and recommends considering other measures of central tendency.

This does not make AOV wrong. Revenue divided by orders remains an important business metric because it reconciles directly to total revenue. The point is that AOV answers “what is the arithmetic revenue per order?” rather than “what does the most typical customer spend?”

Segmented AOV is usually more actionable than one storewide number

Storewide AOV can hide important differences between customer groups. Useful segments may include:

• new customers vs repeat customers
• paid search vs organic traffic
• email vs social vs direct traffic
• mobile vs desktop
• domestic vs international orders
• full-price vs promotional orders
• subscriber vs non-subscriber customers
• product category, collection or brand

A blended AOV can rise simply because the mix shifted toward a high-value segment, even if no individual segment improved. Segment analysis helps separate true behavioral change from mix change.

Weighted AOV: do not average segment AOVs equally

If different segments have different numbers of orders, the combined AOV should be calculated from combined revenue and combined orders, not from a simple average of segment percentages or values.

Example: Segment A has 100 orders at an AOV of 100, producing 10,000 of revenue. Segment B has 900 orders at an AOV of 40, producing 36,000. A simple average of 100 and 40 is 70, but the true combined AOV is 46,000 ÷ 1,000 = 46.

This weighting preserves the actual transaction mix.

Worked example: basic AOV calculation

An ecommerce store reports 84,000 of included revenue from 1,200 orders during a month.

• Revenue: 84,000
• Orders: 1,200
• AOV: 84,000 ÷ 1,200 = 70
• Revenue per 100 orders: 7,000

If the store sold 3,000 items, average basket size is 2.5 items per order and average revenue per item is 28.

Worked example: target AOV planning

Suppose a store expects 4,000 orders next quarter and wants to raise AOV from 65 to 72. Required revenue at the new target is 4,000 × 72 = 288,000. At the old AOV, the same order volume would produce 260,000.

The difference is 28,000, or about 10.77% higher revenue if order count remains unchanged. That last condition is critical: the model should be updated if the strategy used to increase AOV changes conversion or order volume.

Worked example: required orders for a revenue goal

A business wants 500,000 in revenue at an expected AOV of 85. Required orders are 500,000 ÷ 85 = approximately 5,882.35. Since partial orders are not possible, at least 5,883 orders are needed to meet or exceed the target at exactly that AOV.

If expected conversion rate is 2.8%, the business could then use a separate conversion-rate calculation to estimate the traffic required for 5,883 orders.

Free-shipping thresholds and AOV

Free-shipping thresholds are often designed to encourage customers to add more to the cart. A common idea is to set the threshold somewhat above a typical order value so many shoppers are within reach of qualifying. But there is no universally correct percentage above AOV.

A threshold should account for shipping cost, contribution margin, product prices, basket distribution and customer response. If most orders are 35 and individual products cost 50, a 40 threshold may not change behavior at all. If the threshold is too high, customers may abandon the attempt rather than add more.

AOV can inform the threshold, but median order value and common basket combinations are often equally important. Test thresholds against margin and conversion rather than adopting an arbitrary “AOV plus X%” rule.

Upselling, cross-selling and bundles

Three common approaches to increasing AOV are:

• Upselling: encouraging a higher-value version or upgrade.
• Cross-selling: suggesting complementary products.
• Bundling: combining several products into one offer or package.

Each strategy can raise AOV, but the business outcome depends on margin and customer behavior. A heavily discounted bundle may raise order value while lowering contribution per order. An irrelevant cross-sell can add checkout friction. Evaluate incremental revenue together with incremental cost.

Quantity discounts can raise AOV but lower margin percentage

“Buy more, save more” offers can increase basket size and AOV by encouraging larger quantities. However, a larger order is not automatically more profitable if the additional units are deeply discounted or expensive to fulfill.

For example, raising AOV from 50 to 70 sounds positive. But if contribution margin falls from 40% to 25%, contribution per order moves from 20 to 17.50. AOV improved while contribution per order declined. That is why margin belongs next to AOV in promotion analysis.

AOV and customer acquisition economics

AOV can influence how much acquisition cost a business can support. If higher AOV creates more gross profit or contribution per order, the business may be able to spend more to acquire customers while maintaining the same profitability target.

But the relationship depends on margin. Doubling AOV does not necessarily double contribution if the product mix, discounting or fulfillment cost changes. For paid acquisition, connect AOV with conversion rate, contribution margin, CPA and ROAS rather than using AOV alone.

AOV and ROAS

At a stable conversion rate and ad cost structure, higher AOV can increase attributed revenue and therefore improve ROAS. But the causal chain matters. If a strategy raises AOV by increasing prices and reduces conversion substantially, ROAS may not improve.

One useful decomposition is:

Changes in any of those components can change attributed revenue. Diagnose which driver actually moved before crediting the result to AOV.

Returns, refunds and cancellations

Order value measured at checkout can differ from realized revenue after returns and refunds. Some platforms calculate AOV from the original order value and exclude post-order adjustments, while financial reporting may care about net realized sales.

If return rates differ between product categories or promotions, a high checkout AOV can overstate the economic value of those orders. Consider reporting both order-time AOV and a separate net or realized revenue-per-order measure when returns materially affect the business.

Currency consistency

This calculator does not fetch exchange rates. Revenue, target revenue and AOV values should therefore use the same currency. If your store sells in multiple currencies, either convert orders to a common reporting currency using a consistent method or calculate AOV separately by currency.

Mixing unconverted dollar, euro and rupee order values in a single numerator produces a meaningless average.

What is a good AOV?

There is no universal good average order value. AOV is heavily shaped by product prices, category, bundles, purchasing frequency, geography, customer mix and business model. A store selling inexpensive consumables and a store selling premium furniture should not be expected to have similar AOVs.

Even within the same broad industry, price positioning can make external averages misleading. A more useful benchmark is your own historical AOV under a consistent definition, segmented by customer type and channel where appropriate.

External benchmarks can provide context, but use them only when you understand the revenue definition, currency, order mix, geography and sample behind them.

How to tell whether an AOV increase is actually good

When AOV rises, ask what caused it. Then check the downstream metrics:

• Did total revenue increase?
• Did order count or conversion rate fall?
• Did gross profit or contribution per order increase?
• Did discounts become more expensive?
• Did return or cancellation rates change?
• Did the mix shift toward a small number of large orders?
• Did new-customer acquisition become more or less efficient?

An AOV improvement is most valuable when it creates additional profitable revenue without damaging conversion, retention or customer experience.

Common AOV mistakes

• Mixing incompatible revenue and order scopes. The numerator and denominator must cover the same orders.
• Assuming every platform defines AOV identically. Shipping, tax, discounts and adjustments may be handled differently.
• Calling AOV “average customer spend.” One customer can place multiple orders; customer-level spend is a different metric.
• Ignoring the distribution. A few very large orders can pull the mean above the typical order.
• Averaging segment AOVs equally. Use combined revenue divided by combined orders.
• Increasing AOV with unprofitable discounts. More revenue per order does not guarantee more contribution.
• Ignoring conversion rate. AOV gains can be outweighed by fewer completed orders.
• Ignoring returns. High checkout AOV can turn into lower realized revenue.
• Using universal benchmarks blindly. Product prices and business models differ too much.
• Mixing currencies. Convert to a common currency or segment calculations.

Frequently asked questions

AOV measurement note

Average order value is most useful when revenue and orders share the same scope and the definition stays consistent over time. Before acting on an AOV change, check whether the movement came from basket size, price, product mix, discounts, customer mix or a few unusually large orders. Then evaluate conversion, order volume, margin and returns alongside AOV so that a higher average translates into a better business outcome rather than just a larger headline number.