Booking Amendments

An amendment to a booking or a booking item is defined as a change of requirements, which can come about as a result of a number of reasons (e.g.: flight changes, problems with obtaining visas, etc.). If permitted by the property these changes should always be handled as amendments rather than cancelling an existing booking or booking item and then creating a new booking or booking item.

It is possible to amend the following details:

  • arrival date
  • check-out date
  • number of nights
  • tour date
  • number of rooms
  • type of rooms
  • number of passengers and passenger names
  • departure date
  • agent reference

It is NOT possible to amend the following details:

  • item
  • room category
  • city

It is important to note, that when amending a booking the same passengers assigned to the original pax IDs should ALWAYS be kept. If, for example fewer passengers are travelling, no passengers should be removed from the pax ID list. The original pax IDs should be kept and the change or re-assignment should be performed via the <ModifyBookingItemRequest> message.

The departure date cannot be later than the arrival date of any of your booking items or earlier than 180 days before the earliest arrival date of any of your booking items. If you modify the arrival date to an earlier date then you need to ensure you are also modifying the departure date to an earlier date BEFORE you modify the arrival date. If you modify the arrival date to a later date then you need to ensure you are also modifying the departure date to the same date as the new arrival date AFTER you modify the arrival date. The same applies if you would like to add another item to an existing booking. If the new item has an arrival date or tour date that lies before the departure date of the existing booking you first need to send us a <ModifyBookingRequest> adjusting the departure date to the earlier date and then send the <AddBookingItemRequest>.

If an amendment is not available, a response with the ItemStatus RJ (Rejected) will be returned. Immediately afterwards, another response with the original details of the booking in C (Confirmed) status will be generated. Therefore, when a response with the ItemStatus RJ is generated for the amendment, no cancellation request should be sent for that item, otherwise the original booking with the confirmed criteria will be cancelled.

The above information refers to general amendment rules; to check if amendments are permitted for a specific property it is necessary to perform a <SearchChargeConditionsRequest> before sending a <ModifyBookingItemRequest>.

If the booking amendment module is implemented we strongly recommend the push mechanism is used. Further information on this can be found under the Booking Processes document.

The attached amendment examples are intended as guidelines only and do not cover all possible scenarios.
These documents should be read in conjunction with the document explaining the Booking Statuses & Booking Flows.

Transfer Amendments

Hotel Amendments (Participation Level 0)

Hotel Amendments (Participation Level 2)

Docs Navigation