Order: Reshopping for Ancillaries [ORDRE2]

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

This capability allows the Seller to request a set of Offers as a replacement of or in addition to specific OrderItem(s) that include ancillaries.

Seller

This capability allows the Seller to request a set of Offers as a replacement of or in addition to specific OrderItem(s) that include ancillaries.

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

Links to EASD Implementation Guidance

Capability: Shop for Replacement Flights & Services: https://standards.atlassian.net/wiki/spaces/EASD/pages/574914614

Capability: Seller-initiated Change to an Order: 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 Adds an Ancillary to Existing Order (includes 2 worked example variations): https://standards.atlassian.net/wiki/spaces/EASD/pages/842301482

Worked Example: Customer requests a change to an Order containing a paid OrderItem (includes 7 worked example variations): https://standards.atlassian.net/wiki/spaces/EASD/pages/842268673

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

All ancillary reshopping scenarios can be considered within ARM index validation for ORDRE2. The use of penalties, forfeited amounts, and residual values are not reviewed or validated within ORDRE2.

Ancillaries can be purchased post-Order-creation. The ServiceListRQ/RS and SeatAvailabilityRQ/RS messages can be used to request and present ancillaries related to an Order with existing flight services. These can then be selected by the Seller through the OrderQuoteRQ/OrderReshopRS message pair and the change is the committed (and potentially paid for) through OrderChangeRQ.

While the OrderReshopRS message is able to include ancillaries (similarly to AirShoppingRS), its main function is to reshop for flights. OrderReshopRQ can, however, support ancillary-related shopping criteria/preferences (e.g. Airline Taxonomy service codes) during its flight-shopping request. This is also true of OrderQuoteRQ, whose response is also OrderReshopRS.

Note: OrderQuoteRQ is required for scenarios aiming to “replace” or “cancel” ancillary Order Items, as a price differential needs to be returned. OrderChangeRQ is, in principle, able to accept an OfferID directly from ServiceListRS, however it is recommended that “adding” ancillaries also leverage the step through OrderQuoteRQ for consistency.

Pre-21.1 Implementations

Due to limitations in releases prior to 21.1, ancillaries from ServiceListRQ/RS or SeatAvailabilityRQ/RS cannot be efficiently brought into a reshopping scenario, as the OfferIDs/OfferItemIDs from these shopping responses cannot be carried over to OrderReshopRQ. 21.1 solves this by adding the new OrderQuoteRQ message.

Adding an ancillary to an Order would therefore need to be done in one of the following ways:

• Using OrderReshopRQ to ask for ancillaries related to a flight which exists in the passenger’s Order. The Airline would be able to return any ancillaries in the OrderReshopRS (related to the flight details entered in OrderReshopRQ), which can then be carried over and confirmed in OrderChangeRQ with or without payment instructions.

• Obtaining ancillaries from either ServiceListRQ/RS or SeatAvailabilityRQ/RS related to the flight and skipping the OrderReshopRQ/RS steps, entering these OfferIDs directly into OrderChangeRQ. If instant payment is required, the Seller will have to take care of calculating payable amounts themselves without the guidance normally offered through OrderReshopRS.

Likewise, replacing ancillaries in a reshopping scenario are also affected by the aforementioned limitations, and actually presents further challenges to the Seller, as the Airline would have a harder time describing what are the implications (additional collection or residual values, penalty fees, etc.) of replacing an existing ancillary. The workaround for this scenario extends the two solutions above for “adding ancillaries to an Order” with an additional step:

• Firstly cancelling the OrderItem intended to be replaced through OrderReshopRQ/RS (indicating the preference to “respend”, so as to not trigger a refund). Once this cancel operation is complete (through OrderChangeRQ/OrderViewRS), the new ancillary could be added by following either of the two steps mentioned above. The value stored from the previous cancellation can be allocated towards the new ancillary being purchased.

If submitting messages using a version prior to 21.1, please also include a snapshot of the Order (OrderRetrieveRQ/OrderViewRS) prior to the first reshopping step of the Order.

Airline

Seller

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