The following table gives an overview of all itinerary states within TripBuilder during the booking process. Please note that not all states may be used by your instance as they also depend on the checkout process used, for example.
Process | State | Details |
Planning | InPlanning | An itinerary has been created by the user and is in planning. |
CheckoutStarted | The user has entered the checkout process at least once for the underlying itinerary. This state may also result from an abort process where all already booked components were able to be fully cancelled with success. | |
Booking | BookingInitiated |
The user or the provider has started the checkout process (after planning). This does not mean the user could not go back to the planner and still make changes. This state is maintained throughout the checkout process until booking components in the external systems have started. |
ReservationRequested | For on request processes only. This indicates that a reservation has been requested. | |
ReservationPendingModification | A reservation is currently being modified by the supplier. | |
ReservationConfirmation |
The services in this itinerary have been reserved for a given timeframe. During this timeframe, the Itinerary can be booked with automatic confirmation. |
|
BookingRequested |
The customer has made a legally binding booking request, but the booking has not yet been confirmed on the supplier side. This can have different reasons:
|
|
BookingInProgress |
The booking has started and is currently in progress. This is an intermediate technical state during the booking, which means we're currently booking the components in external systems, and nobody must make changes to this checkout at this time. |
|
BookingCompleted | The booking is completed, and components are booked in external systems. All components are confirmed by the suppliers. | |
Manual Processing |
Manual Processing (Booking Requested) |
An itinerary will be in Manual Processing, if after booking any of the components below appear in "Open" or "None" status To confirm their booking the Customer Care user will need to manually change their status to "Booked". |
Cancellation | CancellationInitiated | The user has initiated a cancellation process. |
CancellationRequested |
The user has requested the cancellation in a legally binding form. At this point, we actually completed the cancellation process but could not completely cancel the booking. A booking in this state requires manual intervention. |
|
CancellationInProgress |
The cancellation process has started and is currently in progress. This is an intermediate technical state indicating that we're currently cancelling components in external systems. This means no changes are allowed to this checkout at this time. |
|
CancellationCompleted | The cancellation has been successfully completed. | |
Booking Change | BookingChangeInitiated |
The user has started a booking change. Technically, this means the checkout is copied while the refId is maintained. At this point, the user has an alternative itinerary in planning. |
BookingChangeInProgress |
The booking of the new components and cancellation of the old components is currently in progress. This intermediate technical state indicates that we're currently booking components in external systems. This means no changes are allowed to this checkout at this time. |
|
BookingChangeRequested |
A booking change has been requested by the user (legally binding) but has not yet been confirmed automatically. The booking is left in this state for manual intervention. This can have different reasons:
|
|
BookingChangeCompleted | The booking change has been successfully completed. All new components are booked, and old components are cancelled. | |
All | Discarded | The Checkout has been discarded before completion. |
Please Note: Payments are not strictly coupled with the checkout process. Depending on the terms and conditions of the package provider, payments might happen at different points in time and in different forms. This is the reason why payment aspects are not mentioned at all above. |
Comments
0 comments
Article is closed for comments.