Store indicators: ticket, conversion, space, staff
For each store calculates average ticket, units per ticket, average unit price, conversion, sales per m² and per employee and comparable growth, and shows which stores lag.
At a glance
- What question does it answer?
- Which stores lag and in what: traffic, conversion, ticket or return on space and staff.
- What data is needed?
- Each store’s sales and number of tickets.
- How to read the result?
- Compare stores of one format. Low conversion with normal traffic is a question of range, price and staff; high conversion with low sales means a lack of traffic. Comparable sales show organic growth without new stores. Example on the default values: Four stores give chain revenue of RUB 12,547,500: average ticket RUB 5,690.48, UPT 2.0, average unit price RUB 2,845.24, conversion 9.26% and like-for-like sales −0.42%. The lowest conversion is in the outskirts mall store (7.5%). If traffic is normal and conversion low, look at assortment, price and staff work; if conversion is high and revenue low, traffic is missing. Next: “Store comparison across the chain” and “Store economics”.
Why and how to reason
Store revenue is a product: visitors x conversion x basket, and basket = units per basket x unit price. So the indicators break revenue into causes. Conversion = transactions / visitors: how many who came in bought. Average basket = revenue / transactions. UPT is units per transaction, AUR is average unit price. Revenue per m² and per employee show resource efficiency.
Like-for-like sales = revenue / last year’s revenue - 1, for stores that operated in both periods: that way growth is not mixed with the effect of openings.
Example. Network: revenue RUB 12.55 m, 2,205 transactions, basket RUB 5,690, 2 units per transaction, unit price RUB 2,845. Visitors 23,800, conversion 9.26%. Revenue is -0.4% against last year. A store with below-average conversion loses in traffic, one with a low basket loses in selling additional units.
When to use it
Use it for weekly and monthly store analysis, to understand where to look for the cause of lag. Assumption: the traffic counter works properly. Do not compare stores of different formats directly: an outlet and a boutique differ in basket and conversion. Compute like-for-like only for stores that operated a full period. Take the same dates as for the traffic data.
How to read the result
Look along the chain: traffic, conversion, basket, area, staff. Low conversion with good traffic is a problem of assortment, sizes, service. Low UPT is few add-on sales. A fall in like-for-like sales shows that without new points the network does not grow (-0.4% in the example). Decision: choose the main lever for each lagging store and set a goal on that metric, not on revenue in general. Then check whether it has changed after a month. Compare stores on the metric you can change: for some it is conversion (training, display), for others basket (add-on sales). Identify one leader on each metric and study what it does differently.
Common mistakes
Taking mall traffic without allowing for passers-by; not counting returned receipts; mixing comparable and non-comparable stores; computing conversion from total flow including staff. Also: confusing units per transaction with the number of lines. Also: comparing conversion of stores with different visitor-counting systems.
What data is needed?
- Each store’s sales and number of tickets.
- Optionally: units, visitors, area, staff, last year’s sales.
- Where to take it: revenue and receipts from the till report or 1C by store for the period; units from the units-sold report; visitors from counters (leave blank if you have none, conversion will not be calculated); area and staff from the store passport and the staffing table; last year’s revenue for like-for-like sales.
How it is calculated
| Step | Formula |
|---|---|
| Average ticket | Sales ÷ tickets |
| UPT, AUR | Units ÷ tickets; sales ÷ units |
| Conversion | Tickets ÷ visitors |
| Comparable sales | Sales ÷ last year’s sales − 1 |
Worked numbers
Default values from the app; in the interactive version you enter your own.
- Chain sales
- 12.5 m ₽
- Average ticket
- 5,690.48 ₽
- Units per ticket (UPT)
- 2
- Average unit retail (AUR)
- 2,845.24 ₽
- Conversion
- 9.3 %
- Comparable sales
- −0.4 %Only stores with last-year data.
Indicators by store
| Store | Ticket | UPT | Conversion | Per sqm | Per employee | Comp. |
|---|---|---|---|---|---|---|
| Central mall | 6,500 ₽ | 2 | 9 % | 34,125 ₽ | 455,000 ₽ | 5 % |
| High street | 6,000 ₽ | 2 | 9.5 % | 45,600 ₽ | 532,000 ₽ | −3.3 % |
| Suburban mall | 5,900 ₽ | 2 | 7.5 % | 25,153 ₽ | 398,250 ₽ | 3.9 % |
| Outlet | 4,500 ₽ | 2 | 11 % | 20,507 ₽ | 574,200 ₽ | −7.4 % |
The lowest conversion is at “Suburban mall” (7.5 %). If traffic is fine look at range, price and staff; if conversion is high but sales are low, traffic is short.
Nuances and limits
- Do not include stores opened less than a year ago in comparable sales.
- Visitor counters distort data in malls: check the counting method.
- Visitor counters in malls distort data: reconcile them with the tills.
- Do not include stores opened less than a year ago in like-for-like sales.