What is average unit retail (AUR)?

AUR = net sales ÷ units sold. It's the average price actually realized per unit across every transaction, discount, and markdown that happened during the period — not the price on the ticket. If a store sells 500 units for $18,000 in net sales, AUR is $36, even if the original ticket price was $50.

What does AUR stand for in retail?

AUR stands for average unit retail, sometimes called average selling price (ASP). It measures realized revenue per unit sold, which makes it the fastest single number for tracking how much of the original ticket price a category is actually collecting once markdowns and discounts are applied.

How do you calculate AUR?

Divide net sales dollars by units sold for the same period: AUR = net sales ÷ units sold. Net sales should already reflect any returns and discounts. Calculate it per SKU, per class, or store-wide — the narrower the slice, the more clearly AUR shows price drift in a specific category rather than an average across unrelated ones.

What is the difference between AUR and AOV or ATV?

AUR is revenue per unit; average order value (AOV) or average transaction value (ATV) is revenue per transaction. AOV divided by units per transaction (UPT) equals AUR. A rising AOV driven entirely by shoppers buying more units, with a falling AUR per unit, still signals markdown pressure that AOV alone would hide.

Why is falling AUR the earliest sign of markdown drift?

AUR reacts to every price break the moment it happens, before weekly sell-through reports or end-of-month margin statements catch up. A category-level AUR trending down week over week — even while unit sales look healthy — usually means more units are selling at deeper discounts than the plan assumed, which is exactly the pattern that erodes maintained margin.

How do you read AUR against maintained margin?

AUR falling toward cost is fine if it was planned — maintained margin still holds if the reduction matched the plan. AUR falling faster than the planned schedule, with maintained margin sliding alongside it, means price cuts are running ahead of the plan and the next markdown decision needs to be reconsidered before it compounds.

What is a good AUR as a percentage of original ticket price?

There's no universal target — it depends entirely on your planned markdown cadence and category. The useful comparison is AUR against your own plan's blended expected price for that point in the season, not against a generic benchmark. A material gap below plan is the actionable signal, regardless of what the raw percentage is.

Average unit retail (AUR) calculator

AUR = net sales ÷ units sold. It's the price a category actually realized, blended across every unit sold at full price, at a markdown, or on a discount during the period. Because AUR moves the instant a price break happens, a category-level AUR that's sliding faster than planned is usually the earliest visible symptom of markdown drift — well before a margin statement catches it.

Check sell-through against AUR Maintained markup calculator

AUR versus ticket price, AOV, and UPT

AUR is not the ticket price — it's the realized average across every unit sold at every price point that occurred. It's also not the same thing as average order value (AOV) or average transaction value (ATV), which measure revenue per transaction rather than per unit. The two connect through units per transaction (UPT): AOV ÷ UPT = AUR. A store can grow AOV purely by selling more units per basket while AUR per unit keeps sliding — which is why AUR needs to be read on its own, not inferred from AOV.

Worked example: net sales of $18,000 across 500 units sold in 320 transactions gives AUR = 18,000 ÷ 500 = $36.00, UPT = 500 ÷ 320 = 1.56, and ATV = 18,000 ÷ 320 = $56.25. If the original ticket price was $50, AUR is running at 72% of ticket — a useful number only once it's compared against what the plan expected at this point in the markdown cadence.

AUR and transaction mix

Net sales ($)

Units sold

Transactions

Original ticket price ($)

AUR (average unit retail): $36.00
Units per transaction (UPT): 1.56
Average transaction value: $56.25
AUR as % of ticket price: 72.0%
Implied blended markdown: 28.0%

Implied blended markdown assumes net sales reflect actual realized pricing with no other cost changes — it's a read on price realization, not a substitute for the planned markdown schedule.

AUR and maintained margin across a four-stage markdown cadence (illustrative, 65% starting IMU)

Cadence stage	Retail price	Cumulative AUR	AUR as % of ticket	Maintained margin
Full price	$50.00	$50.00	100%	50%
1st markdown (20% off)	$40.00	$44.10	88%	45%
2nd markdown (40% off)	$30.00	$37.80	76%	38%
Clearance (60% off)	$20.00	$28.90	58%	29%

Cumulative AUR blends prior full-price and discounted units sold with the current stage's units, which is why it declines more gradually than the current price. Figures are illustrative — replace with your own class-level history.

Reading AUR movement, not just its level

A falling AUR is not automatically a problem — if the plan called for a markdown this week, AUR should fall, and maintained margin should hold at the planned level. The signal worth acting on is AUR falling faster than the schedule assumed, or maintained margin sliding at the same time AUR falls, which together mean units are moving through at deeper discounts than the plan budgeted for.

Track AUR at the class or SKU level, not just store-wide — a store-wide AUR can look stable while masking one category running well behind plan and another running ahead of it. The narrower the slice, the sooner the drift is visible and the sooner the next markdown decision can be adjusted before it compounds across the rest of the season.

Reading AUR week to week

What to check alongside AUR before reacting

AUR against the plan, not against last week

Compare to schedule

A week-over-week drop is expected once a markdown fires. Compare AUR to what the plan assumed for this point in the cadence, not just to the prior period.

Maintained margin moving with it

The margin check

AUR falling as planned with maintained margin holding is a plan executing normally. AUR and margin both sliding below plan is drift worth acting on.

UPT and transaction count

Separate volume from price

A rising unit count with falling AUR could mean the markdown is working as intended, or that units are simply being given away. Check sell-through velocity alongside AUR before deciding which.

Keep planning

Sell-through and markdowns
Pair AUR with weekly sell-through to separate velocity gains from margin loss.
Maintained markup calculator
Check whether the margin implied by current AUR matches the plan.
Initial markup (IMU) calculator
See the starting ticket AUR is drifting away from.
Retail markdown formulas
The full formula reference AUR sits alongside.

Answers

Average unit retail questions

Compare realized AUR against your planned markdown schedule

Model the planned price at each markdown stage and see where actual AUR is running ahead of or behind the plan.

Free, no sign-up, with CSV export and a shareable link. Pro ($29/mo) saves named season plans, imports inventory CSVs, and prints a decision memo.

Open the markdown planner