Free owns the booking lifecycle. Pro can add cancellation policy evaluation and refund history, but a lifecycle action and a transfer of money remain separate operations.
Before changing a booking
Use an authorized staff account. Open the booking, verify the guest, stay dates, room quantity and payment ledger, and check any cancellation terms saved with it. Keep a recoverable backup before a bulk operational change.
Follow the supported transition
| Current status | Available next lifecycle states |
|---|---|
| Pending | Confirmed, Cancelled, No-show |
| Confirmed | Checked In, Cancelled, No-show |
| Checked In | Checked Out |
| Checked Out, Cancelled, No-show | No further ordinary lifecycle transition |
These are the lifecycle possibilities; current permissions and Pro policy checks can further restrict an action. Use the action the interface makes available, review its details and confirm once. Do not treat the table as permission to bypass a server rejection.
For a cancellation or no-show covered by Pro, read the saved policy and current financial estimate. Server time, the booking snapshot and the locked ledger are checked again when confirming. If the decision changes, review the new result before confirming again. Customer cancellation and hotel-initiated cancellation have different policy treatment.
Check the outcome
Reload the detail and verify the new booking status, activity entry, inventory effect and any cancellation/refund history. No-show terms in this policy version are 0% refundable; hotel-initiated cancellation is a separate workflow. Legacy or externally owned terms may require manual review.
Cancellation, no-show and check-out do not automatically dispatch a gateway refund. Staff must use the supported gateway refund operation or record a verified external outcome.
Terminal states are not ordinary undo buttons. Correct an accidental action through an authorized, reviewed recovery procedure; do not reopen a booking by editing its database row. Keep historical financial records intact.
