Add ancillaries to existing booking

Workflow description

This workflow is used to add ancillaries to an existing booking, e.g. new seats or services.

The Client has to retrieve the existing booking first, then he is able to shop for new seats or services.

After the Client has decided, which amendments he wishes to attach, he can inquire these changes using an IATA_OrderChangeRQ and the endpoint “/order/changeInquiry”

This will simulate the update and return an IATA_OrderViewRS containing the Order and how it would look after the change. This may also include possible update or cancellation fees.

Please note that after the inquiry step, the Order has not been changed yet!

The inquiry step is also fully optional, it is just an assisting step to provide final information to the customer before actually changing the Order.

If the Client is sure to apply the changes, he can use the same IATA_OrderChangeRQ like in the inquiry to change the booking using the endpoint “/order/change”.

This will return an IATA_OrderViewRS with the successfully changed Order, or an error message, if something prohibited the change process.

Message Flow

IATA_OrderReshopRQ or IATA_OrderChangeRQ?

In this workflow IATA_OrderChangeRQ is the only option in the NDC.one API, because IATA_OrderReshopRQ is missing some features needed for this workflow.

In IATA_OrderReshopRQ it is not possible to request specific seats or services, it is merely possible to give unspecific shopping criteria.

Therefore the decision was made to support only IATA_OrderChangeRQ for the pricing step.