Footfall vs. sales: why traffic and revenue tell different stories
Busy doors and full tills are not the same thing. The gap between them is where most retail decisions go wrong.
A retailer in a mid-sized Swedish city reported record footfall one November. Visitors were up, dwell time was up, and the marketing team felt vindicated. Then the P&L arrived. Revenue was flat. The problem turned out to be straightforward once someone looked: most of those extra visitors were there for an in-store event that involved no browsing and no purchasing. The footfall was real. The sales weren’t. And nobody had been watching the gap between them.
The metric nobody argues about, until it contradicts the other one
Footfall and revenue are the two figures every retailer tracks. They rarely disagree until one moves without the other, then the argument gets loud. Management points at traffic as proof the location is healthy. Finance points at the revenue line as proof something is wrong. Both are right, and both are missing the number that connects them: in-store conversion rate.
Conversion rate is transactions divided by visitors, expressed as a percentage.
According to TruRating’s retail conversion analysis, in-store conversion varies sharply by format: roughly 10–20% for big-box, 15–30% for specialty retail, and 20–40% for grocery. A single “average” is misleading, a grocery store and a luxury watch boutique have almost nothing in common on this metric, which is why your own rolling baseline matters more than any published benchmark.
What conversion rate gives you is a clean answer to the question footfall and revenue cannot answer separately: of all the people who came in, how many actually bought?
When footfall goes up and revenue doesn’t
Traffic growth without revenue growth is the more common surprise. It shows up in several recognisable patterns. A promotional campaign brings in new visitors who are curious but uncommitted; conversion drops because the new arrivals behave differently from the regular customer base. A busy shopping-centre location picks up footfall from a popular anchor tenant but captures few of those customers for itself. Seasonal weather sends people indoors who had no intention of shopping at all.
In every case, the raw footfall number looked encouraging. The conversion number, if anyone had been watching it, would have told the true story earlier.
When revenue goes up and footfall doesn’t
The reverse is equally instructive and often more welcome. A store trims its window display, reorganises the floor around a smaller number of key categories, and trains staff more tightly. Footfall is unchanged, the same number of people walk past and decide to come in. But the percentage who buy rises, average basket size rises, and revenue grows without the marketing spend needed to pull in more visitors.
This is the case for treating conversion as a lever in its own right.
The market for more footfall is expensive and competitive; the market for converting the visitors you already have is mostly just measurement and execution.
What the data shows that instinct doesn’t
Store managers feel when a period is busy or slow, and they are often right.
They are almost never right about why.
Was last Tuesday slow because fewer people came in, or because the people who came in left faster and bought less? From behind the counter, both cases look identical. The responses are completely different, more marketing in the first, more merchandising or staff attention in the second.
This is why the data deliverables from a properly instrumented store include both the visitor count and the timestamps that let you match it against your POS export. That visitor count can come straight from the building’s existing Wi-Fi, with no cameras. Without both, you are diagnosing the business with half the information.
Conversion by day, hour, and zone
Once you have both numbers running in parallel, the questions get more precise. Conversion on Saturday afternoons may be fifteen points higher than conversion on Tuesday mornings, and the interesting question is not just that it is higher but whether you are staffed for it. Staff planning built on footfall patterns means putting more resource on the floor when more buyers are actually in the building, rather than defaulting to fixed rotas that flatten out the peaks.
Zone-level data adds another layer. A high-footfall area of the store that produces few transactions is often poorly merchandised or awkwardly lit, not simply unvisited. An area with lower traffic that converts well might reward expansion. The combination of movement data and sales data is what makes the difference visible.
The chain problem
For a single store, the conversation is relatively contained. For a retail chain operating dozens of sites, the stakes are higher and the comparisons more powerful. A chain that can rank its locations by both traffic and conversion simultaneously can quickly identify which sites are underperforming on one metric while excelling on the other, and that distinction changes what you do about it. That ranking only holds up if every site was counted the same way, which is what a footfall benchmark is actually worth.
A location with high footfall and low conversion is a different operational problem from one with low footfall and high conversion. The first needs something done about the product offer, the layout, or the staff; the second needs marketing or signage to pull in more of the passing trade it is clearly capable of converting once it has it. Without both numbers, both look the same: underperforming.
Joining counts to tills via API
The practical bottleneck is usually integration. Footfall data and POS data sit in different systems, with different time granularities and different owners. The solution is an analytics platform with API connectivity that normalises both streams onto a shared time axis, making conversion rate a live operational metric rather than something someone calculates in a spreadsheet once a month.
When conversion drops on a Thursday afternoon for no obvious external reason, someone knows today, not at the next trading review. That is the difference between footfall data as a reporting tool and footfall data as a management tool, and it is what turns the gap between traffic and revenue from something you occasionally notice into something you actively close. For flagship stores and chains alike, the GDPR-compliant footfall analytics that underpins all of this runs without identifying a single customer by name.
- 10–40%
- In-store conversion rate (varies by format)
- 20%
- Conversion when 160 of 800 buy
Frequently asked questions
What is the difference between footfall and sales?
Footfall counts how many people enter a space; sales counts how many transactions occur. A store can be full of people and still record falling revenue if those visitors are browsing, sheltering from rain, or simply failing to find what they want. The two metrics only converge when conversion, the ratio of buyers to visitors, is also tracked.
How do you calculate in-store conversion rate?
Divide the number of completed transactions by the number of visitors in the same period, then multiply by 100 to get a percentage. If 800 people walk in and 160 buy something, conversion is 20 per cent. What counts as a healthy rate varies considerably by format, from roughly 10–20% for big-box to 20–40% for grocery, so the meaningful comparison is against your own baseline rather than a single benchmark.
Can footfall rise while revenue falls?
Yes, and it happens more often than retailers expect. Heavy promotional periods draw browsers who rarely buy. Sale events pull in bargain-seekers with small basket sizes. A new competitor nearby increases passing trade but captures the buyers. Footfall is opportunity; conversion and average transaction value together determine whether that opportunity turns into revenue.
Why do I need both footfall data and POS data?
POS data tells you what sold and when. Footfall data tells you who was there when, and how many of them bought nothing. Together, they tell you whether a quiet Tuesday was quiet because no one came in, or because the people who came in left empty-handed, two very different problems requiring very different responses.