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

Guidance for Schema Version:

21.3

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

This capability document is currently in the SOSB Ballot process. Once the capability has been approved in the voting process, the links will be updated.

Update links: Capability: Seller-initiated Change to an Order

Text from Seller-initiated Change to an Order, Variant 2:

Variant 2
Change to an Order not based on an Offer/Reshop
Preconditions
▪ An Order has been created
Process

  1. The Seller requests the change by sending change details.

  2. The Airline reviews changes requested and sends response to Sellers

Post Condition
Success
▪ Order is changed - updated Order Information is received by the Seller.
Failure
▪ Airline is unable to process the changes
▪ Order is not changed and an error or warning is returned.
Relevant Messages
▪ OrderChangeRQ
▪ OrderViewRS

Related Concepts, Capabilities and Worked Examples:

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

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/ChangeOrder/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:

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.

e.g. correcting a contact phone number:

...
<ChangeOrder>
  <UpdatePax>
    <Current>
      <PaxRefID>PAX001</PaxRefID>
    </Current>
    <New>
      <PaxRefID>112233</PaxRefID>
    </New>
  </UpdatePax>
</ChangeOrder>
...
<DataLists>
  <PaxList>
    <ContactInfoList>
      <ContactInfo>
        <ContactInfoID>CTC123</ContactInfoID>
        <Phone>
          <PhoneNumber>+1 222 333 444</PhoneNumber>
        </Phone>
      </ContactInfo>
      <ContactInfo>
        <ContactInfoID>CTC456</ContactInfoID>
        <Phone>
          <PhoneNumber>+1 555 666 777</PhoneNumber>
        </Phone>
      </ContactInfo>
    </ContactInfoList>
    <Pax>
      <ContactInfoRefID>CTC123</ContactInfoRefID>
      <PaxID>PAX001</PaxID>
    </Pax>
    <Pax>
      <ContactInfoRefID>CTC456</ContactInfoRefID>
      <PaxID>112233</PaxID>
    </Pax>
  </PaxList>
</DataLists>
...
<Order>
  <OrderID>ORD12345</OrderID>
  <OwnerCode>XB</OwnerCode>
</Order>
...  

Airline

Minimum Requirements

OrderChangeRQ/OrderViewRS

Seller

Minimum Requirements

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.