Split Order Flow
This flow demonstrates the end-to-end process for performing a Split Order (traditionally known as a Split PNR) operation. The Split Order function allows customers or agents to separate one or more passengers from an existing booking into a new order (or PNR), enabling independent management of itineraries, ticketing, payments, or modifications.
The sample below outlines all required API interactions, including order retrieval, passenger selection, split request submission, and confirmation of the newly created order, ensuring both the original and split orders are correctly updated and linked.
Flow Process
- 1.
OrderRetrieveRQ (Parent) - Retrieve the full state of the original Order before any split decision is made.
- 2.
OrderChangeRQ (Split the Order) - To split the Order. After split the OrderViewRS has both child and parent in the response.
- 3.
OrderRetrieveRQ (Parent & Child) - You’ll need to call OrderRetrieve separately for each Order ID to display them individually.
XML Samples
File
Download
Created
Modified
31-October-2025
31-October-2025
31-October-2025
31-October-2025
31-October-2025
31-October-2025
31-October-2025
31-October-2025
31-October-2025
31-October-2025
31-October-2025
31-October-2025
Inputs/Outputs
OrderRetrieve
Request
-
OrderID or Booking Reference - The order to be split
Response
-
OrderID or Booking Reference
-
Passenger details
-
Flight segment details
-
Flight segment details
-
Total order price and breakdown
-
Seat and baggage details
OrderChange
Request
-
OrderID — the order to be split
-
PassengerRefID(s) — the passengers to move to a new order
Response
-
OriginalOrderID — the updated original order
-
NewOrderID — the newly created split order
-
Passenger and ticket mapping
-
Confirmation of status for both orders
A paid or unpaid order can be split by moving passengers into a new order. The following rules apply:
- The order must contain more than one ADT passenger
- Any associated INF passenger must move with their parent ADT passenger into the new order
- Young Adult and Child passengers cannot be moved to a new order without being accompanied by an ADT passenger
- At least one ADT passenger must remain in the original order
- Orders containing flown segments cannot be split
How to Implement Split Order
The following Augmentation Point needs to be added to the OrderChangeRQ. This will split selected passengers from the original order to the new order.
Click on the XML Samples above for the full Split Order sample
Element
Details
DataType
M/O/C
Splits selected passengers from the original order into a new order.
O
List of passengers to be moved into the child order.
List [1..8]
M
Reference to the passenger ID in the original order.
Alphanumeric
M
<AugmentationPoint>
<ChangeOrderChoice>
<UpdatePax>
<PaxSharingPref>
<PaxRefID>ADULT_2</PaxRefID>
</PaxSharingPref>
</UpdatePax>
</ChangeOrderChoice>
</AugmentationPoint>
<AugmentationPoint>
<ChangeOrderChoice>
<UpdatePax>
<PaxSharingPref>
<PaxRefID>ADULT_2</PaxRefID>
</PaxSharingPref>
</UpdatePax>
</ChangeOrderChoice>
</AugmentationPoint>
<DistributionChain>
<DistributionChainLink xmlns="http://www.iata.org/IATA/2015/EASD/00/IATA_OffersAndOrdersCommonTypes">
<Ordinal>1</Ordinal>
<OrgRole>Seller</OrgRole>
<ParticipatingOrg>
<Name>Test Agent</Name>
<OrgID>12345678</OrgID>
</ParticipatingOrg>
</DistributionChainLink>
<DistributionChainLink xmlns="http://www.iata.org/IATA/2015/EASD/00/IATA_OffersAndOrdersCommonTypes">
<Ordinal>2</Ordinal>
<OrgRole>Carrier</OrgRole>
<ParticipatingOrg>
<Name>VIRGIN ATLANTIC</Name>
<OrgID>VS</OrgID>
</ParticipatingOrg>
</DistributionChainLink>
</DistributionChain>
<Request>
<BookingRef xmlns="http://www.iata.org/IATA/2015/EASD/00/IATA_OffersAndOrdersCommonTypes">
<BookingID>TQKIAF</BookingID>
</BookingRef>
<Order xmlns="http://www.iata.org/IATA/2015/EASD/00/IATA_OffersAndOrdersCommonTypes">
<OrderID>VS932TQKIAF25</OrderID>
<OwnerCode>VS</OwnerCode>
</Order>
</Request>
