Order: Seller-Initiated Change to an Order Not Requiring Reshop [ORDPAX]

Guidance for Schema Version:

21.3 - Please consult the ARM index Schema version 21.3 regarding validation of capabilities within the ARM index program.

Definition of Capability

Airline

The Airline has the ability to change an Order without the need to reshop. This capability is validated based on updating Passenger details.

Seller

The Seller has the ability to request a change to an Order without the need to reshop. This capability is validated based on updating Passenger details.

NOTE: System Providers will use the above definition that pertains to their customers for Capabilities Verification.

Links to EASD Implementation Guidance

Capability: Seller-initiated Change to an Order, Variant 2: https://standards.atlassian.net/wiki/spaces/EASD/pages/574554168

Concept: Modification of an Order: https://standards.atlassian.net/wiki/spaces/EASD/pages/574619782

Worked Example: Customer Updates Existing Contact Details: https://standards.atlassian.net/wiki/spaces/EASD/pages/673021953

Related Concepts, Capabilities and Worked Examples:

Concepts: Orders: https://standards.atlassian.net/wiki/spaces/EASD/pages/574717963
Capabilities: Orders: https://standards.atlassian.net/wiki/spaces/EASD/pages/574259560
Worked Examples: Orders: https://standards.atlassian.net/wiki/spaces/EASD/pages/574619770

NOTE: Retailing Capabilities Verification Guidance will align to the published EASD Implementation Guidance at all times. From time to time when new guidance is published this will be updated and supersede any Retailing Capabilities Verification Guidance listed below.

Retailing Capabilities Verification Guidance

For all capabilities, please also consult the list of general guidelines for adherence to best practices that span across several capabilities and messages: https://standards.atlassian.net/wiki/spaces/ARMI/pages/584318980

Updating passenger details works by providing the old data together with the new data it is meant to replace within the following function of OrderChangeRQ:

/IATA_OrderChangeRQ/Request/ChangeOrderChoice/UpdatePax

If only new data is being appended to the passenger’s profile, then the “Current” must be provided, but only for the PaxID (no other details required).

Updating passenger details requires the following steps:

Seller enters reference ID of the passenger (as it appears in OrderViewRS) in the “Current” element:
- /IATA_OrderChangeRQ/Request/ChangeOrderChoice/UpdatePax/Current/PaxRefID
and includes the passenger details that are required to change under DataLists/PaxList/Pax:
- /IATA_OrderChangeRQ/Request/DataLists/PaxList/Pax…
Seller enters a Seller-generated Passenger reference ID (this is temporary and used only within a single XML API transaction):
- /IATA_OrderChangeRQ/Request/ChangeOrderChoice/UpdatePax/New/PaxRefID
and includes the new passenger details intended to replace the details earlier provided under the “Current” structure.
/IATA_OrderChangeRQ/Request/DataLists/PaxList/Pax…

The Airline’s OrderViewRS should then reflect the modified and/or appended details. Note: The PaxID returned should still be the same as per previous OrderViewRSs.

This function is not intended for modifications to a passenger’s name - use the “Names changes/corrections through reshopping“ capability instead.

Airline

Minimum Requirements
OrderRetrieveRQ/OrderViewRS
OrderChangeRQ/OrderViewRS

Seller

Minimum Requirements
OrderRetrieveRQ/OrderViewRS
OrderChangeRQ/OrderViewRS

NOTE: For all versions prior to that listed above (generally the most recent), the verification will be based on the guidance available for that version. In the case that no guidance is available, verification will be at IATA’s discretion.