Supermarket catchment population: counting residents within a walk or a drive
How many people live close enough to shop at a supermarket depends on its format. How to set the walk or drive, count the residents and the rival stores, and read the ratio.
Part of the guide Location intelligence automation
A supermarket catchment population is the number of people who live close enough to make that store their usual grocery shop. For a small neighbourhood store it is the residents within a walk of five to ten minutes; for a large store with a car park, the residents within a short drive. Draw that area along the real streets, count the residents inside it, count the other supermarkets inside the same area, and divide one by the other. The result, people per supermarket, is the number that lets you compare one site with another.
This article is for grocery retailers, franchisees, property teams leasing to grocers and investors looking at a store. It covers matching the area to the store format, the run that produces the counts, a worked example, and the traps that make a catchment look better than it is.
Match the area to the format
| Format | How people arrive | A sensible area |
|---|---|---|
| Convenience or express store | On foot, small baskets, often daily | 5 minute walk |
| Neighbourhood supermarket | On foot or a short drive, a few times a week | 10 minute walk or 5 minute drive |
| Large supermarket with parking | Mostly by car, a weekly shop | 10 to 15 minute drive |
| Discount store | By car and on foot, willing to travel for price | 15 minute drive |
Starting points, to be adjusted to local habits: car use, density and public transport vary a lot between cities.
Travel area draws each area along the roads, by car, on foot or by bike, for a travel time or a distance by road. On the current plan it reaches up to 15 minutes or 10 km. Times are for usual traffic, not the traffic at the moment of the run.
The run, step by step
- Put the store or candidate sites in My data, or pick them on the map inside the Travel area block.
- Travel area: the format's walk or drive, one area per site, up to 25 sites a run.
- Demographics, looking in the Area of interest with Totals for each area: residents, age groups and people per km² for each site's catchment.
- Nearby places, also looking in the Area of interest, for supermarkets and grocery stores, passing on the stores found, each labelled with the area it falls in.
- Calculated field or xMap LLM to put residents and rival stores side by side, and an email to the team.
A worked example
To know what a market looks like, start with a real count. xMap's places database lists 82 supermarkets within 10 km of the centre of Toronto (November 2026); of those 82, 34% belong to a chain and 66% are independent. Inside that wide circle, though, the stores are not spread evenly, which is why the catchment of each site matters more than the city total.
Now a made-up comparison. Say a grocer is choosing between two sites in the city for a neighbourhood supermarket, and both have a 10 minute walk drawn around them. Site one has, say, 14,000 residents in its walk area and two other supermarkets: about 4,700 people per store, counting the new one. Site two has 22,000 residents and five other stores: about 3,700 per store. Site two has more people, but site one has more people for each store, and fewer rivals to win them from. That ratio is the one to put in front of the committee.
Traps that flatter a catchment
- Circles instead of streets. A river or a motorway inside a circle adds people who cannot reach the store easily. Use the travel area.
- Ignoring the rivals' pull. A large store just outside your walk area still draws your residents for their weekly shop.
- Workers and visitors. Residents are only part of the demand. Stores by offices or stations sell to people who live elsewhere; residents set the floor, not the ceiling.
- Estimates read as real. When the routing service cannot draw an area, the block uses a circle at a typical speed and says it is an estimate. Flag those sites.
- Countries without population data. The grid covers about 100 countries, among them Canada, France, India, Thailand, Egypt and Australia, but not the United Kingdom or the United States.
Who lives there, not just how many
Two catchments of equal size can buy very differently. Demographics gives the nine age groups for each area, so you can see whether a site's residents lean towards young families (bigger baskets, more nappies and snacks) or towards older people (smaller, more frequent shops). It does not give income, so pair the count with what is already around: a street of discount stores and one of delicatessens say different things about the same number of residents.
Run monthly on a Schedule, the same flow notices new grocers opening inside each catchment with Only new. It is a small piece of location intelligence automation that keeps a site decision honest after the store opens.
Questions
Is a radius good enough for a supermarket catchment?
For a quick comparison of many sites, yes. For a decision on one site, use a walk or drive along the streets, since barriers like rivers and rail lines change who can reach it.
What is a good number of people per supermarket?
There is no single number: it depends on store size, format and local habits. Compare candidate sites with each other and with your best existing stores, measured the same way.
Can I include people who work near the store?
Residents are what Demographics counts. Mobility Footfall can show how busy the area around a site is during the day, as people-hours of presence, in most countries outside Australia.
How far can a travel area reach?
On the current plan, up to 15 minutes or 10 km by road, by car, on foot or by bike.
Templates that do this
Read next
More on population and demographics · Every article · Templates