How to Find Your Store's Real Peak Hours with Footfall Data
Most store peak hours analysis starts with the sales report. That feels logical, but it answers the wrong question. A sales peak tells you when people bought. It does not tell you when the store was actually full of people who needed your attention.
Those are different things, and the gap between them is where service slips and staffing budgets get wasted. The hour you sold the most might not be the hour the most people walked in.
This guide shows how hourly and daily footfall data reveals your store's real peaks, including the browsers who never buy a thing. Then it shows how to turn that pattern into staffing, promotion, and operations decisions you can act on this week.
Key takeaways
- Sales reports show when you sold. Footfall data shows when you were actually busy.
- Browsers who never buy are invisible to your POS, but they are real demand on your team.
- Read an average week by hour, and separate weekday from weekend, to find consistent peaks instead of one-off spikes.
- Staff to the traffic peak, not only the sales peak, and move tasks like restocking into genuine lulls.
- Staff exclusion keeps the curve focused on shoppers rather than your own team walking the floor.
Why sales-based peaks mislead you
A sales peak is a record of completed transactions. It tells you the hour the most receipts printed. It says nothing about the hours when the store was packed but conversion was low.
Think about a Saturday afternoon. Plenty of people come in to browse, try things on, and compare prices. Many leave without buying. Your POS sees a quiet patch. Your team, standing in the middle of it, knows the floor was busy.
That browsing traffic is invisible to sales data, but it is real demand. Those visitors ask questions, need fitting rooms, and form the queue at the till. If you staff to the sales peak alone, you can be short-handed exactly when the floor is at its fullest.
The result is a familiar problem. You schedule cover for the hour money came in, the earlier rush of foot traffic goes under-served, and conversion drops because nobody was free to help. Sales-based scheduling can quietly reinforce the very gap it is trying to close.
What footfall data shows that sales cannot
Footfall counts the people, not the purchases. An entry count at the door records everyone who walked in, whether or not they bought. That single change in perspective uncovers the demand your POS never sees.
Hourly and daily entry counts reveal the true shape of demand across the week. You can see the morning build, the lunchtime surge, the afternoon plateau, and the evening fade for what they really are, by people rather than by sales.
You can also see the traffic that arrives and leaves without a transaction. That is not wasted data. It is a measure of interest, browsing pressure, and missed conversion, and it tells you where the work is even when the till stays quiet.
Occupancy adds a second layer. Entry counts tell you how many people came in. Real-time occupancy tells you how full the store is right now, which is what actually shapes the experience on the floor. A store with steady entries but long dwell can be more crowded than one with high entries and quick visits.
One practical note. Footfall is measured per entrance, then summed to a store total. If you have a main door and a side door, each is counted separately and added together, so the store-level curve reflects every way people get in. Want the wider context first? Our overview of footfall analytics walks through how these metrics fit together.
How to read your hourly and daily curve
The single most useful view is an average week by hour. Lay out each day across columns and each hour down the rows, then average several weeks together. Consistent peaks stand out. One-off spikes from a local event or a rainy afternoon blend back into the average where they belong.
Next, separate weekday and weekend patterns. They usually differ in both size and shape. A weekday might show a sharp lunchtime peak and a smaller after-work bump. A weekend might build slowly, hold a long midday plateau, and stay busy into the afternoon. Averaging them together hides both.
Watch for the power-hour effect. In most stores a small slice of the week holds a large share of the total traffic. For example, a handful of weekend midday hours might carry a quarter of the week's footfall. Those power hours are where staffing and promotions earn the most, so it is worth knowing exactly when they fall.
Finally, use enough data. A single week is mostly noise. Weather, paydays, school holidays, and local events all move the curve. Several weeks of footfall by hour smooth those out and let the genuine pattern show through.
Peaks for staffing decisions
The first move is to schedule cover for the traffic peak, not only the sales peak. If foot traffic crests at 2 pm but receipts crest at 4 pm, you likely need hands on the floor from early afternoon onward, not just at four. Staffing to people protects service during the build, which is often when conversion is won or lost.
Position staff where traffic concentrates during the rush. If entries surge through one door or visitors cluster in one zone, that is where you want experienced staff and open tills. Matching placement to the shape of the peak does more than adding headcount everywhere.
Plan low-value tasks for genuine lulls. Restocking, cleaning, price changes, and stock counts belong in the quiet windows your curve reveals, not during the rush. A clear hourly pattern turns "fit it in when you can" into a defensible schedule.
Then react on the day with real-time occupancy. The average week tells you what to plan for. Live occupancy tells you when today is running hot or cold, so a manager can pull someone onto a till or send them to break before a queue forms. For a deeper look at building rotas around this, see our guide on matching rotas to when customers actually arrive.
Peaks for promotions and operations
Timing is most of the value in a promotion. Run a demo, sampling, or limited offer when the most people are physically present, and it reaches the largest audience for the same effort. Your footfall curve tells you exactly which hour that is, and it is often not the hour you assumed.
Operations work the other way. Deliveries, maintenance, deep cleaning, and contractor visits should land in the low-traffic windows. Scheduling a delivery into a power hour blocks an aisle and an exit at the worst possible time. The curve makes those windows obvious.
Comparing peak shapes across days also surfaces opportunity. The table below shows an illustrative pattern for a single store.
| Day | Traffic peak | Share of weekly footfall | Notes |
|---|---|---|---|
| Tuesday | 12 pm to 1 pm | Low | Quiet midweek, room to drive traffic |
| Thursday | 5 pm to 7 pm | Medium | After-work build |
| Saturday | 12 pm to 3 pm | High | Power-hour block, long plateau |
| Sunday | 1 pm to 4 pm | Medium-high | Slower build, steady afternoon |
An underused slot like the Tuesday lunch dip is a candidate for a targeted promotion or a midweek event, because you are adding traffic where you have spare capacity rather than crowding an hour that is already full.
Setting this up with CountPort
CountPort gives you footfall by hour from the IP cameras you already have, with no new sensors at the door. It runs as pure software on a back-office PC, mini-PC, or Mac Mini, reading the camera over RTSP or ONVIF, and your video stays on-site. Detection is body-only, with no facial recognition.
Staff exclusion keeps the hourly curve focused on shoppers. Your own team walks the floor and passes the entrance throughout the day, so counting them as visitors would inflate your peaks. Excluding staff means the pattern you plan against reflects real customer demand.
From there you get scheduled reports and a live occupancy view. The reports turn the average-week analysis above into something that lands in an inbox every Monday, and the live view lets a manager react on the day. To build the recurring report, see our walkthrough on creating a weekly footfall report your team will actually use, and for busy trading periods, our guide to managing occupancy during seasonal peaks.
Accuracy depends on real-world factors, not a single headline number. Camera placement, mounting height, lighting, and how crowded the entrance gets all affect how cleanly people are counted. A well-placed overhead view at the door gives a cleaner count than a wide, angled camera meant for security.
Frequently asked questions
How do I find my store's peak hours?
Look at footfall counts by hour across several weeks and find the times that are consistently high, not one-off spikes. Separate weekday and weekend patterns, since they usually differ in both shape and size.
Why use footfall instead of sales to find peak hours?
Sales only show when people bought. Footfall shows everyone who came in, including browsers who never buy, so you can staff for true demand rather than just transactions.
What are power hours in retail?
Power hours are the busiest stretches of the week, when a large share of your total traffic arrives in a small number of hours. Identifying them helps you focus staffing and promotions where they matter most.
Can footfall data help with staff scheduling?
Yes. Once you know your traffic peaks by hour and day, you can schedule cover for the rush and move tasks like restocking into quieter windows. Staff exclusion keeps the count focused on shoppers, not your own team.
See your real peaks
The fastest way to know your true peak hours is to look at your own door. Request a demo and we will show you footfall by hour from your existing cameras, with staff excluded, so you can plan against real demand.
