TapNTable 0.10.11: one clock, and it belongs to your restaurant
Promotions on local time
Promotion time windows - happy hours, validity periods with start and end times - were compared against the server clock, which lives in UTC. In practice, during daylight saving time, a promotion meant to open at 09:00 only opened at 10:00. Every check now uses the restaurant clock: start, end, and conditions by day of week or time range. Automatic activation and expiry of scheduled promotions also respect the local day of each franchise - a promotion starting tomorrow no longer wakes up an hour before midnight.
Google Calendar without forgotten reservations
The daily reservation sync with Google Calendar started at midnight UTC. As a result, reservations booked for the first hour of the local day could be left out of that day’s sync. The window now opens at the restaurant’s midnight.
Reports with an honest timestamp
The “generated at” stamp on CSV and PDF exports came out in the server timezone with a fixed format. It now uses the restaurant timezone and the date and time format you configured in settings - consistent with the rest of the product.
The calendar counts your restaurant’s days
The “Today”, “Last 7 days”, “Last 30 days”, “This month” and “Last month” shortcuts in the report date picker were anchored to the device clock. In the early hours, or with a manager travelling in another timezone, the numbers were for the wrong day. They now anchor to the restaurant’s day. And in the audit log, the date filter could pick the day before the one you selected in certain timezones - fixed.
Everything counts the same day
Under the hood, tests now guarantee that order tokens, daily report totals and promotion windows all count the same local day - even near midnight, and even with the restaurant in a different timezone than the server.
Version 0.10.11 is available now and reaches installations through the built-in updater, as usual.