Store operations
How to Measure Store Productivity: Sales per Square Foot Is Not Enough
Store productivity is output per unit of the resource a store consumes: space, staff hours, walk-ins and conversations. Sales per square foot measures only the first, and in Indian retail the rent line is fixed for the lease term while staff hours and walk-ins change every week. To measure store productivity properly you need one number per resource and one execution measure that explains why the numbers differ between stores that share a rent line.
Four denominators, four productivity numbers
| Metric | Formula | Source | What it tells you |
|---|---|---|---|
| Sales per square foot | Monthly sales over carpet area | POS and lease | Whether the space earns its rent; fixed for the lease term |
| Sales per advisor hour | Sales over rostered floor hours | POS and roster | Whether staff hours are placed and used well |
| Revenue per walk-in | Sales over footfall | POS and counter | Whether the store turns traffic into money |
| Revenue per conversation | Sales over attended conversations | POS and conversation capture | Whether the advisor turns attention into money |
| Conversion per conversation | Bills over attended conversations | POS and conversation capture | The selling rate, separated from the unattended walk-ins |
A worked example: two stores, same rent line
Store A and Store B are both 1,200 square feet and both did 18 lakh rupees last month, which is 1,500 rupees per square foot each. On the rent line they are twins.
Store A rosters four advisors and had 1,100 walk-ins and 260 bills. Store B rosters six advisors and had 1,900 walk-ins and 250 bills. At 26 trading days and nine floor hours a day, A used 936 advisor hours and B used 1,404. Sales per advisor hour: A 1,923 rupees, B 1,282 rupees. Revenue per walk-in: A 1,636 rupees, B 947 rupees. Conversion: A 23.6 percent, B 13.2 percent.
B has 70 percent more traffic and the same sales. It is a conversion problem masked by footfall, and the rent-line number hid it. A is close to capacity: at 1,100 walk-ins and four advisors, the next rupee comes from a fifth advisor at peak, not from coaching.
Capacity or conversion: the question productivity has to answer
- Signs of a capacity problem: queues at the demo counter, conversations under four minutes at peak, walk-ins leaving unattended, conversion falling on Sundays only.
- Signs of a conversion problem: long conversations that end without a bill, low number-taken rate, one playbook step skipped in most conversations, offer quoted wrongly.
- Signs of a range or ticket problem: conversion fine, average ticket below cohort, customers asking for a variant the store does not carry.
The execution metric that explains the gap
In Store B, the productivity numbers say what is wrong and not why. The why is in the conversation: adherence on the demonstration and offer steps, and the share of walk-ins nobody attended. Borentis Floor scores consented conversations against the playbook, so revenue per conversation sits next to adherence by step for the same store and week. On the operations side, BorentisOps checklist completion tells you whether the demo units were working on the days conversion fell.
Roster hours, footfall and sales come from the retailer's own systems. Productivity measurement is a join, not a single tool.
Productivity by hour and by day
A store's staff hours are often in the wrong hours. Measure sales per advisor hour by hour band (11 to 2, 2 to 5, 5 to 8, 8 to close) and by day. In most Indian high-street and mall stores the 5 to 9 pm band on Saturday and Sunday carries 35 to 45 percent of the week's bills, and the roster is flat. Festive weeks move the peak earlier and widen it. A roster built from the hour-band numbers usually raises sales per advisor hour without adding a head.
A monthly productivity review in five lines
- Sales per advisor hour by store, against the cohort median.
- Conversion per conversation and unattended walk-in rate, to separate capacity from conversion.
- The one playbook step whose adherence best explains the conversion gap.
- The hour bands where advisor hours exceed demand and where demand exceeds advisors.
- One roster change and one coaching focus per store, with a date.
Frequently asked questions
What is a good sales per square foot in India?
It varies too much by category and format to quote a national figure: jewellery and mobile stores run many times the figure of apparel or furniture. Use your own cohort median by format and city tier, and read the trend rather than the level.
How do I measure productivity per employee in a retail store?
Use sales per rostered hour, not sales per head. Part-timers, festive temps and split shifts make per-head figures misleading. Hours are what the store pays for.
Is footfall conversion the same as store productivity?
It is one productivity number, revenue per walk-in expressed as a rate, and usually the one that moves most. It does not tell you whether the gap is unattended walk-ins or poor conversations, which is why conversion per conversation sits next to it.
Which productivity metric should an area manager track weekly?
Sales per advisor hour and conversion per conversation. The first says whether hours are placed well; the second says whether the selling is working.
Related reading
- Retail KPIs only the conversation can measure
- How to compare retail store performance fairly
- How to improve retail operational efficiency
- Sales Execution, the use case
Where Borentis applies this
- Execution Scorecards: See the floor before the P&L does.
- Playbook Adherence: Your playbook, finally observed.
- Walk-in Recovery: The customer who left is still yours.
Borentis is the Agentic Operating System for Customer Interactions, built for Indian retail floors: consented one-tap capture on the advisor's phone, every conversation scored against your playbook with the evidence behind every number, leads created when a number is heard, and coaching from your own best conversations.