Order: Seller-initiated Change/Cancel to an Order with forfeited amounts [ORDFOR]

Guidance for Schema Version:

24.1

Definition of Capability

Airline

This capability allows the Airline to associate forfeited amounts (e.g. non-refundable amounts) as a consequence of changes/cancellations to an OrderItem and to persist these forfeited amounts across the lifecycle of an Order.

Seller

This capability allows the Seller to track values of forfeited amounts through the lifecycle of an Order.

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

Links to EASD Implementation Guidance

Capability: Shop for Replacement Flights & Services: https://standards.atlassian.net/wiki/spaces/EASD/pages/574914614

Capability: Seller-initiated Change to an Order: https://standards.atlassian.net/wiki/spaces/EASD/pages/574554168

Concept: Modification of an Order: https://standards.atlassian.net/wiki/spaces/EASD/pages/574619782

Worked Example:

Customer requests a change to an Order containing a paid OrderItem (includes 7 worked example variations): https://standards.atlassian.net/wiki/spaces/EASD/pages/842268673

Customer requests a cancellation to paid Order or OrderItems (includes 5 worked example variations): https://standards.atlassian.net/wiki/spaces/EASD/pages/817594369

Related Concepts, Capabilities and Worked Examples:

  • Concepts: Orders: https://standards.atlassian.net/wiki/spaces/EASD/pages/574717963

  • Capabilities: Orders: https://standards.atlassian.net/wiki/spaces/EASD/pages/574259560

  • Worked Examples: Orders: https://standards.atlassian.net/wiki/spaces/EASD/pages/574619770

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

This capability is only available for schema versions 24.1 and later.

The forfeited amounts structure available from ATSB Release 24.1 onward brings improvements in terms of visibility and Order integrity in cases where multiple changes occur in an Order.

Forfeited amounts are located at the Order level and support associations to OrderItems. Forfeited amounts persist with the Order when OrderItems are removed/replaced during servicing. Since forfeited amounts are values not recovered by the Seller, it is important for Sellers to be able to reconcile and balance all values in an Order against all payment transactions (incl. refunds).

Within the reshopping response, the airline is expected to include within all Offers:

  • Price differentials

  • Status of existing Services marked as cancelled (if applicable)

  • Confirmation that certain Services would not undergo any changes (with the “UnchangedIndicator”) (if applicable)

  • Details about the new services and related pricing & conditions (if applicable)

The airline’s confirmation of the Order following the changes is expected to include:

  • The creation of any OrderItem(s) (replacing older OrderItems affected by the reshop) including any potentially unchanged or delivered Service(s) transferred into the newly created OrderItem

  • The cancellation of replaced OrderItems and their respective Service(s).

  • Applicable forfeited amounts within the Order level forfeited information structure related to the changes made. /IATA_OrderViewRS/Response/Order/ForfeitedInfoList/ForfeitedInfo

Airline

Minimum Requirements

Optional Messages

OrderRetrieveRQ/OrderViewRS

OrderQuoteRQ/OrderReshopRS

OrderReshopRQ/RS

OrderChangeRQ/OrderViewRS

Seller

Minimum Requirements

Optional Messages

OrderRetrieveRQ/OrderViewRS

OrderQuoteRQ/OrderReshopRS

OrderReshopRQ/RS

OrderChangeRQ/OrderViewRS

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.