Low Fare Shopping: One-Way Component Shop (NZ and AU)

Low Fare Shopping

One-Way Component Shop allows the client to offer each travel direction separately. One-way, stand-alone air prices are returned for each origin to destination (O and D) in a Low Fare Shopping or Asynchronous Low Fare Shopping Air Price Points request. Each fare that is returned can be ticketed by itself or shown separately if it is ticketed with another fare, allowing each O and D option to be displayed independently.

One-Way Component Shop is available for specifically provisioned customers on Galileo (1G) and Airline Content Hub (ACH), and only for a Low Fare Shopping request having travel within or between Australia and New Zealand.

The Apollo (1V), and Worldspan (1P) providers do not support One-Way Component Shop.

Schema

See the following transactions for One-Way Component Shop:

Request

The One-Way Component Shop functionality applies to itineraries with no more than four O and Ds, when the request is for Air Price Points.

The Air Pricing and Air Booking services support this functionality.

Ensure your application is provisioned by Travelport to allow the One-Way Component Shop functionality. After being provisioned, Low Fare Shopping requests are identified by a credential that allows the function. The combination of the customer credentials and the locations of the origins and destinations in the request determine whether Universal API displays each origin and destination option independently in the response.
Request One-Way Component Shop functionality in LowFareSearchReq or LowFareSearchAsynchReq (v49.0 and earlier):

Set the request to return Air Price Points:

@SolutionResult=”false”
@PreferCompleteItinerary=”false”

Set the request to return One-Way Component Shop.

AirPricingModifiers @OneWayShop=“true”

Universal API validates that all locations are within the geography and maximum number of segments permitted for One-Way Component Shop, and Low Fare Shopping requests are sent to Galileo (1G), Apollo (1V), and Airline Content Hub (ACH), as applicable.

Note: The Galileo request adds four preset preference modifiers based on market requirements. The preset modifiers are: Airline, Booking Code, Cabin, and Penalty Tolerance. If the customer includes any one of these preset modifiers, it creates a conflict, and the modifier sent by the customer is ignored. See Warning and Errors below.

Filter the results by carrier:
- Enter carrier in AirSearchModifiers/ @PermittedCarriers or SearchAirLeg/AirLegModifiers/ @PermittedCarriers to include only the specified carriers.
- Enter carriers in AirSearchModifiers/ @ProhibitedCarriers or SearchAirLeg/AirLegModifiers/ @ProhibitedCarriers to exclude the specified carriers.

See Search Modifier by Carrier and Alliance for details.

Note: ACH does not support airline filter options at the leg level (AirLegModfiers). If entered, they are ignored, and a warning message is returned: ACH carriers do not support AirLegModifiers.

See Warnings and Errors in the Response section for a full list.

Response

A Low Fare Shopping response (LowFareSearchRsp or LowFareSearchAsynchRsp (v49.0 and earlier)) that contains price points for the one-way fares is returned.

Warnings and Errors

Errors and warnings may be returned for One-Way Component Shop.

Error Text	Reason/Action
User not authorized for OneWayShop	OneWayShop=”true” but the customer is not provisioned for One Way Shop. The Low Fare Shopping (LFS) request fails.
OneWayShop cannot be used with PreferCompleteItinerary=”true”	OneWayShop=”true” and PreferCompleteItinerary=”true” or PreferCompleteItinerary is omitted. The LFS request fails.
A location is invalid for OneWayShop	OneWayShop=”true” and any one (or more) origin or destination is outside the geography permitted for this function. The LFS request fails.
OneWayShop allows a maximum of 4 origins and destinations.	OneWayShop=”true” and there are more than four origins and destinations. The LFS request fails.
OneWayShop and FlexSearch cannot be used together.	OneWayShop=”true” and the request is also for FlexSearch. The LFS request fails.
A requested provider does not support One Way Shop.	OneWayShop=”true” and a provider does not support One Way Shop. The LFS request fails.
Modifiers for Cabin, Booking Code and Penalty cannot be used with One Way Shop.	OneWayShop=”true” and one of these preference modifiers was included; Booking Code, Cabin, Penalty Tolerance. The LFS request is processed. If found, options with available flights/fares are returned.
AirSearchModifiers/PreferredCarriers cannot be used with One Way Shop. or AirLegModifiers/PreferredCarriers cannot be used with One Way Shop.	@PreferredCarriers is not supported in the request. The LFS request is processed, but the modifier is ignored in the request. If found, options with available flights/fares are returned. Note: Galileo (1G) supports PreferredCarriers, but not in the One-Way Component Shop request.
Preferred Carrier Code not supported. All results returned.	@PreferredCarriers is not supported in the request. The LFS request is processed, but the modifier is ignored in the request. If found, options with available flights/fares are returned. Note: Airline Content Hub (ACH) does not support PreferredCarriers.
Not all of the One Way searches returned results.	The provider returned NO AVAILABILITY FOR THIS REQUEST REQUEST or UNABLE TO FARE QUOTE for the shopping request. The LFS request is processed. If found, options with available flights/fares are returned.
OneWayShop must be requested with SolutionResult=”false”	OneWayShop=”true” and SolutionResult="true" or SolutionResult is omitted. The LFS request fails.
No fare/flight options are returned for your request	No results were returned. This can occur when a city pair has no air service, such as PERBUY.

Air Pricing and Air Booking

Travelport recommends sending multiple individual Air Pricing requests when the itinerary to be priced is the result of a One-Way Component Shop request.

A pricing request should be sent for each O and D and for each journey variation based on the airlines and markets being priced. For example, in the Australia/New Zealand implementation, to determine which combination returns the lowest price, you would send:

One pricing request for each individual origin to destination.
One pricing request that includes all portions of a journey with travel on the same carrier.
One pricing request that includes all portions of a journey with travel on combinable carriers.

There are no changes to the Air Booking process, however, requests may differ based on the selected price options.

If the selected options from the Pricing response contain two or more stand-alone prices and all options are from Galileo:
Send AirCreateReservationReq with the first flight/fare option.
Use Universal Record Modify, which references the Locator Codes from AirCreateReservationRsp, to add subsequent flight/fare data.
If the selected options from the Pricing response contain two or more stand-alone prices and at least one price is from ACH:
Send AirCreateReservationReq with the first flight/fare option.
Send a subsequent AirCreateReservationReq for each subsequent flight/fare option. The Universal Record Locator Code must be included so that the additional flight/fare options can be added to the same Universal Record.
If the selected option from the Pricing response contains one price for the entire journey:
Send AirCreateReservationReq with all flight/fare data.

There is no change to the Air Booking (AirCreateReservationReq) or Universal Record Modify (UniversalRecordModifyReq) requests, but it should be noted that the data needed does differ based on the provider of the flight/fare options. For example, an Air Booking request that uses a flight/fare from the ACH provider requires a Host Token, which a flight/fare from the 1G provider does not.

Low Fare Shopping: One-Way Component Shop (NZ and AU)