Cat1 - Eligibility

Category 1 (Eligibility) provides the capability to further define the passenger for whom the fare applies.

Category 1 is a supplement to the Fare Class Application further defining the passenger. If a passenger type codes does not have additional eligibility requirements, then it should be coded in the Fare Class Application only and not repeated in Category 1.

How to Link Eligibility and Security Data

Option 1 uses Category 1 as a qualifying condition to control to who can sell the fare. Coding Category 15 (Sales Restrictions) as a main provision allows the Travelport 360 Fares system to sell the fare to anyone who is eligible to use the fare. Listing the 1V/1G/1P CRS code in the main Category 15 and linking to the qualifying IF Category 1 controls to whom the fare can be sold. Once a passenger is identified in the IF Category 1, then only the CRS/GDS listed in the associated Category 15 portion can sell to the specified passenger.

Option 2 uses Category 1 as a qualifying condition to control to whom can sell the fare. Coding Category 35 (Negotiated Fares) as a main provision allows the Travelport 360 Fares system to sell the fare to anyone who is eligible to use the fare. Unlike Category 15, Category 35 includes a passenger type field. When the information within multiple data tables applies to different passenger type codes, it can be coded within the Category 35 without having to IF to a Category 1. However, if there is a need to indicate that the different data tables within the same sequence are applicable to different account codes or other eligibility information, then an IF Category 1 is needed. Listing the 1V/1G/1P CRS code in the main Category 35 and linking to the qualifying IF Category 1 controls to whom the fare can be sold. Once a passenger is identified in the IF Category 1, then only the CRS/GDS listed in the associated Category 15 portion can sell to the specified passenger.

A Passenger type of Adult “ADT” in Category 1 does not match ALL passenger types; it only matches ADT. Therefore, when Category 35 is filed with an IF to Category 1 for a passenger type and, if applicable, account code and other associated PTCs (i.e. CNN, INF) are also eligible for the fare, the string must contain an OR Category 1 for each passenger type.

An OR CAT01 is needed for all the primary passenger types in Record 1/Record 8/Category 25 and the secondary passenger type found in Categories 19-22 that are eligible for the private fare.

Example

Option 3 uses Category 15 as the qualifying condition to control when the eligibility provision appliers. This option does not apply to Category 35 as Category 35 cannot be used as a qualifying category. This option does not control the passenger type to whom the system can sell the fare. This option is used when the eligibility provisions is dependent upon the sales restriction provision. For example, a Category 1 IF Category 15 would be coded when the account code for a passenger type is dependent upon the GDS selling the fare.