Free retail staffing and checkout wait calculator (Google Sheets)

What the calculator answers

Two questions come up in almost every store operations review, and most stores answer both with a guess:

1. Which hours are we actually short on the floor? Not short on the schedule. Short where shoppers are.
2. How long are people waiting to pay? Not on average across the day. In the hours that matter.

The Retail Staffing and Checkout Calculator answers both from numbers a store can collect this week. It is a free Google Sheets template: the link opens a Make a copy screen, and the copy is yours to edit. Nothing you enter comes back to us.

It is built on the methods in two of our guides, customer-to-staff ratio by hour and how to measure checkout wait time. Those guides explain the why. The template does the arithmetic.

The three tabs

Inputs are blue text on a yellow background. Everything else is a formula. Hours and snapshots above target turn orange.

The two formulas

Both tabs rest on Little's Law, a result from queueing theory first proved by John Little in 1961: the average number of people in a system equals the rate they arrive multiplied by the average time each one spends there. Know two of the three and you can work out the third. Little later described the law as being "in the measurement business, not the forecasting business," which is exactly how this template uses it: to make sense of counts you already took.

Hourly coverage uses it to turn door entries into the number of shoppers in the store at once:

Checkout wait uses it the other way round, to turn line counts into a wait:

Both are estimates that assume each hour or period is reasonably steady. Use them to find the hours worth fixing, not as exact measurements of any one shopper.

The example store, read hour by hour

The sheet opens with numbers already filled in. They describe a hypothetical store on a Saturday, built to show the method. They are not customer data.

The store logs 491 entries between 10:00 and 20:00, with an average visit of 17 minutes and a target of no more than 6 shoppers per associate on the floor. Here are the hours that matter:

Three hours are flagged, and they are flagged for two different reasons:

• 13:00 and 18:00 are deployment problems. The schedule was reasonable (four people at 13:00), but only two were on the floor. Lunch breaks and a stockroom task landing in the busiest hour would produce exactly this. Conversion in those hours is the lowest of the day.
• 17:00 is a scheduling problem. Everyone booked was on the floor, and there still were not enough of them for the after-work rush.

Across the whole day the store runs at 14.9 entries per scheduled associate-hour, a number that looks unremarkable in a weekly report. The hourly view is what shows where the day went wrong, and the fix is different for each kind of hour: move breaks and tasks out of 13:00 and 18:00, and add a person at 17:00.

The checkout tab tells a similar story. From 12:00 to 14:00 the example store records a line count every two minutes (60 snapshots) and 168 transactions from the POS:

• Average people waiting: 3.7
• Checkouts per minute: 168 ÷ 120 = 1.4
• Estimated average wait: 3.7 ÷ 1.4 = 2.6 minutes

An average under three minutes sounds fine. But the line was at or above the target of 6 people in 14 of 60 snapshots, about 23% of the period or roughly 28 minutes, and in 10 of those 14 a scheduled register was closed. The average hides both the problem and its cause.

How to set your own target

The template ships with a target of 6 shoppers per associate on the floor. Treat it as a placeholder.

Research on retail traffic supports the idea that a store's own data, not an industry benchmark, should set the line. Perdikaki, Kesavan and Swaminathan (2012) found that sales grow with traffic but conversion falls as traffic rises, and that more labor softens that fall with diminishing returns. In other words, there is a level of shoppers per associate where service starts to slip, and it is different for each store format.

To find yours:

1. Collect four or more weeks of hourly entries, transactions and floor counts for a few representative stores.
2. Group the hours by shoppers per associate on the floor (for example under 3, 3 to 5, 5 to 7, 7 to 9, above 9).
3. Compute conversion for each group.
4. Find the bend where conversion starts to drop faster. Enter that level as your target.

Then manage by exceptions: hours per week above target, by store, and why.

How to get good numbers in

• Entries: from a door counter, by hour. Exclude staff if your counter allows it, or entries will look high around shift changes.
• Visit length: from your counter's dwell report if it has one. Otherwise time a sample of shoppers on a few days. It changes by daypart, so if your lunch visits are short and weekend visits are long, use separate copies.
• Associates on the floor: count them, at the same minute each hour. This is the column most stores have never measured and the one that most often explains a bad hour.
• Line counts: count people waiting, not people being served, at a fixed interval such as every two minutes. Thirty to sixty snapshots over a busy window is enough.
• Transactions: from the POS for the same hours. They also give you conversion by hour on the coverage tab.

Honest limits

• It cannot see lost sales. Shoppers who saw the line and left, or could not find help, never appear as transactions. That is why both tabs flag time above target rather than relying on averages. Rogelio Oliva's MIT Sloan research, as reported by Retail Dive, found one apparel chain reaching only 85% to 95% of its potential sales with its existing staffing.
• Steady periods only. Little's Law estimates are reliable over windows where the line or the store is about as busy at the end as at the start. Do not run the checkout tab across a whole day.
• Averages, not individuals. The wait figure is an average for the period, not the wait of any particular shopper.
• Manual counts take effort. A week of hourly floor counts in the busiest hours is realistic. Every hour of every day at every store is not, which is where a continuous record helps.

Also available

• The guides behind each tab: customer-to-staff ratio by hour and zone and how to measure checkout wait time.
• Why the usual productivity number misses this: is sales per labor hour a good KPI?
• Formulas, CSV templates and a small script for teams that prefer to work in code: the retail-ops-metrics repository on GitHub.

How Super Vision approaches this

The calculator works when someone has time to count. Super Vision turns the cameras a store already has into an operational record of what happened on the floor, so the same questions can be answered across more hours and more locations: when visitor traffic rose and service coverage did not, when checkout lines formed and how long they stayed above target, and staff presence at registers and service points where cameras cover the zone. Findings come with evidence attached.

It does not score individual associates, and it does not infer purchases from video: transaction and revenue metrics come from your POS. Start with one location and one question, such as whether Saturday peaks are covered.