CCalclabhub

Business · 36 calculations

Ecommerce

How To Calculate Average Order Value

Average order value, usually shortened to AOV, is the average amount spent each time a customer places an order. It divides total revenue by the number of orders in the same period, and it matters because raising it grows revenue without buying extra traffic. The same figure also reveals the revenue earned from every hundred orders and how many orders are required to reach a revenue target.

Last updated

Quick Answer

AOV = total revenue / number of orders

AOV
Average order value, the mean spend per order
R
Total revenue for the chosen period
N
Number of orders placed in that same period
T
A revenue target, used to find the required order count

Divide total revenue by the number of orders to get the average amount spent per transaction. With 48,000 of revenue from 1,200 orders the AOV is 40.0, which means every hundred orders brings in 4,000.0. To reach a 60,000 revenue target at that AOV you would need 1,500.0 orders, found by dividing the target by 40.0.

What Is Average Order Value?

Average order value, often abbreviated to AOV, is the mean amount of money a customer spends per order. It is calculated by dividing total revenue for a period by the number of orders placed in that same period. If a store takes 48,000 from 1,200 separate orders, each order contributed 40.0 on average. The figure is an average in the strict statistical sense: individual orders will be larger or smaller, but the mean captures the typical transaction size in a single number. It is one of the first metrics any online retailer watches because it turns a messy stream of transactions into a simple, comparable figure.

The metric comes from ecommerce, where the cost of attracting a visitor is high and growth is usually decomposed into two levers: more orders or larger orders. Traffic and conversion rate determine how many orders arrive, while AOV determines how much each one is worth. Because paid advertising has to be bought for every additional visitor, lifting AOV is often the cheaper route to more revenue. A ten per cent rise in AOV adds ten per cent to revenue with no change in traffic, whereas ten per cent more traffic usually costs ten per cent more in acquisition spend.

The direction of the calculation is worth stating explicitly. Hold revenue fixed at 48,000 and let the order count rise from 1,200 to 2,400: the AOV halves from 40.0 to 20.0, because the same money is spread across twice as many baskets. Hold the order count fixed at 1,200 and let revenue rise to 60,000: the AOV climbs to 50.0. Confusing the two directions is common when reading a dashboard, since a rising order count is normally good news even when it pulls the average order value down. Always check which of the two inputs actually moved.

Multiplying the AOV by a round block of orders gives an instinctive sense of scale. At an AOV of 40.0, every hundred orders is worth 4,000.0, and a thousand orders is worth 40,000.0. This simple scaling is useful for quick mental forecasts and for explaining the metric to colleagues who do not work with ratios every day. It also makes the value of conversion improvements tangible: if a campaign lifts monthly orders by three hundred, the expected revenue gain is three times 4,000.0, or 12,000.0.

Turning the relationship around answers a different and equally practical question: how many orders are needed to hit a revenue target? Divide the target by the AOV and the required order count follows. With a 60,000 target and an AOV of 40.0, the answer is 1,500.0 orders, compared with the 1,200 actually placed. That gap of 300 orders is the concrete distance between current performance and the goal, and it can be attacked through conversion, traffic or basket size. Expressing the gap in orders rather than in abstract currency makes it far easier to assign to a team.

AOV sits in a small family of ecommerce ratios. Conversion rate measures the share of visitors who become buyers, while average order value measures what those buyers spend. Customer lifetime value multiplies an average purchase value by the number of purchases a customer makes over time. Revenue growth rate then describes how the top line changes between periods. Reading AOV alongside these measures separates a basket-size problem from a traffic problem, which is why it appears in almost every marketing dashboard. A single ratio cannot tell you whether shoppers are missing or simply spending too little.

Because AOV is a mean, it is sensitive to unusual transactions. A handful of wholesale buyers placing very large orders can pull the figure well above what a typical shopper spends. Analysts therefore often look at the median order value too, which is the middle value once orders are sorted from smallest to largest. If the mean is much higher than the median, the distribution is skewed and a single headline AOV may mislead. Reporting both, and segmenting by customer type, gives a fairer picture of ordinary behaviour. The gap between the two is itself a useful clue about who is really driving revenue.

The definition of an order matters as much as the arithmetic. Most retailers count one order per completed transaction, regardless of how many different items it contains, so buying five products in one basket is one order, not five. Revenue should be net of refunds, cancellations and discounts wherever possible, otherwise the average is inflated by money that was returned. The period must be identical for both inputs: a full month of revenue divided by a fortnight of orders produces a nonsense figure. Currency also needs care when a business sells in more than one, since mixing currencies before conversion distorts the mean and quietly favours whichever rate was used.

The three relationships on this page are simply rearrangements of one another. AOV is revenue divided by orders; revenue per hundred orders is AOV scaled by a hundred; and orders needed for a target is that target divided by AOV. Once the first figure is known, the others follow without any new data. That is why the calculator uses a single helper named aov and reuses it for both companion outputs. Master the division and the rest is arithmetic, which makes this one of the most approachable metrics in the whole of ecommerce.

Formula

AOV = R / N

Formula page →

Total revenue divided by the number of orders in the same period. With R equal to 48,000 and N equal to 1,200, the result is 40.0 per order.

SymbolMeaning
RTotal revenue
NNumber of orders

Revenue per 100 orders = AOV x 100

Formula page →

Scale the average to a round block of orders for quick forecasting. An AOV of 40.0 gives 4,000.0 per hundred orders.

SymbolMeaning
AOVAverage order value
nBlock size

Orders needed = T / AOV

Formula page →

Divide the revenue target by the average order value. A target of 60,000 at 40.0 per order requires 1,500.0 orders.

SymbolMeaning
TRevenue target
AOVAverage order value

How To Calculate Average Order Value

  1. 1

    Fix the period and gather both inputs

    Choose a single reporting period, such as one month or one quarter, and take total revenue and the number of orders from that exact window. Use net revenue wherever possible, meaning sales after refunds, cancellations and discounts have been removed. Mixing a full quarter of sales with a single month of orders is the fastest way to produce a figure that looks plausible but means nothing.

  2. 2

    Decide what counts as an order

    Count one order for each completed transaction, not for each item or each unit shipped. A single basket containing five products is one order, and that is the convention the metric assumes. If the business counts repeat deliveries or split shipments separately, keep the definition consistent between the revenue figure and the order count so that the numerator and denominator describe the same things.

  3. 3

    Divide revenue by the order count

    Compute average order value as total revenue divided by the number of orders. With 48,000 of revenue and 1,200 orders the result is 40.0. The calculator stores this as a helper named aov and reuses it below. Keep a few decimal places while checking, but remember this is an average: individual orders will sit above and below it, and a small number of bulk purchases can shift it noticeably.

  4. 4

    Scale the AOV to a round block of orders

    Multiply the AOV by one hundred to see the revenue generated by every hundred orders. At 40.0 per order that is 4,000.0. This figure is handy for quick forecasts: an extra three hundred orders should add roughly 12,000.0 of revenue at the same AOV. It is a linear scaling, so doubling the block doubles the revenue and halving it halves the revenue.

  5. 5

    Find the orders required for a revenue target

    Divide the revenue target by the AOV to learn how many orders are needed. A target of 60,000 at 40.0 per order requires 1,500.0 orders. Compare that with the orders actually placed to see the size of the gap. Because the AOV sits in the denominator, a higher average means fewer orders are needed, which is exactly why improving basket size is such an attractive lever.

Examples

Example 1: The worked default — 48,000 from 1,200 orders

totalRevenue
48000
numberOfOrders
1200
targetRevenue
60000
StepCalculationResult
Average order valuetotalRevenue / numberOfOrders40.0
Revenue per 100 ordersaov * 1004000.0
Orders needed for targettargetRevenue / aov1500.0

Result: For 48,000 of revenue and 1,200 orders the AOV is 40.0, every hundred orders earns 4000.0, and a 60,000 target requires 1500.0 orders.

Example 2: Larger baskets — same revenue from fewer orders

totalRevenue
48000
numberOfOrders
800
targetRevenue
60000
StepCalculationResult
Average order valuetotalRevenue / numberOfOrders60.0
Revenue per 100 ordersaov * 1006000.0
Orders needed for targettargetRevenue / aov1000.0

Result: With 800 orders the AOV rises to 60.0, a hundred orders earns 6000.0, and the 60,000 target now needs only 1000.0 orders.

Example 3: A larger store planning its next quarter

totalRevenue
250000
numberOfOrders
5000
targetRevenue
400000
StepCalculationResult
Average order valuetotalRevenue / numberOfOrders50.0
Revenue per 100 ordersaov * 1005000.0
Orders needed for targettargetRevenue / aov8000.0

Result: At 250,000 from 5,000 orders the AOV is 50.0, a hundred orders earns 5000.0, and the 400,000 target calls for 8000.0 orders.

Calculator

Average order value

$40.00

Revenue per 100 orders
$4,000.00
Orders needed for target
1,500

Values update as you type. This calculator covers the single scenario its formula assumes — see Common Mistakes for what it leaves out.

Prefer a full-width tool? Open the Average Order Value calculator page.

Common Mistakes

  • Mixing reporting periods

    Revenue taken from a whole quarter and an order count taken from one month gives an average that is roughly three times too high. Both inputs must cover identical dates. The same caution applies after a system migration or a change in how orders are recorded, when one side of the division may silently cover a different span than the other.

  • Counting items instead of orders

    A basket with five products is one order, not five. Dividing revenue by item count produces average item value, a different metric that will be lower whenever customers buy more than one thing at a time. State clearly which denominator is in use before comparing figures from different teams, dashboards or tools.

  • Forgetting refunds and cancellations

    Gross revenue includes sales that were later returned, but the cash never stayed. Working from gross revenue while the order count excludes cancelled orders inflates the average and flatters performance. Use net revenue and a matching order definition, and apply the same rule consistently in every period you compare.

  • Trusting a skewed mean without checking the median

    A few large wholesale orders can pull the average well above the typical shopper's basket. If the mean and median are far apart, the headline AOV is describing an outlier rather than ordinary behaviour. Report both and segment by customer type before setting targets from a single number.

  • Confusing AOV with revenue per customer

    Revenue per customer divides by the number of customers, not orders, and it rises when a customer orders repeatedly even if basket size is unchanged. AOV says nothing about how often a person buys. Use customer lifetime value when the question concerns a person's total contribution rather than a single transaction.

  • Assuming AOV stays fixed as order volume changes

    The orders-needed calculation treats AOV as constant, but discounts, promotions and a changing product mix can move it at the same time as volume changes. A campaign that brings in many small orders can lower the average and miss its revenue target. Recheck the AOV after any major change in traffic or pricing.

FAQ

What exactly does average order value tell me?

It tells you the average amount spent each time an order is placed. Divide total revenue by the number of orders in the same period and you have the typical basket size in a single figure. At 48,000 of revenue from 1,200 orders the AOV is 40.0. It is an average, so individual baskets will be larger or smaller, but it is a fast way to compare periods, campaigns and customer segments.

How do I calculate AOV?

Take total revenue for a chosen period, count the completed orders in that same period and divide one by the other. The result is revenue per order. With 48,000 and 1,200 orders you get 40.0. Keep the definition of an order consistent, count one per transaction rather than per item, and use net revenue so that refunds and cancellations do not inflate the figure.

Is a higher AOV always better?

Usually, because more revenue arrives from the same traffic, but not always. If a rise in AOV comes from pushing customers to buy things they did not want, returns and dissatisfaction can offset the gain. AOV can also rise simply because a few large wholesale orders landed in the period. Read it alongside conversion rate, repeat purchase rate and margin before celebrating an increase.

How many orders do I need to reach a revenue target?

Divide the target by the AOV. At an AOV of 40.0, a 60,000 target requires 1,500.0 orders. If the store is currently placing 1,200, the gap is 300 orders. Remember that the calculation assumes the AOV stays constant, so revisit it if a campaign changes the product mix or introduces discounts.

What is the difference between AOV and average item value?

AOV divides revenue by orders, while average item value divides revenue by the number of individual products sold. When shoppers routinely buy several items in one basket, the item value is the smaller figure. Both are useful: AOV tracks basket size, whereas item value helps with pricing and product mix decisions.

How do refunds and bulk orders affect AOV?

Refunds should be removed from revenue, or the average is overstated by sales that were returned. Bulk orders pull a mean upward because a handful of very large baskets carry disproportionate weight. Check the median as well as the mean and consider reporting the two separately so that ordinary shopper behaviour is not hidden by a few exceptional transactions.

References