Average Order Size
Also known as: items per order, IPO
Average number of items per completed order.
Average Order Size is a metrics & economics concept that ecommerce teams touch every week, usually without agreeing on a definition first. This page sets out what it means, how to apply it at catalog scale, what to measure, and where it breaks.
Definition
Average order size (units per order) is total units sold divided by total orders. It complements AOV — you can raise AOV via more items or via a higher-priced hero SKU.
Why it matters
Understanding whether AOV moves via bundle depth or unit price changes the correct merchandising response.
Formula
Avg Order Size = Total Units ÷ Total Orders
Average Order Size in practice
Average order size (units per order) is total units sold divided by total orders. It complements AOV — you can raise AOV via more items or via a higher-priced hero SKU. This is an economics metric, which means it is only useful next to the other numbers in its chain. On its own it can be gamed: a great number on a tiny denominator tells you nothing, and a poor number can be the correct trade for volume. Read it alongside spend, order volume, contribution margin and the time window the platform used to attribute the result. Read it next to AOV (Average Order Value), Conversion Rate (CVR).
How to calculate and use it
The calculation itself is simple — Avg Order Size = Total Units ÷ Total Orders — and the judgement is entirely in the inputs and the window you choose. Treat the metric as a decision rule, not a scoreboard. Write down the threshold at which you would scale, hold, or cut before you look at the report — then let the number answer that question. Segment by campaign objective, audience temperature and creative concept, because a blended figure hides the two or three line items actually moving it. Worked through: 3,600 units across 1,200 orders → 3.0 items/order.
What to measure and watch
Pull the number from one source of truth and keep the window fixed. Platform reporting, your analytics suite and your order system will disagree, usually because of attribution windows and refunds. Pick the system your P&L trusts, note the window, and compare like-for-like week over week rather than chasing daily noise. Why this matters commercially: Understanding whether AOV moves via bundle depth or unit price changes the correct merchandising response.
Where Average Order Size sits in an agentic creative workflow
Xeli reads this metric back to the creative and the SKU that produced it, so the next production run is weighted toward what actually paid. Instead of a spreadsheet reconciling creative names to results, each rendered asset carries its concept, offer, ratio and product ID — which turns the metric into a brief for the next batch. In the context of metrics & economics, that means the concept stops being something a person re-applies by hand every campaign and becomes a rule the system enforces on every asset it produces.
Failure modes worth naming
The recurring problems are predictable: reporting only aov without units per order; missing bundle vs unit-price mix shift. Each of these is a process gap rather than a knowledge gap — which is why the fix is usually a checklist, a template or an automated rule instead of more training.
3,600 units across 1,200 orders → 3.0 items/order.
Common mistakes
- ✕Reporting only AOV without units per order.
- ✕Missing bundle vs unit-price mix shift.