This safeguard helps ensure:
Improved data accuracy and reporting consistency
Reduced risk of accidental data loss
Clearer booking lifecycle management
Better alignment with audit and compliance standards
Why We Are Making This Change
Protecting Revenue Accuracy
Deleting active bookings removes them from historical reports, which can create gaps in revenue and performance data—especially for Definite business.
Requiring a Lost status ensures all lost business is captured correctly and included in daily snapshots and historical reporting.
Preserving Operational Audit Trails
Many teams rely on booking history to understand changes, troubleshoot issues, and maintain accountability.
Changing a booking to Lost preserves a clear, traceable lifecycle instead of removing records entirely.
Reducing Accidental Data Loss
Bookings are sometimes deleted unintentionally, particularly during high-volume periods or when users are multitasking.
Requiring a status change adds an intentional step that helps prevent mistakes.
What Will Change
Users can no longer delete a booking or room block that is in an active status:
Lead
Tentative
Definite
To delete a booking or room block, it must first be marked as Lost
Once marked as Lost, the booking or room block can be deleted if required by the organization’s workflow
How This Works in the System
If the status is Lead, Tentative, or Definite, the Delete option is disabled
If the status is Lost, the Delete option is enabled
The UI clearly indicates this restriction (for example, via a tooltip explaining that deletion is only allowed once a booking is marked Lost)
Recommended Best Practice
Hotels may want to create Lost Business Reasons to support this workflow, such as:
User error
Test booking
Duplicate booking
Using clear lost reasons improves reporting clarity and makes it easier to understand why bookings were canceled or removed.