FlowsBook a callSign inCreate free accountSign up
Footfall and mobility

Footfall analytics for retail: busiest hours, best days, trends and store against store

Four readings that turn footfall analytics into retail decisions: the busiest hour, the best day, the trend, and each store ranked against the network.

Part of the guide Location intelligence automation

By the xMap team · · 5 min read

Footfall analytics for retail comes down to four readings for each store: when the area around it is busiest in the day, which day of the week is strongest, whether the area is getting busier or quieter, and how its level compares with the rest of the network. Put next to your own sales, those four readings show which stores sit in a good spot but underperform, which ones do well in a quiet spot, and where hours or staff do not match the street.

This is for retail operations, network planning and regional managers with ten or more stores. It goes through the four readings, a simple matrix that combines footfall with sales, a made-up example from a cosmetics chain in Paris, the traps, and a monthly AI employee that keeps the numbers fresh. Where the figures come from is explained under foot traffic data.

Reading one: the busiest hour against your opening hours

The busiest hour and the way the day splits (morning, midday, evening, late night) show when the street around a store is full. Lay them over the store's opening hours. A store that closes at 19:00 on a street whose busiest hour is 19:00 is shutting the door on its best hour. A store that opens at 08:00 where mornings are a fifth of the day may be paying staff to wait.

Reading two: the best and worst day

Each store's busiest and quietest day, counted in its own local week, tells you where weekend trade carries the store and where weekdays do. Shopping streets near offices often peak midweek and fall away on Sunday; streets near homes and parks often do the opposite. The difference decides when to run promotions, deliveries and stock counts.

Reading three: the trend

The last seven days against the seven before shows whether the area is picking up or slowing. On its own, one week's move means little: a holiday, a match or rain can swing it. Watch it over several months, and act when a store's area keeps falling while the rest of the network holds steady. That pattern points to something local: roadworks, a rival opening, an office closing.

Reading four: store against store

Rank every store by footfall per day around it, measured over the same days and the same distance. Then give each store an index: its footfall divided by the network's middle store, times 100. A store at 140 sits in an area 40% busier than the typical store; one at 70 sits in a quiet one. The index is easier to read in a meeting than raw people-hours, and it stays comparable as the months change.

The matrix: footfall next to sales

Footfall is not sales, but the two together are revealing. Put each store in one of four boxes by its footfall index and its sales against target.

Sales above targetSales below target
Busy area (index over 100)Keep: good spot, well runLook inside: the street is there, the store is not converting it
Quiet area (index under 100)Learn from it: a loyal or destination storeQuestion the site: few people and few sales

A way to combine your own sales with footfall; the boxes are a starting point, not a verdict.

The box that pays back fastest is usually the busy area with weak sales: the people are already outside, so the fix is in the store (window, hours, staff, range), not in the location.

An example from Paris, made up for illustration

Say a cosmetics chain has six stores in Paris and runs the four readings over the same 14 days, within 200 metres of each store.

StoreFootfall indexBusiest hourBusiest dayTrendSales vs target
Rue de Rivoli15017:00Saturday+3%Above
Saint-Lazare13518:00Thursday+1%Below
Bastille10519:00Saturday-2%Above
Montparnasse10013:00Wednesday-6%Below
Batignolles8011:00Sunday+2%Above
Nation7012:00Saturday-1%Below

Made-up figures for illustration only.

Saint-Lazare sits in the second busiest area yet misses its target, and its street peaks at 18:00 on a Thursday: commuters on the way home. The chain extends its weekday closing to 20:00 there. Montparnasse has an average area that fell 6% in a week; the regional manager checks and finds roadworks blocking the main crossing, which explains it and passes. Batignolles beats its target in a quiet area on Sundays, so the chain studies what it does differently. Nation goes on the list for a closer look at the lease.

Traps in footfall analytics

  • Mixed windows or distances. A ranking only holds if every store uses the same days and the same radius.
  • Reading people-hours as shoppers. The figures count presence around the store, and long stays count more. A store by a hospital and one by a bus station can share a figure for different reasons.
  • Reacting to one week. Act on trends that hold for a month or more, after ruling out holidays, events and weather.
  • Forgetting the delay. Each day arrives about ten days later, so the newest figures describe the week before last.
  • Expecting Australian stores. Footfall covers most of the world from 17 October 2026, not Australia yet.

A monthly AI employee for the network

In xMap Flows the four readings come from one flow that runs at the start of each month and writes into the sheet your team already uses. It is a typical job for location intelligence automation.

  1. Add a Schedule for the first Monday of the month and bring in your stores with My data.
  2. Add Mobility Footfall at 200 m, the last 14 or 30 days, with Footfall, Busy hours, Busiest days and Trend ticked.
  3. Add a Calculated field for the index, or let Data analyst work out each store's index against the middle store and the ranking.
  4. Add Sort and limit on footfall per day, highest first.
  5. Write the rows to a sheet in Google Sheets next to your sales, and email the regional managers a short summary from xMap LLM.

What lands each month is one row per store with its footfall per day, busiest hour, split of the day, busiest and quietest day, trend and index, plus a few lines on the stores that moved most. Your team adds the sales column and fills the matrix. To see who lives around each store as well, the template Who lives around new places shows how Demographics fits in, and Competitor density around each site adds the rivals.

Questions

What is the most useful footfall reading for a retailer?

The busiest hour laid over each store's opening hours, because it leads straight to a change: open later, close later, or move staff to the right hours.

How do I compare stores in different cities?

Use the same days and distance for every store and index each one against the network's middle store. Then read the busiest hour and day in each city's own local time.

Can footfall predict a store's sales?

Not on its own. It shows how many people are around the store; your window, range, price and staff decide how many buy. Use the two together.

How often should the analysis run?

Monthly suits ranking and the matrix. Weekly is useful only for watching a store whose trend has started to fall.

Templates that do this

Read next

More on footfall and mobility · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.