3. Book Using Session Control


	Guest Journey: Journey: Manage Channel Reservation Using Session Control This workflow is a more advanced booking flow based on a two-phase reservation flow. First, the channel sends an "in-session" reservation request (Create, Modify, or Cancel). OPERA Cloud then confirms the requested reservation action only for that session. The request is in a hold state, not known to the hotelier. Second, the channel sends a Commit request to validate the reservation action, which will then become visible by the hotelier. Alternatively, the channel can send an Ignore request to remove the latest reservation action. If OPERA Cloud does not get a Commit or Ignore message within 30 minutes from the original reservation action request, the reservation action is automatically ignored and the current hold state remains. If the request was to create a reservation, the reservation in session is deleted.

Guest Journey:

Journey: Manage Channel Reservation Using Session Control

This workflow is a more advanced booking flow based on a two-phase reservation flow.

First, the channel sends an "in-session" reservation request (Create, Modify, or Cancel). OPERA Cloud then confirms the requested reservation action only for that session. The request is in a hold state, not known to the hotelier.

Second, the channel sends a Commit request to validate the reservation action, which will then become visible by the hotelier.

Alternatively, the channel can send an Ignore request to remove the latest reservation action.

If OPERA Cloud does not get a Commit or Ignore message within 30 minutes from the original reservation action request, the reservation action is automatically ignored and the current hold state remains. If the request was to create a reservation, the reservation in session is deleted.

Shop and Book Use Cases

1. Shop

See Distribution Shop Operations and Error Codes.

2. Book

See Distribution Book Operations and Error Codes.

Parent topic: Workflows