Manual Fare Adjustments

The Galileo (1G), Apollo (1V), and Worldspan (1P) providers have functionality that allows increases or decreases to be applied to a fare quote when the appropriate parameters are set in Shop/Price/Book requests. The fare can be increased or decreased either by percentage or flat amount. The user can increase or decrease either the base amount or total. Total amount has some restrictions.

Request

ManualFareAdjustment is an element in AirPricingModifiers that is used to provide increments or discounts to a fare using a percentage or amount. For details on other modifiers, see Air Pricing Modifiers.

1. You can manually adjust a fare using any of the following requests:
   1. Low Fare Shopping
   2. Air Pricing
   3. Air Booking
   4. Universal Record Modify for AirAdd
2. Use the attributes in Manual Fare Adjustment to adjust a fare:

   Show schema diagram

   

   • @AppliedOn: The pricing component upon which the manual fare adjustment is applied. The supported values are Base and Total. Other is available, but currently request processing logic is not available for a value of Other.

     • The only applicable option is "Base" for Worldspan (1P).

   • @AdjustmentType: The process used for applying the increment or discount. The supported values are Amount or Percentage.
   • @Value: The value of increment/discount to be applied. A negative value is a discount and a positive value is an increment.
     • In Galileo (1G) or Apollo (1V), if a value is entered, it is a price increase. In Worldspan , if a value is entered, it is a price discount.
     • For best practices, put a + or a - in front of the numeric value to indicate whether it is an increase or decrease.
   • @PassengerRef: The type of passenger to which the increment or discount is associated. This is for Apollo and Galileo only.
   • @TicketDesignator: This is custom discount pricing for the amount or percentage increase/decrease.
     • Amount Decrease format: Dollar Amount deducted from base fares and followed by amount value.
     • Amount Increase format: Dollar Amount added to base fare and followed by amount value.
   • @FareType:This is the Fare Type Code. For example, enter the Excursion Fare as "EX".

 Notes: 

• @Ticket Designator and @FareType are Worldspan (1P) only.
• Both TicketDesignator (custom discount details like the amount/percentage increase or decrease) and FareType (like the excursion fare "EX") must be sent together to apply custom discount pricing.
• Branded fares do not show discounts or ticket designators when using custom discount pricing.

Supported ManualFareAdjustment Attribute Combinations

Universal API supports any of the following ManualFareAdjustment attribute combinations in a request.

Note: Worldspan (1P) can only use @AppliedOn=Base.

Permitted Attribute Combination	@AppliedOn=	@Adjustment=	@Value=
Base, Percentage, Positive Value	“Base”	“Percentage”	“Positive value”
Base, Percentage, Negative Value	“Base”	“Percentage”	“Negative value”
Base, Amount, Positive Value	“Base”	“Amount”	“Positive value”
Base, Amount, Negative Value	“Base”	“Amount”	“Negative value”
Total, Amount, Positive Value	“Total”	“Amount”	“Positive value”
Total, Amount, Negative Value	“Total”	“Amount”	“Negative value”
Total, Percentage, Positive Value	“Total”	“Percentage”	“Positive value”
Total, Percentage, Negative Value	“Total”	“Percentage”	“Negative value”

Show code snippet

The following code snippet decreases the base price of a fare on a Low Fare Search response by an amount of two dollars.

Response

Galileo and Apollo consider a Passenger Type Code (PTC) with a manual fare discount as “unique” PTC. For example: “ADT PTC with 5% manual discount” and “ADT PTC with 10% manual discount” are considered two different PTCs.

Universal API accepts a PTC with a manual fare discount that is associated either to a specific AirPricingInfo or the first instance of AirPricingInfo in the request. However, in the response, Universal API associates the PTC/manual fare adjustment to the corresponding AirPricingInfo of the traveler to which it is associated.

For Universal Record Import, the response does not return the modifiers, but does return multiple AirPricingInfo elements with the same passenger type where the differentiating factor is the total or base price. The response is similar to the Air Book Request: 10% Increase and 5% Increase in the Customer Examples section.

Manual Fare Adjustments display in the following responses:

• Low Fare Shopping (LowFareSearchRsp and LowFareSearchAsynchRsp (v49.0 and earlier))
• Air Pricing (AirPriceRsp)
• Air Booking (AirCreateReservationRsp)
• Universal Record Modify for AirAdd (UniversalRecordModifyRsp)
• Universal Record Retrieve (UniversalRecordRetrieveRsp)
• Universal Record Import (UniversalRecordImportRsp)
• Universal Record History (URHistory)

Exceptions