Store KPI pack: traffic, conversion, ticket, revenue per m², payroll and shrinkage
A single store scorecard with formulas, plan and variance: traffic, conversion, average ticket, revenue per square meter, payroll and shrinkage. The store manager and head of retail use it to decide what drags revenue down and where to intervene: attraction, selling, space or staff.
Why this document
Store revenue is traffic times conversion times ticket, and a drop in each is cured differently. Looking only at revenue, the manager does not know what to change: bring people in, train sellers or change the assortment. So the head of retail and the store manager read the scorecard, while finance checks payroll and rent against space productivity. The indicators are therefore needed together and with identical formulas across all stores, otherwise comparing stores and paying sellers' bonuses loses its meaning.
At a glance
- What is this document and why is it needed?
- A single store scorecard with formulas, plan and variance: traffic, conversion, average ticket, revenue per square meter, payroll and shrinkage. The store manager and head of retail use it to decide what drags revenue down and where to intervene: attraction, selling, space or staff.
- Who owns the document and how often is it rebuilt?
- Run by the retail sales director and an analyst; at store level the store manager looks at it (days, weeks), the region and head office monthly; thresholds are approved by the commercial director.
- What mistakes are the most common?
- Comparing stores of different formats → wrong conclusions → compare within format, region and size. Measuring traffic by passers-by rather than entries → conversion understated → a door counter with staff excluded. Looking only at revenue per m² → the cause is lost → always break down the funnel and people.
For whom
- Brand
- A brand with own retail looks at these metrics by store and format to decide what to open and close, and for franchisees as a standards requirement; for wholesale customers only sell-out is visible if they share it.
- Retail
- A retailer builds network management on this: store ranking, norms for payroll and rent, staff incentives, space decisions; comparison is made within a format and region, not across the whole network.
What it consists of
1. Sales funnel
- Traffic (door counter) → receipts → conversion → average ticket (AOV) → units per transaction (UPT) → revenue; revenue = traffic × conversion × ticket.
2. Space and staff efficiency
- Retailer: Revenue per m² of sales area, revenue per employee (FTE), staff load (receipts per person per hour), payroll to revenue, rent to revenue, share of area for display and storage.
3. Stock quality
- Retailer: Share of complete size runs on the floor, availability of fast sellers (in-stock), turnover, full-price sales and share of price reductions.
4. People
- Retailer: Turnover, hiring time, time to planned productivity, share of salespeople with an individual plan, incentives and productivity by salesperson.
5. Losses and service
- Shrinkage, returns, complaints, store NPS, stock accuracy; share of identified receipts.
6. Plan, actual, variance
- For each metric: actual, plan, variance in units and percent, color by threshold, last year and the same period; comparison of comparable stores (LFL).
Who looks at what
- Brand: compares own stores and franchisees on the same indicators and decides on openings and closures from them; for wholesale customers sees only sell-out if the customer shares it.
- Retailer: builds a store ranking, payroll and rent norms and staff incentives; compares stores within a format and region, not across the whole chain.
Brand and retailer: what differs in practice
- Brand: compares the work of its own retail by stores of one format and counts the store contribution to the brand, not only revenue.
- Brand: uses conversion and receipt composition data for range decisions: what is bought together, where sizes are lacking.
- Brand: sets display and visual merchandising by a brand manual and checks it by photos and store audits.
- Brand: ties the staff schedule in the store to traffic peaks: revenue per employee matters more than payroll as a percentage of revenue.
- Brand: compares mono-brand and multi-brand stores separately: a multi-brand range and average ticket differ.
- Brand: ties seller bonuses to conversion and average ticket and not to gross revenue so as not to encourage discounts.
- Brand: compares franchise points on the same indicators as own ones but separately: they have their own costs and terms.
- Retailer: decides which indicators enter the store director bonus: conversion, average ticket and shrinkage, not only revenue.
- Retailer: uses door counters and till data in one report, otherwise conversion is computed on different bases.
How to read the result and what decisions follow
- Start the analysis with the largest bar in the bridge: most often it is conversion, and it is cheaper to work on sales at the door than to raise traffic.
- The point position on the conversion and ticket chart shows what to do: low conversion is staff work and size availability, low ticket is add-on sales and range.
- Decision: the store conversion and ticket plan, training, a schedule for peaks and the threshold at which a store is reviewed or closed.
Control checks
- The number of till receipts equals traffic times conversion and revenue equals receipts times average ticket.
- Store revenue in the report equals revenue in accounting for the period and the area for density is the sales area, not the total.
Where the data comes from
| Data source | Fields |
|---|---|
| Door counters | traffic by hour and day |
| Tills | receipts, revenue, units, returns, discounts, salesperson |
| HR and accounting | payroll, headcount, schedule, rent, utilities |
| Warehouse and counts | stock, losses, discrepancies, size runs |
How to build it step by step
- Step 1: Fix the definitions: what traffic is (entries, not passers-by), receipt (per till, excluding returns), sales area, FTE.
- Step 2: Collect data for the period from counters, tills, HR and accounting; reconcile totals with accounting revenue.
- Step 3: Compute the funnel: conversion, ticket, UPT, revenue; check that traffic × conversion × ticket equals revenue.
- Step 4: Compute space and people: revenue per m², per employee, payroll and rent to revenue.
- Step 5: Add losses, returns and turnover; insert plan and compute variance.
- Step 6: Find the main cause of revenue variance: traffic, conversion or ticket; decompose the difference by formula.
- Retailer: Step 7: Compare stores within a format and region; mark stars, stable and loss-making ones.
- Retailer: Step 8: Assign an action per store and a deadline; the next report checks the result.
Formulas
| Measure | Formulas | Note |
|---|---|---|
| Retailer: Revenue | Revenue = traffic × conversion × average ticket | All money excl. VAT. |
| Retailer: Conversion | Conversion, % = receipts ÷ traffic × 100 | Receipts without returns; traffic from the door counter. |
| Retailer: Revenue per m² | Revenue per m² = revenue ÷ sales area | Use the same area base for comparisons: sales area, not total. |
| Retailer: Payroll and rent to revenue | Share, % = cost ÷ revenue × 100 | There is no single norm, rely on your own format and network data; foreign values only as a hint. |
| Retailer: Effect of conversion on revenue | Δrevenue = traffic × Δconversion × ticket | Likewise for traffic and ticket; the sum of effects gives the full variance (allowing for the mixed effect). |
| Retailer: Staff turnover | Turnover, % = leavers in the period ÷ average headcount × 100 | Also compute for newcomers (under 3 months): early exits cause hiring and training losses. |
Formulas in notation
- Store revenue
R = T × c × A
T traffic, c conversion, A average ticket. Example: 9,000 × 11% × 6,200 = RUB 6,138,000.- Average ticket
A = UPT × ASP
UPT units per transaction, ASP average price per unit. Example: 2.1 × RUB 2,952.- Revenue per m² and per employee
D = R / S; E = R / FTE
Example: RUB 51,150 per m² and RUB 767,250 per employee.- Revenue lost to a conversion shortfall
Δ = T × (c_plan − c_act) × A
Example: 90 receipts × RUB 6,200 = RUB 558,000.- Staff turnover
t = Leavers / Average headcount
Example: 38% per year (illustrative numbers).
Worked example
Store scorecard for a month: actual, plan and variance
| Metric | Formula | Actual | Plan | Var. |
|---|---|---|---|---|
| Traffic (visits) | door counter | 9,000 | 9,500 | |
| Conversion, % | receipts ÷ traffic | 11.0 | 12.0 | −1.0 |
| Receipts | traffic × conversion | 990 | 1,140 | |
| Average ticket (AOV), RUB | revenue ÷ receipts | 6,200 | 6,000 | 200 |
| Units per transaction (UPT) | units ÷ receipts | 2.1 | 2.2 | −0.1 |
| Revenue, RUB | receipts × ticket | 6,138,000 | ||
| Revenue per m², RUB | revenue ÷ sales area | 51,150 | 52,000 | −850 |
| Payroll to revenue, % | payroll ÷ revenue | 10.4 | 10.0 | 0.4 |
| Rent to revenue, % | rent ÷ revenue | 11.4 | 11.0 | 0.4 |
| Revenue per employee, RUB | revenue ÷ FTE | 767,250 | 780,000 | −12,750 |
| Shrinkage, % | loss ÷ revenue | 0.9 | 0.8 | 0.1 |
| Turnover, % per year | leavers ÷ average headcount | 38 |
Traffic of 9,000, conversion of 11.0% and 990 receipts at RUB 6,200 give revenue of RUB 6,138,000 (2,079 units, average unit price RUB 2,952). Revenue per m² is RUB 51,150, per employee RUB 767,250, payroll 10.4% and rent 11.4% of revenue. Conversion is 1.0 pp below plan: at the same traffic that is 90 receipts or RUB 558,000 a month. Plans and thresholds in the example are notional: there is no single norm for payroll, rent and conversion.
Figures
- positive
- negative
- total
Data as a table
| Step | Change | Level |
|---|---|---|
| Plan | — | 6.84m |
| Traffic | −360k | 6.48m |
| Conversion | −540k | 5.94m |
| Average ticket | +198k | 6.14m |
| Actual | — | 6.14m |
Why store revenue differs from plan: traffic, conversion, average ticket. Revenue equals traffic times conversion times average ticket; the deviation is decomposed sequentially into three effects. Loss from conversion RUB 558,000 with a shortfall of 1.0 pp. Illustrative figures.
- Actual
- Plan
Data as a table
| Measure | Actual | Plan |
|---|---|---|
| Payroll | 10.4 | 10 |
| Rent | 11.4 | 11 |
| Shrinkage | 0.9 | 0.8 |
Load on revenue: actual and plan. The share of payroll, rent and shrinkage in revenue: lower is better; exceeding the plan shows where the store loses profit.
Data as a table
| Conversion, % | Average ticket, RUB | |
|---|---|---|
| 11 | 6,200 | Actual |
| 12 | 6,000 | Plan |
| 12 | 6,200 | Actual ticket at planned conversion |
Conversion and average ticket: actual and plan. The store position relative to plan on the conversion and average ticket plane shows what is weaker: turning visitors into receipts or the size of the receipt.
Specifics by category
- Apparel
- Apparel: conversion and UPT depend on fitting rooms and consultation; revenue per m² depends on assortment turnover; seasonal peaks require a weekly scorecard.
- Footwear
- Footwear: higher ticket and lower UPT (usually one pair), higher conversion among visitors with intent; depth by size is needed, so size availability is the key metric.
- Accessories
- Accessories: high ticket per unit and small area, high revenue per m², but a higher loss risk and a bigger role for checkout merchandising.
- Kids
- Kids: higher UPT (sets, several children), average ticket; seasonality by school and holidays; a higher share of size returns.
- Men
- Menswear: higher conversion (mission shopping), steadier ticket, lower UPT; a bigger contribution from repeat purchases of core items.
- Women
- Womenswear: lower conversion at higher traffic (browsing), higher UPT and add-on sales; stronger effect of assortment and display.
Common mistakes
- Comparing stores of different formats → wrong conclusions → compare within format, region and size.
- Measuring traffic by passers-by rather than entries → conversion understated → a door counter with staff excluded.
- Looking only at revenue per m² → the cause is lost → always break down the funnel and people.
- Counting payroll without bonuses and contributions → share understated → include full accruals and contributions.
- One threshold for all stores → false red zones → thresholds by format and region.
Russian specifics
- Labor Code: working time and overtime (Arts. 91, 152) limit schedules and the cost of staff hours; account for this in payroll and productivity. Rule: Labor Code Art. 152: Labor Code, Art. 152 (overtime pay).
- Insurance contributions and the contribution base limit affect payroll including taxes; parameters change, check them at the calculation date. Rule: Decree 1705 of 31.10.2025: Government Decree of 31.10.2025 No. 1705 (contribution base limit).
- There are no uniform norms in Russia for conversion, ticket, payroll or rent to revenue; the company sets thresholds from its own data. Ranges from foreign practice are only a hint.