We’ve revamped Booking History so it’s much easier to understand what happened to a booking, when it happened, and where the change came from.
A clearer, more usable History page
History is now easier to scan and drill into, so you can quickly find the right booking and see the important activity without wading through noise.
Related changes are grouped together and repeated “bursts” of updates are condensed so the timeline stays readable.
Tracks what changed (before → after), automatically
When a booking is updated, History records the key details that changed (for example: time, date, duration, guest count, contact details, notes, status).
Changes are recorded regardless of the source of the change; be it the Gantt or list view or anywhere else.
History shows the previous value and the new value, so you don’t have to guess what was edited.
Relations are also logged (so you'll be able to see when guest types etc are changed)
History now records the change source (e.g. changes made in the admin system vs changes coming from integrations/API vs automated/system updates), which makes it much easier to understand why something changed.
Helps identify who made admin changes
When changes are made by logged-in staff in the admin, History can now record the staff member’s name, reducing “who changed this?” confusion and helping with shift handovers and also helping you understand changes that may otherwise seem random!
Reliability improvements
Booking duration now updates correctly when guest numbers change, even if an older/stale value is sent from a device/browser.
Table assignments are automatically cleared when a booking changes in a way that makes the currently assigned table no longer suitable, helping prevent seating issues.
The modal to view the booking history no longer is covered by the top navigiation bar.
