Order: Order Creation Without Tickets/EMDs [ORDCWT]

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

The ability for an airline to create and fulfill an Order from a selection of Offer(s) and Offer Item(s) without the need to create PNRs/tickets/EMDs (ONE Order) (capability only available from v18.2 onwards).

Seller

The ability for a seller to process an Order without the need to reference PNRs/tickets/EMDs (ONE Order)(capability only available from v18.2 onwards).

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

Links to EASD Implementation Guidance

Worked Example: Shop and Order a Flight For a Single Passenger: https://standards.atlassian.net/wiki/spaces/EASD/pages/600375364

Worked Example: End to End Payment Via Pre Authenticated Card Transaction: https://standards.atlassian.net/wiki/spaces/EASD/pages/574849139

Worked Example: End to End Payment via Settlement Plan: https://standards.atlassian.net/wiki/spaces/EASD/pages/676724743

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

Demonstrate use of NDC Order creation based on OfferIDs using the following structure:

The Order must be created and fully paid in the flow submitted (payment can be carried out through either OrderCreateRQ or OrderChangeRQ).

Airline

Create Orders including fulfillment statuses without associating any legacy accountable documents from the following structure:

Assign delivery status code to Service(s) for fulfilment:

Minimum Requirements

AirShoppingRQ/RS or OfferPriceRQ/RS

OrderCreateRQ/OrderViewRS

OrderChangeRQ/OrderViewRS (optional, if payment is carried out through OrderChangeRQ)

Seller

Minimum Requirements

AirShoppingRQ/RS or OfferPriceRQ/RS

OrderCreateRQ/OrderViewRS

OrderChangeRQ/OrderViewRS (optional, if payment is carried out through OrderChangeRQ)

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.