Your Monday Morning Retail Data: The Numbers a Store Manager Checks First

It is 8:40 on a Monday. The weekly report landed in your inbox at 06:00, it runs to eleven pages, and the first thing you see is that sales were down 4 percent against the same week last year. Your area manager will ring at 10:00 and ask why. The honest answer is that the report tells you sales fell but not whether fewer people came in, whether the people who came in bought less often, or whether they bought less each time. Those are three completely different problems with three completely different fixes, and an eleven-page report that does not separate them is not helping you.

This article is about the order in which to read your retail data so that by 10:00 you have an answer, not a shrug. Five numbers, read in sequence, each one narrowing down where the problem actually sits.

Number one: footfall, before you look at sales

Most managers open the sales line first. That is backwards. Sales is the outcome; footfall is the first cause. If 4 percent fewer people walked through the door, a 4 percent sales drop is not a store performance problem at all. It is a traffic problem, and traffic is usually driven by things outside your four walls: weather, a competitor's promotion, roadworks, a school holiday that shifted a week, or in a mall, a change in the centre's own footfall.

So the first check is simple. Visitors this week versus last week, and versus the same week last year. Then, if you are in a mall, the second check is capture rate: your visitors divided by the mall's visitors passing your frontage. If mall traffic fell 6 percent and yours fell 4 percent, you actually gained share. That is a sentence worth having ready for the 10:00 call.

One practical note on trusting the number. Counting sensors are not perfect. A contractual minimum of 96 percent accuracy is the standard Vemco works to, and in practice 98 to 99 percent is typical when lighting, entrance layout and visitor behaviour allow it. Wide entrances where people walk in pairs, glass doors that reflect sunlight in the afternoon, and staff using the customer door all nudge the number. The point is not that the count is off; it is that a week-on-week comparison is far more reliable than the absolute figure, because the same conditions apply to both weeks.

Number two: conversion rate, the store's own report card

Conversion is transactions divided by visitors. If footfall held steady but conversion dropped from 22 percent to 19 percent, now you have a problem that is genuinely yours. Something happened inside the store. The usual suspects, in rough order of how often they turn out to be the cause:

• Staffing did not match the busy hours (see number four).
• A key size or line was out of stock for several days.
• A new window or promotion pulled in browsers who were never going to buy.
• Till queues at peak times sent people out empty-handed.

This is the single most useful retail data insight a store manager has, because it separates "nobody came" from "they came and we lost them". Vemcount produces it by joining the footfall count to your POS transaction feed, so the number is the same in your report and your area manager's report. That alignment matters more than it sounds: half of the Monday argument in many chains is two people quoting different conversion figures from different spreadsheets.

Number three: average transaction value and sales per visitor

If footfall is flat and conversion is flat but sales are still down, the remaining explanation is that each basket was smaller. Average transaction value comes straight from the POS and needs no sensor at all. A drop here usually points to mix (more low-ticket items, fewer add-ons) or to discounting that was deeper than planned.

Sales per visitor is the number that ties the first three together: it is conversion multiplied by average transaction value. It is also the fairest way to compare two stores of different sizes, or your store this year against last year when traffic has changed. If an area manager is going to rank stores on one metric, this is the one to ask for, because it rewards the store that does the most with the people it actually gets.

Number four: peak hours against staffing, where the budget decision lives

This is the number that turns retail data analytics into a decision you can act on by Tuesday. Lay your hourly footfall for the week over your hourly rota. In almost every store the first time this is done, the two curves do not match. Common pattern: full staff from 09:00, when the store is quiet, and the thinnest cover between 12:00 and 14:00 and again at 17:00, when the counter shows the heaviest traffic.

Here is the practitioner observation that saves people a lot of wasted effort. Do not look at weekly peak hours. Look at them by day. Saturday's peak and Wednesday's peak are often three hours apart, and a rota built on the weekly average will be wrong on both days. Build the rota from daily curves and check conversion by hour afterwards; if conversion at 13:00 rises after you moved a shift, the change paid for itself. If it did not move, the problem was never staffing and you can put the hours back.

Number five: dwell time, only if you have it

Not every store measures dwell time, and it is the one number on this list you can skip on a Monday if you do not. Where it exists, it is a useful tie-breaker. Dwell time up and conversion down usually means people are searching for something and not finding it, or waiting to be served. Dwell time down and conversion down usually means they walked in, saw nothing of interest, and left. Same sales result, opposite remedies.

The ten-minute Monday routine, in order

• Footfall versus last week and last year. In a mall, capture rate too.
• Conversion rate. If it moved, look at stock and rota before anything else.
• Average transaction value and sales per visitor.
• Hourly footfall against the rota, by day, not by week.
• Dwell time, if available, as a tie-breaker.

Read in that order, the data tells a story: fewer people, or the same people buying less often, or the same people buying less each. Everything else in the eleven pages is supporting detail. For area managers, the same sequence works across a region, and for mall operators VemTenant applies it to tenant sales so the centre and the store are reading from the same retail business intelligence rather than arguing about whose footfall figure is right.

Frequently asked questions

What retail data should a store manager look at every week? Footfall, conversion rate, average transaction value, sales per visitor and hourly traffic against the rota. Capture rate as well if the store is in a mall. Those five or six numbers explain almost every sales movement; the rest of the report is context.

What is the difference between retail data and retail insights? Data is the raw figure: 3,120 visitors on Saturday. An insight is the figure placed next to something else so it tells you what to do: 3,120 visitors but only two staff between 13:00 and 15:00, when 40 percent of them arrived. Actionable retail insights always involve a comparison.

How do you turn footfall data into decisions? Combine it with transactions to get conversion, then split both by hour and by day. The gaps between when people arrive and when staff are on the floor are the decisions. Change one shift, check conversion in that hour the following week, and keep or reverse the change based on the result.

Which retail data comes from the POS and which from sensors? The POS gives you transactions, revenue and average transaction value. Sensors give you visitors, hourly traffic, dwell time and, in malls, the passing traffic needed for capture rate. Conversion and sales per visitor need both, which is why a platform like Vemcount joins the two feeds.

How often should retail data be reviewed? Weekly for the five numbers above, because that is the cadence on which rotas and stock orders change. Daily glances at footfall and conversion are useful in peak season. Monthly and yearly comparisons are for area managers spotting trends across stores, not for running a single store.

If your Monday report still shows sales without the footfall and conversion next to it, that is fixable. Talk to Vemco Group at vemcogroup.com/contact-us about joining your counting data to your POS so the five numbers above arrive in one view, ready before the 10:00 call.