The Airline has the ability to persist a cancelled OrderItem such that some or all of its value is reusable in subsequent servicing operations.
The Seller has the ability to track whether an OrderItem’s value is partially or entirely reusable in subsequent servicing operations.
Capability: Shop for Replacement Flights & Services:
Capability: Seller-initiated Change to an Order:
Concept: Modification of an Order:
Worked Example:
Customer requests a cancellation to paid Order or OrderItems resulting in a Reusable amount:
Concepts: Orders:
Capabilities: Orders:
Worked Examples: Orders:
For all capabilities, please also consult the list of general guidelines for adherence to best practices that span across several capabilities and messages: |
This capability is only available for schema versions 24.1 and later.
A reusable amount occurs in cases where the cancellation of an OrderItem does not trigger a refund and the airline is not yet able to precisely calculate the potentially refundable or reusable amount, thus the OrderItem is kept “ACTIVE” (even though the Services within would be cancelled). Typically, the Airline would then await either a refund request or further reshopping operations by the Seller, at which time the exact amounts would be calculated. The DeliveryStatusCode(s) of the Service(s) must be set to “REMOVE HOLD VALUE”.
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).
Expected data elements and their expected values in the scenario of a cancelled OrderItem with a reusable amount (as per the EASD Implementation Guidance Worked Example):
Messages | Element location | Expected Value |
OrderReshopRQ | …/UpdateOrder/ReshopOrder/ReshopOrderChoice/ServiceOrder/DeleteOrderItem/OrderItemRefID | |
OrderReshopRQ | …/UpdateOrder/ReshopOrder/ReshopOrderChoice/ServiceOrder/DeleteOrderItem/RespendInd | true |
OrderReshopRS | …/ReshopResults/ReshopOffers/Offer/DeleteOrderItem/ExistingOrderItem/ExistingService/FutureDeliveryStatusCode | REMOVED HOLD VALUE |
OrderReshopRS | …/ReshopResults/ReshopOffers/Offer/DeleteOrderItem/ExistingOrderItem/ExistingService/FutureStatusCode | CANCELLED |
OrderReshopRS | …/ReshopResults/ReshopOffers/Offer/DeleteOrderItem/PriceDifferential/DifferentialTypeCode | Reusable |
OrderViewRS | …/Response/Order/OrderItem/Service/DeliveryStatusCode | REMOVED HOLD VALUE |
OrderViewRS | …/Response/Order/OrderItem/Service/StatusCode | CANCELLED |
OrderViewRS | …/Response/Order/OrderItem/StatusCode | ACTIVE |
OrderViewRS | …/Response/Order/StatusCode | OPENED |
OrderViewRS | …/PaymentFunctions/PaymentProcessingSummary/PaymentStatusCode | SUCCESSFUL |
Minimum Requirements |
---|
OrderRetrieveRQ/OrderViewRS |
OrderReshopRQ/RS |
OrderChangeRQ/OrderViewRS |
Minimum Requirements |
---|
OrderRetrieveRQ/OrderViewRS |
OrderReshopRQ/RS |
OrderChangeRQ/OrderViewRS |