Retail park footfall: reading busy car parks and big-box days
Retail park footfall behaves unlike a high street: long visits, weekend peaks and car-borne shoppers. How to measure it, compare parks and pair it with the roads.
Part of the guide Location intelligence automation
Retail park footfall measures how much presence there is across a park of large stores and its car park, in people-hours, and it behaves differently from a high street. Visits are long, most people arrive by car, weekends usually lead, and evenings fade early. To read it well, draw the circle wide enough to take in the car park and the units, compare parks with other parks rather than with town centres, and set it next to how the access roads move.
This is for tenants weighing a unit on an out-of-town park, landlords and asset managers comparing parks, and brands that sell into them: EV charging operators, food outlets and car services that want the waiting shopper. It covers how a park's figures behave, a worked example, mistakes to avoid and an AI employee that keeps the picture current.
How a park's figures behave
People spend a long time in furniture, DIY and home stores, and they come for a planned trip rather than passing by. Because Mobility Footfall counts hours of presence, a park with a few large destination stores can score as well as a busy street with many quick visits. Expect:
- A strong weekend, with Saturday or Sunday the busiest day in most countries (the block follows each place's own weekend).
- Midday and early afternoon peaks, with a weak late night share once stores close.
- Holidays and payday weekends that may stand out, since the trips are planned.
Parks next to a supermarket or a cinema break the pattern: a supermarket brings weekday evening trips and a cinema brings late visits. The shape of the day tells you which kind of park you are looking at.
Choosing the circle
Up to 200 m the block measures the one cell of the map the point sits in, about 0.1 km², which can miss half of a large park and its car park. For a whole park, use a wider radius, 300 to 500 m from its middle, and keep the same radius for every park you compare. To read one end of a long park, measure a second point there with 200 m.
A worked example in Lyon and Calgary (made up)
Say a mattress brand is choosing between units on two parks near Lyon and one near Calgary, all with similar rents. The figures below are made up to show the reading.
| Park | People-hours a day | Busiest day | Busiest hour | Speed on the access road, Sat 11:00 |
|---|---|---|---|---|
| Lyon, north park | 31,000 | Saturday | 15:00 | Moderate |
| Lyon, east park | 24,500 | Wednesday | 18:00 | Free flowing |
| Calgary, south park | 27,800 | Saturday | 14:00 | Heavy |
Made-up figures for illustration only.
The north Lyon park looks like a classic weekend home-goods destination, which suits mattresses: people come to compare and stay. The east park peaks midweek in the early evening, which suggests a supermarket draws it; it is busy, but with quick food trips. Calgary's park draws a weekend crowd too, but the access road is heavy at the Saturday peak; the brand checks whether that is a junction that clears or a daily queue that puts people off, by measuring it on several weekends before signing.
Mistakes to avoid
- Comparing a park with a high street. They draw different trips. Rank parks against parks.
- A circle that misses the car park. Much of the presence on a park is in and around the parking. Widen the circle.
- Reading people-hours as shoppers. One family staying two hours counts more than once. Footfall is presence, not visitors or sales.
- Expecting last weekend. Footfall arrives about 10 days after each day.
- Ignoring the roads. A park that is hard to reach at the peak loses trips over time. Live speeds on the access roads show it.
An AI employee for a portfolio of parks
A monthly flow keeps every park on one sheet with its footfall, its peak and the state of its roads. It is a natural part of the work on the AI employee for site selection.
- A Schedule on the first Saturday of the month, late morning, so the road readings catch the weekend peak.
- My data with your parks and their middle points.
- Mobility Footfall on each, 500 m, the last 30 days, with Footfall, Busy hours, Busiest days and Trend.
- Traffic Flow with Within 1 km, for the access roads at that moment.
- EV charging within 1 km, if charging is part of your plan or your offer.
- xMap LLM to describe each park's kind (weekend destination, food-led, mixed) and flag any fall in footfall.
- Email or Make a report for the asset or expansion team.
Each month the inbox holds every park with its footfall, its busiest day and hour, the trend, how the access roads were moving at the weekend peak and a one-line reading. For a park with many visitors and few chargers, see the template below on busy shopping places with the fewest EV chargers.
Questions
Why is footfall at a retail park high with few stores?
Because people stay a long time in large stores, and footfall counts hours of presence, not the number of people.
What radius should I use for a retail park?
Wide enough to cover the units and the car park, usually 300 to 500 m from the middle. Use the same radius for every park you compare.
Can I see how many cars arrive at a retail park?
Not from Traffic Flow, which gives live speeds and the jam factor. Car counts by hour exist only for roads in the United Arab Emirates, through Regional data.
Is the weekend always the busiest at a retail park?
Often, but not always. Parks anchored by a supermarket can peak on weekday evenings. The busiest day and hour show which kind each park is.