Shop: Shop For or with Ancillaries [SHPANC]

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 Airline to provide a list of available services based on existing flight Offers/Orders or defined flight criteria. The airline may consider additional qualifiers and context in the process of calculating the resulting offers.

Seller

This capability allows the Seller to request from an Airline a set of Services based on:

  • OfferId

  • OrderId

  • Flight Details, passenger type and defined dates (PaxSegment)

The Seller may provide additional qualifiers and context which the Airline may consider in the content of the resulting offer(s).

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

Links to EASD Implementation Guidance

Shopping for Ancillaries

  • Capability: Shop for ancillaries: https://standards.atlassian.net/wiki/spaces/EASD/pages/574226524

Related Concepts, Capabilities and Worked Examples:

  • Concepts: Shop: https://standards.atlassian.net/wiki/spaces/EASD/pages/574750733

  • Capabilities: Shop: https://standards.atlassian.net/wiki/spaces/EASD/pages/574750721

  • Worked Examples: Offers: https://standards.atlassian.net/wiki/spaces/EASD/pages/574881865

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

Ancillary services can be provided in several steps of a shopping process, depending on an Airline’s implementation and message flow. Ancillaries are presented either as:

Ancillaries within regular Offer structures are not required to be mandatory (using the Mandatory indicator). Each optional ancillary Offer Item is priced, which would later allow the Seller to calculate the payable amount of the mandatory items, as well as the optional ancillaries they select through OrderCreateRQ (or optionally OfferPriceRQ, if this step is required prior to Order creation).

Airlines can construct ancillary Offer Items directly via AirShoppingRQ/RS (and OrderReshopRQ/RS, in case of servicing), or separate them into the ancillary-specific message pair ServiceListRQ/ServiceListRS, depending on their implementation. Seat-related ancillaries, typically presented through the SeatAvailabilityRQ/RS message pair, are technically also A-La-Carte ancillary services which need to be selected in later steps of the shopping process and combined with their counterpart flight-related Offers (through OfferPriceRQ or OrderCreateRQ).

Airline

Demonstrate construction of ancillary Offer Items for seats and bags.

Any one of the following message pairs

AirShoppingRQ/RS

ServiceListRQ/RS

SeatAvailabilityRQ/RS

OfferPriceRQ/RS

Seller

Request ancillary services and present ancillaries on front end.

Minimum Requirements…

…and any one of the following message pairs

Optional Messages

User Interface Screenshots

AirShoppingRQ/RS

SeatAvailabilityRQ/RS

ServiceListRQ/RS

OfferPriceRQ/RS

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.