Traffic Flow and Customer Flow: Zone Analytics Beyond the Door Count

Two stores with identical door counts can have completely different commercial realities. One pushes 70 percent of its visitors past the highest-margin category; the other loses half of them within eight metres of the entrance to a route that bypasses everything the merchandising team spent weeks planning. A door counter cannot tell you which store you are running. Traffic flow analysis can — and that is the difference between knowing how many people came in and knowing what they actually did once inside.

If you are still building the basics of people counting terminology, the pillar article What is Footfall covers the overview. This article goes deep on one thing only: how visitors move through and between zones, and why that visitor flow data changes decisions that entrance counts never could.

What zone analytics actually measures

Zone analytics works by placing sensors at zone transitions — the thresholds between entrances, departments, floors, corridors and defined areas. Each sensor registers anonymous movement crossing that boundary, in each direction. Stitch those transitions together and you get a directional map of customer flow: not a snapshot of where people stood, but a record of how they travelled.

This produces answers that door counting structurally cannot provide:

• Entrance weighting — which entrance carries the most traffic, and how that shifts by hour, weekday and season. Many multi-entrance sites discover their "main" entrance is only main on paper.
• Route patterns — the actual paths visitors take between zones, including the routes nobody designed for.
• Dead legs — corridors, corners and departments that traffic consistently avoids, regardless of what is placed there.
• Floor distribution — how footfall splits between floors, and where vertical circulation (escalators, lifts, stairs) leaks visitors.

A related metric worth knowing is capture rate: the share of passing traffic a zone or store actually pulls in. A unit on a corridor carrying 4,000 people a day with a low capture rate has a proposition problem. The same unit on a corridor carrying 400 people a day has a location problem. Without zone-level traffic flow data, these two problems look identical from the till.

Why zone traffic is hard currency for shopping centres

For centre operators, zone analytics is not a marketing tool — it is a financial one. Traffic per corridor and per lease unit feeds directly into rent negotiations, turnover clauses and leasing dialogues. When a tenant argues their unit underperforms because "the centre is quiet," corridor-level visitor flow data ends the debate with evidence: here is the traffic your frontage received, here is how it compares to the corridor average, here is the trend over twelve months.

The same data works in the other direction. Leasing teams can price units on demonstrated traffic rather than floor-plan intuition, and prospective tenants — particularly international brands with sophisticated site-selection models — increasingly expect it. A centre that can show verified zone traffic for a vacant unit negotiates from a stronger position than one offering only a total entrance count and a promise.

Data quality matters here more than anywhere else, because numbers used in commercial negotiations get challenged. Vemco Group commits contractually to a minimum of 96 percent counting accuracy, and in practice typically achieves 98–99 percent where conditions — lighting, layout, visitor behaviour — allow. When a turnover clause hinges on the figures, that contractual floor is the difference between data a tenant's lawyers accept and data they pick apart.

What zone analytics reveals inside a store

For retail managers and store designers, the sharpest use of customer flow data is testing whether the store works the way it was designed to work. Campaign areas are the classic example. A promotional bay can look busy on a Saturday walkthrough and still receive a fraction of store traffic across the week. Zone analytics answers the question directly: what share of visitors actually entered the campaign zone, and did that share move when you relocated it?

The same logic applies to layout changes. Move a gondola, open up a sightline, reposition a category — and the movement pattern shifts, sometimes in directions nobody predicted. With zone-level traffic flow measured before and after, layout becomes something you test rather than something you argue about in meetings. Designers get evidence for decisions that were previously defended with experience and instinct alone.

One observation from implementations that rarely makes it into vendor brochures: the first month of zone data almost always contradicts at least one belief the team held with total confidence. A "high-traffic" back wall that staff swore customers visited turns out to see 12 percent of visitors. An entrance dismissed as secondary carries the morning trade. Expect this, and treat the first review meeting as a myth-audit rather than a performance review — teams that do so adopt the data faster, because they stop defending the old map and start using the new one.

Getting the zone definitions right

The value of zone analytics is decided before a single sensor goes live, in how the zones are drawn. Practical guidance from projects that worked:

• Draw zones around decisions, not architecture. If nobody will act differently based on the split between two adjacent zones, merge them.
• Instrument every transition into a zone, not just the obvious one. A department with three entry points measured at one gives you a misleadingly low number and a false dead leg.
• Keep zone definitions stable through layout tests. Change the layout, not the measurement, or your before-and-after comparison collapses.
• Separate transit from engagement corridors. A route to the toilets or car park will always carry traffic; treating it like a shopping corridor inflates expectations for adjacent units.

On privacy: all of this is anonymous movement data. Zone analytics counts and directions crossings — it does not identify individuals, which keeps the approach GDPR-friendly and avoids the consent complexity that camera-based identification schemes drag into every deployment. For UK and EU operators, that distinction shortens legal review from months to days.

One platform, and what comes next

The practical case for unifying people counting, traffic flow, customer flow and zone analytics in one platform — as Vemco does — is consistency. When entrance counts and zone transitions come from the same system, the numbers reconcile. When they come from two vendors, the first hour of every review meeting is spent explaining why the totals disagree.

Zone data is also the foundation for the next layer of analysis. Once you know how visitors flow between zones, dwell time tells you how long they stay in each one, and heatmaps make those patterns visible at a glance. Both build directly on the zone structure described here — but neither is meaningful without solid traffic flow data underneath.

If you are pricing lease units on intuition, or redesigning layouts without measuring how movement patterns respond, zone analytics is the missing evidence layer. Talk to Vemco Group about mapping traffic flow and zone analytics across your site — from entrance weighting to corridor-level leasing data, with contractually guaranteed counting accuracy behind every number.