Skip to main content
GlossaryFinancial Planning

Average Unit Retail (AUR)

In retail, AUR (average unit retail) is the average price paid per unit sold — net sales divided by units sold — the metric that ties pricing, markdowns and mix to the plan.

Need the live calculator? Run the AUR formula on your own numbers, with two worked examples →

Average unit retail (AUR) in retail means the average price a customer actually paid for one unit, calculated as net sales dollars divided by units sold over the same period. A brand that books $540,000 of net sales on 7,500 units has an AUR of $72.00. The number sits underneath every merchandise financial plan, because sales dollars are always units multiplied by AUR: change either one and the top line moves.

What does AUR mean in retail?

In retail, AUR answers a plain question: when a unit left the building, what did it sell for on average? It is not the ticket price, not the planned price, and not a list price from a line sheet. It is the realized price after every promotion, coupon, markdown and employee discount has been applied, and — if the brand calculates it properly — after returns have been netted out.

That makes AUR the honest read on pricing. A brand can hold ticket prices flat all season and still watch its AUR fall, because a growing share of units sold on promotion or at clearance. The reverse also happens: a brand that raises its ticket prices by 5% can see AUR rise by less than 5%, or not at all, if the higher ticket pushed more units into the markdown window.

AUR is also referred to as average selling price (ASP). The two names describe the same calculation; where a team draws a distinction, it should be written into the KPI definitions, because a plan that mixes a wholesale ASP (what the account paid the brand) with a retail AUR (what the consumer paid) will not reconcile.

AUR is measured at a grain. Brand-level AUR is a summary; the planning work happens at department, class, channel and price-tier level, where the number tells a planner something specific about mix and pricing discipline. A flat total AUR can hide a falling DTC AUR and a rising wholesale AUR — two problems that need two different interventions.

How to calculate AUR

The AUR calculation is one division:

AUR = Net Sales Dollars ÷ Units Sold

Both inputs must come from the same period and the same scope. If net sales covers four weeks and three channels, units sold must cover the same four weeks and the same three channels. When an AUR looks wrong, check the scope before the arithmetic: the division cannot fail, but mismatched periods, channels or return windows can.

The period matters as much as the scope. A weekly AUR is noisy — one promotional weekend moves it — and is read as a trend line against the plan rather than as a single point. A season-to-date AUR is the number the financial plan is measured on, because the buy, the open-to-buy dollars and the margin plan were all approved on a season AUR. Both are useful; they answer different questions and should not be compared with each other.

Gross versus net

Net sales is gross sales minus returns, and minus any allowances the brand treats as a reduction of revenue. Units sold should be net of returned units on the same basis. Using gross dollars over net units overstates AUR; using net dollars over gross units understates it. Pick the net basis for both and hold it.

InputGross basisNet basis (recommended)
Sales dollarsTransactions at the register, before returnsTransactions minus returned dollars
UnitsUnits scanned outUnits scanned out minus units returned
Where it misleadsHigh-return categories such as dresses and outerwear, DTC in particularRarely — but keep the return window consistent across periods

The markdown effect

Markdown dollars reduce the price at which a unit sells, so they reduce AUR directly. The gap between the AUR a plan assumed at ticket and the AUR actually realized is the per-unit cost of discounting. Multiply that gap by units and you have the sales dollars the markdowns consumed.

A worked example

A contemporary brand plans a season across three price tiers. The plan calls for 10,000 units.

TierTicket pricePlanned unitsPlanned sales at ticket
Opening price point$553,000$165,000
Core$905,000$450,000
Premium$1452,000$290,000
Total10,000$905,000

Full-price AUR = $905,000 ÷ 10,000 = $90.50.

The season ends with all 10,000 units sold, but markdowns taken across the season total $72,400 — an 8.0% markdown rate against sales at ticket ($72,400 ÷ $905,000 = 0.08). Net sales are therefore $905,000 − $72,400 = $832,600.

Realized AUR = $832,600 ÷ 10,000 = $83.26.

The markdown effect is $90.50 − $83.26 = $7.24 per unit, and $7.24 × 10,000 units = $72,400 — which ties back to the markdown dollars taken. The components sum, which is the check every AUR bridge should pass.

In hindsight the team decides the opening tier was too deep. For the next season it moves 500 units from opening to core, holding total units at 10,000:

TierTicket pricePlanned unitsPlanned sales at ticket
Opening price point$552,500$137,500
Core$905,500$495,000
Premium$1452,000$290,000
Total10,000$922,500

Full-price AUR rises to $922,500 ÷ 10,000 = $92.25. If the markdown rate holds at 8.0%, realized AUR becomes $922,500 × 0.92 ÷ 10,000 = $84.87. The mix move alone is worth $1.61 per unit, or $16,100 across the season, with no change to any ticket price.

AUR vs AUC vs IMU vs ASP vs average ticket

These five numbers are often confused because they all describe a price or a cost per something. They measure different things and they are used at different points in the planning cycle.

MetricFormulaWhat it describesWhen it is used
AUR (average unit retail)Net sales ÷ units soldRealized selling price per unitIn-season tracking, hindsight, financial plan
AUC (average unit cost)Total landed cost ÷ units (bought, for the buy; sold, for a margin read)Landed cost per unitMargin planning, buy costing
IMU (initial markup)(Ticket price − cost) ÷ ticket pricePlanned margin at the original ticketPre-season pricing and buy approval
ASP (average selling price)Same calculation as AURRealized selling price per unit; sometimes the price to a wholesale accountDepends on the team's definition — write it down
Average ticket (average transaction value)Net sales ÷ transactionsSpend per customer visitStore and e-commerce productivity

Two relationships matter in practice. First, AUR minus AUC is the realized margin per unit, and that margin is almost always lower than the IMU implied, because IMU is set at ticket and AUR is realized after markdown. A style ticketed at $90 with a $30 landed cost carries an IMU of ($90 − $30) ÷ $90 = 66.7%. If it realizes an AUR of $72, the margin per unit is $72 − $30 = $42, which is 58.3% of the AUR. The difference between 66.7% and 58.3% is the markdown effect expressed in margin terms. The initial markup formula and the average unit cost formula carry the detail, and the initial markup and gross margin glossary entries cover the terms.

Second, average ticket equals AUR multiplied by units per transaction (UPT). A store with a $72 AUR and a UPT of 1.5 has an average ticket of $108. A rising average ticket can therefore come from customers paying more per unit, buying more units, or both — and the two have different causes.

Why AUR moves

AUR changes for five reasons, and a planner reviewing a miss should be able to say which of the five explains most of it.

  • Price change. Ticket prices went up or down. This is the only driver that changes the price of an individual unit at full price, and it is the one most people assume when AUR moves.

  • Markdown and promotion. A larger share of units sold below ticket, or the average discount on those units grew. In a season that ran long on inventory this is the driver to check first, because clearing the excess means selling it below ticket.

  • Mix across price tiers. More units sold from the opening price point, fewer from premium — or the reverse. The worked example above shows this driver in isolation: no ticket changed, yet AUR moved by $1.75 at full price.

  • Size and color mix. Extended sizes, hero colors and core colors can carry different ticket prices or different markdown exposure. A season that sold through the hero color at full price and cleared the secondary colors at 40% off has a lower AUR than its ticket architecture implied, even though the option count and total units matched plan.

  • Channel mix. Channels carry structurally different AURs. A brand with a DTC AUR of $95 on 4,000 units and a wholesale AUR of $60 on 6,000 units has a blended AUR of ($380,000 + $360,000) ÷ 10,000 = $74.00. If the next season shifts to 3,000 DTC units and 7,000 wholesale units at the same channel AURs, the blend falls to ($285,000 + $420,000) ÷ 10,000 = $70.50. AUR dropped $3.50 without a single price or markdown changing.

The reason the decomposition matters is that each driver has a different owner. A price change is a pricing decision; markdown is an inventory decision made upstream in the buy; tier mix is an assortment architecture decision; channel mix is a distribution decision. Reviewing AUR as one number assigns the miss to nobody.

How planners use AUR

Converting open-to-buy dollars to units

Open-to-buy is planned in retail dollars, but purchase orders are written in units. AUR is the conversion. A receipt plan of $450,000 at retail against a planned AUR of $90 is a buy of 5,000 units. If the realized AUR for that class is running at $85, the same 5,000 units will generate $425,000 of sales, not $450,000 — a $25,000 gap that shows up in the merchandise financial plan unless the planner either buys more units or finds the AUR. What is open-to-buy planning? covers where this conversion sits in the OTB cycle.

Assortment architecture by price tier

An assortment architecture sets how many options and how many units sit at each price tier, and the weighted result is a planned AUR. Planners work the architecture backwards from the financial plan: if the department needs $905,000 at a 10,000-unit capacity, the tier mix must produce a $90.50 full-price AUR before markdowns. Depth decisions interact with this — the breadth vs depth trade-off is partly an AUR question, because deep buys at the opening price point hold the blended AUR down. Merchandise planning vs assortment planning explains how the dollar plan and the option-level plan hand this number back and forth.

Hindsight

In a season hindsight, planned AUR against realized AUR is the first bridge the team builds. The gap — $7.24 per unit in the example above, where all of it was markdown because units and tier mix landed on plan — is split into its drivers in a real season: how much came from markdown, how much from tier mix, how much from channel mix. How to hindsight a season walks through the sequence; the point here is that the AUR bridge is a sales-side bridge, and it should be reconciled with the margin bridge rather than merged into it.

The identity: sales = AUR × units

Every merchandise financial plan rests on this identity. If sales are planned up 6%, the plan must say whether that is 6% more units at the same AUR, the same units at a 6% higher AUR, or some combination — and each path implies a different buy, a different markdown exposure and a different assortment. A plan that grows sales without stating the AUR assumption has not stated a plan.

AUR by vertical

The arithmetic is identical across verticals. What changes is the unit the number describes and the mix drivers that move it.

  • Footwear. AUR is a price per pair. Size-run completeness drives it: a run that breaks early in core sizes pushes the remaining pairs — the fringe sizes — into markdown, and the pair AUR falls. Carryover model-year styles are bought to replenish and rarely enter clearance, so their pair AUR is steadier than that of seasonal styles that must clear before the next model year — and a shift in the carryover share of pairs sold moves the blend.

  • Accessories and bags. Small leather goods at opening price points sit alongside hero bags at several times the price, so the blended AUR is dominated by the mix between them. Attach selling, where a small item rides with a parent purchase, raises units faster than dollars and can lower AUR while improving the total ticket.

  • Home and furniture. A single AUR across a sofa and a cushion means little, so AUR is read by class, and often by option within a style, where fabric grade and finish set the price. Long lead times and container minimums mean the tier mix is largely fixed at the buy, months before a floor set; AUR drift in season is mostly a markdown and dealer-prebook signal.

  • Beauty. AUR is tracked per unit across formats and sizes, and shade-range sell-through moves it: the shades that clear at full price and the shades that need clearing before a gondola reset or before they fall under the retailer's remaining-shelf-life requirement have different realized prices.

  • Sporting goods. Seasonality by sport sets when units sell and at what price, and prebook orders from accounts lock a wholesale ASP months ahead. The blended AUR moves with the DTC-versus-prebook split as much as with any price change.

Markup and pricing by vertical covers how each vertical sets the ticket that AUR is realized against.

Common mistakes

  • Managing AUR in isolation. AUR is meaningless without units and margin. A higher AUR achieved by cutting lower-priced volume may reduce total sales dollars and gross margin dollars. AUR is managed alongside unit targets and margin rates, never instead of them.

  • Ignoring returns. In DTC, a high return rate on premium product distorts AUR if returns are not netted out of both dollars and units. Net AUR is the performance metric, especially for categories with high return exposure.

  • Conflating ticket price with AUR. AUR is the price consumers actually paid, not the price on the tag. A brand with $200 ticket prices and a 40% average discount has a $120 AUR, and its pricing architecture has to acknowledge that.

  • Setting a single AUR target across channels. Wholesale and DTC have structurally different AURs. A blended target obscures channel-level movement and prevents the team from acting where the miss actually occurred.

  • Mixing scopes. Dividing this month's net sales by last month's units, or three channels' dollars by two channels' units, produces a number that looks like AUR and is not.

In RetailNorthstar: AUR is tracked in real time across the assortment by category, channel, and price tier — with planned vs. actual AUR visible at every level, so merchandising teams can detect and respond to pricing erosion before it compounds.

RetailNorthstar Editorial Team
RetailNorthstar ·

Apply these concepts with RetailNorthstar.

See how apparel brands use RetailNorthstar to put connected merchandising planning into practice — OTB through allocation in one system.

No credit card. No commitments.

Connected merchandise planning — live in weeks, not quarters.