Using traffic data for store hours at drive-to branches
For stores most customers drive to, the roads decide when they can come. How to collect a few weeks of live speeds around each branch and read them for opening times.
Part of the guide Location intelligence automation
Traffic data for store hours is most useful at branches people drive to: DIY and hardware stores, garden centres, furniture and appliance showrooms, out-of-town supermarkets and car-dependent suburban shops. For these, the question is not only when people want to shop but when the roads around the store are free enough to make the trip worth it. Collect live road speeds around each branch every 30 minutes for a few weeks, and the pattern shows the hours when access is easy, the hours when the junction outside jams, and whether an earlier opening or a later close would meet drivers when the roads are clear.
This article is for retail operations and regional managers who set or review opening hours across a network, and for owners of a single destination store. It covers what to measure, how to collect a pattern from live readings, how to read it with your own sales data, a made-up example near Johannesburg, and how an AI employee gathers the readings while you get on with the job.
Why roads matter more for some stores than others
A city-centre shop lives on people walking past, so footfall tells you more about its hours. A destination store lives on people deciding to drive there. If the road outside crawls from 4:30 pm to 6:30 pm, some of those customers simply put off the trip. If the ring road is clear at 7:30 am, the trade customers of a hardware store may come before work if you are open.
- Trade counters serve builders and plumbers who want to be in and out before their first job.
- Weekend destination stores see access patterns shaped by leisure traffic, sports and markets nearby.
- Retail parks share one access road between several big stores, so the jam outside may have nothing to do with you.
What to measure
Traffic Flow measures the roads around each point when the flow runs: current speed, free-flow speed, jam factor from 0 to 10, congestion as a percentage, a level in words, roads measured, roads closed, and the busiest road. For a store, two points usually cover it: the car park entrance, with Roads set to the adjacent roads, and the main junction customers turn at, set to 500 m.
It does not count cars and keeps no history. The pattern comes from running it on a schedule and keeping every reading, which is easy to automate.
Collecting a pattern
- List your branches in My data, with one row per point to measure.
- Set a Schedule every 30 minutes, with active hours from an hour before your earliest possible opening to an hour after your latest close.
- Run Traffic Flow on each point.
- Add a row to a spreadsheet in Google Sheets every run: branch, point, weekday, time, speed, jam factor, level.
- After three or four weeks, look at the average jam factor by weekday and half hour for each branch.
The Data analyst block can answer questions over the collected rows, such as "which half hours on weekdays have an average jam factor under 2 at each branch?", and give the answer as a table and a chart.
Reading it with your own data
Road readings alone do not set hours. Put them next to what you already know: sales by hour, staff costs by hour, and, if useful, footfall. Mobility Footfall gives how busy the area around a store is by hour and day, in people-hours of presence rather than visitors, each day arriving about 10 days late and with history only from mid-October 2026.
| If the readings show... | ...consider |
|---|---|
| Roads clear before your opening, with trade customers in the area | Opening earlier on weekdays for a trade counter |
| A jam outside every evening from 5 pm | Whether staying open later catches drivers after it clears |
| Saturday access easy all day, Sunday jammed at midday | Moving staff hours, not just opening hours |
| The jam is on a retail park road shared with others | Talking to the landlord about access, not changing hours |
Ways to read the pattern. Test any change for several weeks before deciding.
A made-up example near Johannesburg
Say a hardware chain has a branch in the northern suburbs of Johannesburg and opens at 8 am. This example is invented. Four weeks of readings show the junction outside at Light or Free flowing from 6:30 to 7:15 every weekday, then Heavy until about 8:30. The store's trade counter sales already peak in its first open hour. The chain tries opening the trade counter only at 7 am, with two staff, for six weeks, and compares sales and wage cost before making it permanent.
Mistakes to avoid
- Deciding from one week. School holidays, public holidays and roadworks change the pattern.
- Measuring only the car park entrance. The junction a kilometre away can be the real barrier.
- Using road data for a walk-in high street shop, where footfall and the people around it matter more.
- Changing all branches at once instead of testing a few.
The AI employee that does the collecting
The flow above runs on its own once deployed: Schedule, My data, Traffic Flow, and a Google Sheets row. Add Traffic incidents so a week with roadworks outside is marked and left out of the averages. Start from Road speeds outside my depots, every hour and swap the depots for your branches. For more on how live road data feeds business decisions, see location intelligence automation.
Questions
Can traffic data tell me the best opening hours?
Not on its own. It shows when the roads around a store are easy to drive, which you then weigh against your sales, staff costs and customers' habits.
How long should I collect readings for?
Three or four weeks gives a usable pattern by weekday. Avoid holiday weeks or mark them separately.
Does it count the cars passing my store?
No. It gives live speeds and a jam factor. Car counts by hour exist only for roads in the United Arab Emirates, in Regional data.
Should a city-centre shop use this?
Usually not as the main measure. For shops people walk to, footfall around the store says more about the busy hours.