Order Concepts

Owned by Vanni Sanvincenti
Last updated: Sept 22, 2023

 

Overview

This document describes the structure of Order, OrderItems, Services and relevant data directly associated with these items. This document will clarify the use of Status elements at these three levels and define what are the characteristics of an “open” item versus a “closed” item (that would no longer appear in OrderRetrieve requests).

Order Types

Order

An Order is a list of products/services that Customer(s) intend to buy or bought using the Customers’ money. An Order is composed of two main element structures: one or more OrderItem elements and, within these, one or more Service elements. Below is a basic illustration of an Order structure, including some additional key data elements:

 

An Order has the below elements.

Order Statuses 

Order status could be: 

CLOSED: When every Order Item (and Service) is in status cancelled and there is no value store/open document present in the Order

OPEN: Anything else   

OrderItem 

An OrderItem represents the product that is bought by the Customer, or it can also represent the product the customer intends to buy. An OrderItem should have at least one service per passenger. An OrderItem has an associated identification number that is not standardized currently.

Each OrderItem is created from a corresponding OfferItem. As such an OrderItem is also a representation of the set of Service(s) collectively evaluated for pricing.  

Order Item Statuses 

OrderItem statuses are described below, the status of the OrderItem is either: 

CANCELLED: When all the contained services in the OrderItem have a service status of cancelled or transferred

ACTIVE: Anything else   

Ordered Services 

One or multiple deliverable services per passengers, associated to the product/ OrderItem. An Ordered Service should be the lowest level of granularity which can be delivered – thus by definition it should not be possible for an Ordered Service to be partially delivered.

In contrast with Offered Services (Services within an OfferItem), Ordered Services do not group references to Passengers and related flights together.

While a single Offer Service can reference multiple Passengers and flight Segments, Order Services multiply more granularly, as they can only reference one Passenger and one flight Segment. This precision is later needed for fulfilment tracking and revenue accounting.

Note that each OfferItem always becomes a single OrderItem, therefore the change in granularity only happens at the Service level. The diagram below illustrates the transition between an Offer and an Order at time of Order creation, using two Passengers travelling round-trip from JFK to CDG via LHR with ancillaries on only certain Segments:

Ordered Service has the following key elements:

Service Status

REQUESTED: Airline is in the process of confirming or not the service to the customer 

WAITLISTED: Airline acknowledges the waitlist request from the Seller and Airline will confirm if service becomes available later 

CONFIRMED: Airline acknowledges and confirms that the service is allocated to the customer.  

CANCELLED: Airline informs that the service is no longer allocated to the customer 

TRANSFERRED: When an OrderItem is modified and some of its services must be retained, Original OrderItem will have OrderItem status cancelled and within this item the retained services will have a service status transferred. The new OrderItem will contain the transferred service with service status confirmed and potentially other services as explained in the Concept document: Change / Modification of an Order.

Other References