Enhanced Exchanges: Early Adopter Release
Enhanced Exchanges (formerly Automated Exchanges for Smartpoint Cloud) is currently available only to agencies that are activated for Early Adopter testing. If your agency would like more information about being part of our pre-release testing, please contact your Travelport representative.
Enhanced Exchange
Overview
Enhanced Exchange is available for Travelport+ itineraries. To modify an NDC itinerary, refer to Modify an NDC booking.
Enhanced Exchange determines eligibility and provides calculations for voluntary exchanges and refunds. This repricing enables agents to offer their customers fully informed choices for new itinerary options, such as flight changes, revised fares, and tax amounts including any applicable change fees.
With Enhanced Exchange, agents no longer need to update the booking file with new flights and fares before starting the exchange process. Agents only need to display a booking file to start the exchange.
Enhanced Exchange supports even exchanges, exchange of tickets with residual value, and add collect exchanges.
For more information, see:
-
Eligibility to see the provisioning, itinerary, ticketing requirements that are automatically validated by Enhanced Exchange.
-
View cancellation and change fees to evaluate the traveler's options before starting the exchange process.
-
Exchange tickets to see the basic workflow for Enhanced Exchange.
-
Exchange and ticket (BSP) to create an Enhanced Exchange and ticketing for BSP markets.
-
Exchange and ticket (ARC) to create an Enhanced Exchange and ticketing for ARC markets.
-
Exchange and hold (BSP and ARC) to hold an exchanged itinerary before ticketing.
-
Known issues
-
If the original ticket was issued with a form of payment in the TMU entry and is not stored in the F. field, then Enhanced Exchange will return an error on Review and Confirm screen and the exchange will not be able to be processed. This scenario is only applicable for an even exchange. As a workaround, you can add a form of payment in the F. field in the booking file before proceeding with an exchange.
-
The confirmation screen shows the original ticket numbers. View booking file shows the correct updated ticket details.
-
If the ticketed booking file does not have F. (FOP) field and user performs even exchange or exchange with refund, then this scenario may fail.
-
For Hold exchanges:
-
If the FOP is changed on the Review and Confirm screen, the new FOP is currently ignored and is not updated in the new filed fare that is stored.
-
When the graphical booking file is viewed after a Confirm and Hold, the original ticket number is not shown on the Tickets card and the Tickets card is blank.
-