Shop: Customer Touchpoints / Device Types [SHPDVC]

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

Ability to use customer technical details to personalize the offer returned.

Seller

Ability for the Seller to inform the airline of the customer technical details related to touchpoints of interaction (e.g. device types, device locations)

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:

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

Sellers have the ability to inform Airlines what type of device is being used by the customer to interact with the Seller. This allows the Airline to tailor the content they return to better suite the device type in question. e.g. lower-resolution rich media and compressed videos for an optimized smartphone experience.

e.g. /IATA_AirShoppingRQ/Request/ResponseParameters/Device/DeviceCode

In addition to device types, the Seller can also transmit to the Airline geolocation details pertaining to the customer’s device. Country, city or detailed longitude/latitude coordinates can be provided. This could drive other personalization in content such as:

constructing Offers in specific languages or for specific markets in case these details are otherwise missing from Point of Sale or other language/currency customer preferences.
presenting flights from “airports nearest to you”
e.g. /IATA_AirShoppingRQ/Request/ResponseParameters/DeviceLocation/Country/CountryCode

The device types available for use are listed here: https://guides.developer.iata.org/v211/docs/atsb-tdt

Device types can also drive an Airline’s risk assessment related to payment methods. e.g. They may wish to support a subset of payment card options, or even exempt the payer of 3D-Secure authentication, if the device used does not belong to the payer (e.g. a tablet or computer terminal owned and operated by a travel agent or other 3rd party).

Airline

Demonstrate differentiation of content specifically driven by a certain device type being used by the customer.

Any one of the message pairs below	Optional messages
AirShoppingRQ/RS	OrderCreateRQ/OrderViewRS
ServiceListRQ/RS	OrderChangeRQ/OrderViewRS
SeatAvailabilityRQ/RS	OrderRetrieveRQ/OrderViewRS
OfferPriceRQ/RS
OrderReshopRQ/RS

Seller

Demonstrate ability to capture and send device type information to Airline.

Any one of the message pairs below	Optional messages
AirShoppingRQ/RS	OrderCreateRQ/OrderViewRS
ServiceListRQ/RS	OrderChangeRQ/OrderViewRS
SeatAvailabilityRQ/RS	OrderRetrieveRQ/OrderViewRS
OfferPriceRQ/RS
OrderReshopRQ/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.