How many people live near a store, and how to draw its catchment
A store's catchment is the area its customers come from. How to count the people inside it, choose between a circle and a travel time, and compare stores fairly.
Part of the guide Location intelligence automation
To know how many people live near a store, first decide its catchment: the area most of its customers come from, best drawn as a travel time on foot or by car rather than a plain circle. Then add up the residents inside it, split by age if your products depend on it. The count is a ceiling on who could shop there, not a forecast of who will, and it is most useful when every store is measured the same way so they can be compared.
This is for retail operations and expansion teams, franchise owners and analysts who need a fair number for each store, whether to judge one site or rank a whole network. It covers how to draw the catchment, how to count the people, a made-up worked example in Paris and the mistakes that make two stores look alike when they are not.
What a catchment is
A catchment is where a store's customers live or spend their day. A convenience store draws from a few streets; a furniture store from a whole region. Three ways to draw one, from rough to realistic:
| Method | How it works | When it is good enough |
|---|---|---|
| A circle | Everything within, say, 1 km in a straight line | Dense, evenly built centres with no rivers or railways in the way |
| A travel time | Everything reachable in so many minutes on foot, by bike or by car, along real roads | Almost always the better choice; essential where roads bend or barriers cut the town |
| Your own customers | Drawn around the home addresses of actual buyers, from loyalty cards or deliveries | The truest, when you have the data, and the way to check the other two |
Three ways to draw a store's catchment.
Travel area draws the second kind: the area within a travel time or a distance by road, by car, on foot or by bike. Today it goes up to 15 minutes or 10 km. A 15-minute walk reaches about a kilometre in a town; a 15-minute drive several.
Counting the people inside
Demographics reads xMap's population grid, small hexagons of about 0.1 km², and adds up the residents of any area: total, men and women, nine age groups, and the share of children and of people over 60. Put it after Travel area and it counts inside each store's catchment; put it after your stores with a distance and it counts within that circle.
A made-up example: three stores in Paris
The figures below are invented to show the method. Say a chain of organic grocers has three Paris stores of the same size, and the one in the east sells far less. Measured with a 1 km circle, all three have similar populations. Measured with a 10-minute walk, the picture changes:
| Store | People within 1 km | People within a 10-minute walk | Share over 60 |
|---|---|---|---|
| West | 38,000 | 29,000 | 26% |
| Centre | 41,000 | 33,000 | 19% |
| East | 39,000 | 17,000 | 17% |
Made-up figures for illustration only.
The eastern store sits beside a railway and a wide boulevard, so half its circle is hard to reach on foot. Its real catchment is about half the others'. The chain stops blaming the manager and starts asking whether delivery from that store could reach the homes on the other side of the tracks.
Mistakes to avoid
- Comparing stores with different catchments. A drive-to store and a walk-in store should not be ranked on the same 1 km circle. Measure each by how its own customers arrive.
- Treating residents as customers. The count is everyone. Your share of them depends on the rivals inside the same area, which is the next thing to count.
- Forgetting overlap. Two of your stores 800 m apart share much of their catchment. Add their populations and you count the same households twice.
- Reading one year as forever. New housing fills a catchment in a few years. Measure again when a big development opens nearby.
Doing it with an AI employee
For a network, measure every store at once and repeat it monthly, so a new store or a new rival changes the picture without anyone rebuilding the sheet. Blocks in order:
- Schedule: the first of each month.
- My data: your stores, uploaded once with their addresses.
- Travel area: a 10-minute walk, or a 15-minute drive, around each store.
- Demographics: the residents in each area, with age groups.
- Nearby places: rival stores of your kind inside each area, counted.
- Calculated field: people per rival store, a simple measure of how much room there is.
- Sort and limit, then Email: the network ranked, to operations.
What lands each month is one table: every store with the people in its catchment, its rivals and people per rival, ranked. To start from a ready flow, try Rivals within 10 minutes' drive of each store or Who lives around new places.
Questions
What radius should I use for a store's catchment?
Use travel time rather than a radius where you can: a 5 to 10 minute walk for convenience stores, a 10 to 15 minute drive for larger stores. If you must use a circle, pick the same one for every store you compare.
Does the population count include people who work nearby?
No. It counts residents. Workers and visitors show up in footfall, which measures how busy an area is in people-hours.
Why is there no population figure for my store in London?
xMap's population grid does not cover the United Kingdom or the United States. Use your own customer addresses there.
How often should catchment population be recounted?
Yearly is enough for most stores; monthly if you are adding stores or tracking new rivals inside each catchment.
Templates that do this
Read next
More on population and demographics · Every article · Templates