Shop: Seat Map and Availability [SHPSTA]

Guidance for Schema Version:

21.3

Definition of Capability

Airline

This capability allows an Airline to return seat map details, including seat availability

Seller

This capability allows the Seller to request and receive seat map details, including seat availability

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: https://standards.atlassian.net/wiki/spaces/ARMI/pages/584318980/General+Guidance

This is a continuation of Seat Options capability. In addition to the requirements of Seat Options, implementers are expected to return seat availability details as described below.

Airline

Make use of OccupationStatusCode at a per-seat level to inform of the availability of a seat, making use of PADIS Code Set 9865:

Minimum Requirements

SeatAvailabilityRQ/SeatAvailabilityRS

Seller

Expected screenshots of the Seller’s travel platform showing the seat map from the Seat Options capability, as well as rendering of seat availability.

Minimum Requirements

User Interface Screenshots

SeatAvailabilityRQ/SeatAvailabilityRS

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.