Take any retail chain and rank the stores by sales per labour hour. The gap between the top quartile and the bottom quartile is almost always enormous — often two to one, sometimes worse.
Now here’s the part that catches leadership off guard. Those stores usually have similar formats, similar footfall, and staff working similar hours. The bottom-quartile teams aren’t lazier. They’re often working harder, because they’re fighting the operation instead of running it.
Store-level productivity is rarely an effort problem. It’s a scheduling problem, a skills problem, or a visibility problem — and those three have very different fixes.
Start by finding out where the hours actually go
Most store managers can tell you their labour budget. Very few can tell you how those hours were spent yesterday.
Before you change anything, spend two weeks capturing where time goes across a representative sample of stores. Not a survey — observation and system data. You’re looking for the split between:
- Selling time — with a customer, doing the thing that generates revenue
- Replenishment and stock work — necessary, but schedulable
- Compliance and admin — checklists, audits, reports, cash reconciliation
- Waiting and searching — looking for stock, waiting for approval, waiting for a manager, looking for the one person who knows how to do something
That last category is the one nobody budgets for and everyone pays for. In stores that look “understaffed”, a meaningful share of the labour hour is going to search and wait time. Adding headcount doesn’t fix that. It just adds more people waiting.
The four levers that actually move store productivity
1. Match labour to demand, not to the rota template.
Most stores are staffed to a shape that made sense three years ago. Meanwhile footfall has shifted — later evening peaks, heavier weekend clustering, different behaviour around paydays and festival weeks.
Pull twelve months of transaction data at hourly granularity. Overlay the current schedule. The mismatch is usually obvious and usually expensive: overstaffed at 11am, badly understaffed at 6.30pm when conversion is highest and the queue is longest.
Fixing this alone often delivers the biggest single gain, and it costs nothing but the effort of rebuilding the schedule.
2. Move task work out of peak hours.
Every hour a staff member spends facing shelves during peak trading is an hour not spent converting a customer who is standing right there. Replenishment, price changes, cycle counts and back-office admin belong in the trough hours.
This sounds obvious. It’s routinely violated, because tasks arrive from head office with a deadline and no guidance on when in the day to do them.
3. Close the skill gaps that create bottlenecks.
In most stores, a handful of tasks can only be done by a handful of people. Processing a return, overriding a price, opening the safe, handling a warranty claim, operating a specific piece of equipment.
When those people are on a break, on leave, or busy, everything queued behind them stops. One under-trained shift creates a queue that a fully staffed shift then has to clear.
Cross-training is the fix, and it’s cheap relative to what the bottleneck costs. But you can only target it if you know who can actually do what — which is where structured upskilling and skill assessment stops being an HR nicety and becomes an operations tool.
4. Give store managers their numbers daily, not monthly.
A monthly report tells a manager what went wrong four weeks ago. By then the shift is long gone and nobody remembers why.
Daily visibility — sales per labour hour, conversion, task completion, queue times — lets a manager adjust tomorrow’s shift based on today’s result. That feedback loop is where continuous improvement actually happens, and it’s the thing most chains never build.
Getting the metric right
Pick your primary store productivity metric carefully, because whatever you choose is what teams will optimise for.
| Metric | What it measures | The risk if used alone |
|---|---|---|
| Sales per labour hour | Revenue efficiency of scheduled time | Encourages understaffing and hurts service |
| Units per hour | Throughput | Ignores basket value and margin |
| Conversion rate | Selling effectiveness | Sensitive to footfall accuracy |
| Transactions per hour | Speed of service | Rewards rushing customers |
| Task completion rate | Operational compliance | Rewards box-ticking over outcomes |
Use two or three together, never one. Sales per labour hour paired with conversion and a customer satisfaction measure gives a balanced picture. Sales per labour hour on its own will get you a store that is quietly understaffed and losing customers you never see leave.
For the full picture on choosing and defining these, see the workforce productivity measurement guide.
Benchmark internally before you benchmark externally
Industry benchmarks are interesting. Your own top-quartile stores are actionable.
If store 34 is doing 40% more sales per labour hour than store 61 with comparable footfall and format, the practice that creates that gap already exists inside your business. Somebody has worked it out. Go and find out what they’re doing.
This is far more useful than a benchmark report, because the practice is already proven in your operating context, with your systems, your product mix and your customers. It also travels better — a store manager will listen to another store manager in a way they won’t listen to a consultant.
Where technology helps, and where it doesn’t
Being blunt about this: software does not fix a store that has no standard way of working. It just produces reports about the chaos faster.
Get the operating rhythm right first — clear task ownership, sensible shift shapes, defined skill requirements per role. Then technology multiplies it:
- Workforce analytics turns transaction and labour data into the demand curve you schedule against
- Digital task management replaces the WhatsApp-and-clipboard system with something you can measure, so you know whether a task was completed and how long it took
- Skill and competency tracking shows you the coverage gap by store and by shift, before it becomes a bottleneck
- Hands-free and connected devices cut the search-and-wait time in stockrooms and back-of-house
State Technologies builds this layer through its data analytics and digital intelligence practices, connecting store-level operational data into dashboards managers actually use during a shift rather than reports they read after it.
A realistic 90-day sequence
Days 1–14 — Measure. Capture where hours go across a sample of stores. Establish your baseline for sales per labour hour, conversion and task completion. Do not change anything yet.
Days 15–30 — Diagnose. Compare top and bottom quartile stores on the same metrics. Identify the two or three practices that separate them. Map the skill coverage gaps.
Days 31–60 — Pilot. Take five to eight stores. Rebuild schedules against the real demand curve. Move task work out of peak. Cross-train against the identified gaps. Give those managers daily numbers.
Days 61–90 — Measure and decide. Compare pilot stores to control stores over the same period. If the gain is real, you now have an internal case study and a group of store managers who can sell it to their peers far better than head office can.
Do not roll out to the whole estate in month one. A network-wide change with no evidence behind it is how good ideas get discredited.
Two things that quietly kill these programmes
Treating it as a cost-cutting exercise. The moment store teams believe productivity work is a prelude to cutting hours, cooperation ends and data quality collapses. Frame it as removing the friction that makes their job harder — and then actually remove it.
Measuring without changing anything. Installing dashboards and asking managers to review them, while leaving the schedule template, the task calendar and the training programme untouched, produces nothing except resentment about extra admin.
FAQs
What is store-level productivity?
Store-level productivity measures how much output a store generates relative to the labour hours it consumes. The most common expression is sales per labour hour, though a complete picture also needs conversion rate and a service quality measure alongside it.
How do I increase productivity without adding staff?
Start by matching the schedule to actual hourly demand rather than a fixed template, then move replenishment and admin work out of peak trading hours. Cross-train staff so that no single task depends on one person being available. Most stores recover meaningful capacity from these three changes alone.
What’s the best metric for measuring store performance?
Sales per labour hour is the standard, but it should never be used alone — on its own it encourages understaffing. Pair it with conversion rate and a customer satisfaction measure so improvements in efficiency don’t come at the cost of service.
How long before workforce optimisation shows results?
Scheduling changes usually show up within four to six weeks because the effect is immediate. Skills and cross-training work takes a quarter or more, since capability has to be built and then used. Run a pilot for at least 60 days before judging results.
Why do stores with similar footfall perform so differently?
Usually because of scheduling shape, skill coverage on shift, and how much time gets lost to searching and waiting. These rarely appear in standard reporting, which is why the gap looks inexplicable until someone observes the stores directly.
Does workforce analytics software fix store productivity?
Not on its own. Software makes an existing operating rhythm measurable and repeatable, but it can’t create one. Standardise how work is planned and assigned first, then use analytics to manage and improve it.
How much labour time is typically lost to non-productive activity?
It varies by format, but search time, waiting for approvals and duplicated admin routinely account for a significant share of the shift in stores without clear task ownership. The only way to know your number is to observe it directly for a couple of weeks.
