NoPriceChangeInd

Open

The PriceGuaranteeTimeLimit (PGTL) element will appear in all Offers and Orders for all markets. Note that this element will have the same value as the PaymentTimeLimit (PTL), except for those markets where the new Reprice on hold is required.

The first market requiring this is Argentina. The PGTL element will be different to the PTL, forcing all users to use the new Reprice on hold functionality.

The price of an Order on hold (un paid) is only guaranteed until the PGTL expires, after which the new Reprice functionality must be used together with the OrderChange-Accept function.

The PTL, is not affected and if expires, the Order is no longer available.

There are three scenarios:

1. Before both the PTL and the PGTL expire,

   1. This is as today, whereby any Reprice will return the same price and conditions (including PGTL) given when booked. An OrderChange-Payment can be sent to fulfill the Order.

2. After both the PTL and the PGTL have expired.

   1. The Order is cancelled, you need to create a new one.

3. After the PGTL has expired, but before the PTL expires. In this case, you must Reprice the Order, as per the following flow:

   1. Send a new OrderReshopRQ-Reprice to get the applicable fare and conditions

   2. If the price has not changed, send an OrderChange-Payment

   3. If the price has changed the system will generate a new Offer which must be accepted using the OrderChange-Accept. Once accepted it can be paid for. The steps would be as per the following:

In the<OrderReshopRS> you can receive one of the following two options:

There are no changes: <NoPriceChangeInd>

The price has changed: <RepricedOfferItem> and <OriginalOrderItem> with a new PGTL.

If after repricing the Order has not change <OrderReshopRS>, only the <NoPriceChangeInd> tag is returned indicating that nothing has changed.

NoPriceChangeInd example:

Open