Skip to documentation content

Booking Operations

Understand the customer booking journey

Trace a customer from availability search through room selection, Book Now, payment when required and signed confirmation.

The supported journey is a sequence of Free-owned decisions. A theme can change the presentation, but it must not replace the availability or pricing service.

Journey sequence

  1. The guest opens /search-availability/.
  2. They select check-in, check-out, adults and children.
  3. Hotel Booking validates the request and returns available room types.
  4. The guest opens a room detail view or selects Book Now.
  5. Hotel Booking rechecks availability, capacity and the authoritative price.
  6. The guest enters contact details and chooses an available payment method.
  7. For Stripe or another online gateway, the guest completes the payment step.
  8. The signed booking confirmation displays the booking code, stay, price and payment state.

The compact Room Detail availability form is a read-only GET attempt. It does not create a booking, accept guest details, apply a coupon or process payment.

Expected result

The confirmation represents the same room, stay interval, guests, currency, taxes, total and payment result that were verified on the server. A refresh of the confirmation does not create another booking or charge.

Staff verification

Use the first booking checklist with a dedicated test address. In Hotel Booking → Bookings, find the booking code and compare its saved snapshot with the confirmation. Check inventory for the same dates after creation.

If a guest reports an error, search for an existing booking before asking them to retry. Preserve the booking code and redacted error details; never ask for a card number or expose a payment secret.

Was this article helpful?

Your feedback helps us improve the documentation.