Time and data freshness
Reference
Store time
Section titled “Store time”Every store has a time zone, set on the store form. Store data is always calculated in that zone:
- Today runs from midnight to now at the store.
- 7 Days and 30 Days are whole calendar days ending today at the store, not a rolling number of hours.
- Operating hours, open/closed status, peak hours and chart buckets are all in store time.
- Daylight-saving changes are handled; a 23- or 25-hour day is still one day.
If you are in a different time zone from the store, the chart’s hours are the store’s hours, not yours.
Your time
Section titled “Your time”A few places use your browser’s time zone and say so on the page: the activity log, timestamps in exported Ask Bon conversations, and the date shown under the Overview title.
Scheduled reports
Section titled “Scheduled reports”Report periods such as “Last 7 days” are worked out when the report runs, in your organization’s time zone.
How fresh the numbers are
Section titled “How fresh the numbers are”Devices send counts to Bon continuously. The console keeps data for a short time before asking again:
| Data | Reused for up to |
|---|---|
| Live figures (In Store Now, online state) | about 30 seconds |
| Analytics (charts, rankings, comparisons) | about 2 minutes |
| Device summaries | about 10 minutes |
| Store and organization settings | about 30 minutes |
Pages do not reload by themselves. Choose Refresh to fetch new data, or switch away and back. Returning to the browser tab also triggers a refresh.
Things that appear later
Section titled “Things that appear later”- Daily summaries, such as device uptime cells and the weather impact card, are produced once a day, so the latest day can lag.
- Catch-up data: if a device loses its connection, it stores counts locally and sends them when it reconnects, up to about two days later. Footfall for those hours fills in afterwards, so a recent day can change.
- Weather impact starts showing results after a few days of data have been collected.

