Shop: Personalize Offers Based on Passenger Type, Loyalty Programs or Other Agreements [SHPPER]

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


This capability allows the Airline to respond to a Seller request with a set of Offers based on frequent flyer status or type of passenger (e.g. infant, senior, military, resident, corporate, etc.)


This capability allows a Seller to request a set of Offers based on frequent flyer status or type of passenger (e.g. include infant, senior, military, resident, corporate, etc.)

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

Links to EASD Implementation Guidance

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

For all capabilities, please also consult the list of general guidelines for adherence to best practices that span across several capabilities and messages:

Personalization involves pricing offers and/or including services depending on additional attributes of a customer, such as:

  • Holding a Frequent Flyer account the airline or alliance partners

  • A specific tier level of their Frequent Flyer program

  • Other personal attributes of a customer, such as birthdays, number of previous flight purchases, etc.

  • Attributes of organization based on commercial agreement (such as corporate IDs)


Demonstrate ability to construct priced offers and/or different bundles of products based on additional attributes of a customer. Submit two shopping responses, one for an anonymous ADT traveler and one with personalized pricing and/or additional services, both for the same itinerary.

Note: If your shopping requests are based on existing Orders, please also submit OrderViewRS traces to include the attributes of the passengers on which the personalization is based on.

Any one of the following message pairs x 2:

AirShoppingRQ/RS x 2

ServiceListRQ/RS x 2

SeatAvailabilityRQ/RS x 2

OfferPriceRQ/RS x 2


Demonstrate ability to pass additional attributes of a customer in shopping queries.

Any one of the following message pairs:





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.