TL;DR
Basket size is the average value or quantity of a single completed order — used interchangeably with <a href="/glossary/aov" class="text-brand-600 underline decoration-brand-200 underline-offset-2 hover:text-brand-700">AOV</a> (when measured in dollars) or with <a href="/glossary/upt-units-per-transaction" class="text-brand-600 underline decoration-brand-200 underline-offset-2 hover:text-brand-700">UPT</a> (when measured in units). The term is ambiguous: some teams use it for dollar-weighted average, others for unit count. Always specify whether you mean basket dollars or basket units when reporting.
What is basket size?
Basket size is a retail and e-commerce term for the average value or quantity per completed order. It originated in brick-and-mortar retail (literal grocery basket) and migrated to e-commerce reporting where it is used somewhat ambiguously.
In dollar terms, basket size is identical to AOV. In unit terms, basket size is identical to UPT. Operators should specify which they mean when reporting; the unqualified term reliably causes confusion in cross-team conversations.
How to calculate it
Basket size (dollars) = Total revenue / Number of orders (identical to AOV) Basket size (units) = Total units sold / Number of orders (identical to UPT) Most retail / e-commerce platforms default to dollar basket size, but the term remains genuinely ambiguous in cross-functional reporting.
Why the ambiguity matters
The dollar-vs-units ambiguity matters operationally because the levers are different:
- Dollar basket size moves through pricing changes, premium-tier upsell, and unit-mix shifts toward higher-priced SKUs.
- Unit basket size moves through bundling, free-shipping thresholds, cart-page cross-sell, and pack-size design.
- A team reporting 'we lifted basket size 12%' could mean either, and the implications for next-quarter merchandising are different. Clarify which.
Benchmarks
Because basket size is used both ways, the benchmark depends on which definition is in use. See AOV for dollar-weighted benchmarks and UPT for unit-weighted benchmarks. Some indicative ranges:
| Category | Dollar basket size (AOV) | Unit basket size (UPT) |
|---|---|---|
| D2C consumables | $45–$120 | 1.7–2.3 |
| D2C apparel | $70–$180 | 1.5–2.0 |
| Beauty / cosmetics | $50–$110 | 2.0–2.8 |
| Single-product D2C | Equal to unit price | 1.0 |
How to disambiguate in reporting
- 1. Always pair basket size with the unit. 'Basket size $84' or 'basket size 1.5 units' — never just 'basket size 1.5'.
- 2. Use AOV and UPT directly when possible. The unambiguous terms are AOV (always dollars) and UPT (always units). Reserve 'basket size' for retail-conversation contexts where the term is established.
- 3. When both matter, report both. 'Basket: $84 / 1.5 units / $56 AUR' is the cleanest one-line summary because it shows all three components.
Related concepts
AOV is the dollar-weighted disambiguation. UPT is the unit-weighted disambiguation. Average Unit Retail (AUR) is the third leg of the decomposition: AOV = UPT × AUR.
At a glance
- Category
- Profit Intelligence
- Related
- 5 terms
Frequently asked questions
Is basket size the same as AOV?
Sometimes. When measured in dollars, basket size and AOV are identical. When measured in units, basket size is the same as UPT. The term itself is ambiguous; always specify the unit when reporting.
Why use 'basket size' instead of AOV or UPT?
Mostly for cross-channel retail conversations where the term is established and includes both wholesale, in-store, and online. In pure-D2C contexts, AOV and UPT are clearer because they're unambiguous.
How should you report basket size?
Always pair with the unit ($84 dollars OR 1.5 units). When both dollar-weighted and unit-weighted matter, report all three components: AOV, UPT, and AUR. The composite picture is what merchandising decisions actually act on.
Sources
- Shopify D2C benchmarks (2025)
- BigCommerce retail metrics
- Fairview customer data (D2C, 2025)
Fairview is an operating intelligence platform that reports the full basket decomposition — AOV, UPT, and AUR — segmented by acquisition channel and customer cohort, so the lever moving any of the three is visible rather than hidden inside an aggregate basket-size headline. Start your free trial →
Siddharth Gangal is the founder of Fairview. He built the three-component basket view after watching D2C operators argue across teams about whether 'basket size up 8%' meant pricing was working or merchandising was working — when the underlying data showed AUR was flat, UPT was up 0.15, and the lift was entirely driven by free-shipping-threshold mechanics. The headline number was the same; the operational interpretation depended entirely on the decomposition.
See it in Fairview
Track Basket Size automatically.
14-day free trial. No credit card. First data source connected in 5 minutes.