A practical guide for travel agents on fixing the *NO FARES/RBD/CARRIER/PASSENGER TYPE error in Amadeus โ why pricing fails and how to reprice with FXR or FXB.
The *NO FARES/RBD/CARRIER/PASSENGER TYPE error is one of the most common Amadeus pricing errors, and it is also one of the most misunderstood. The message does not point to a single problem โ it points to four possible ones, and the system returns the same error whichever of them is missing or invalid. Amadeus simply cannot match a fare because one or more required elements do not line up: the route, the booking class, the carrier, or the passenger type. This article breaks down each cause, explains how to identify which one is blocking your pricing, and shows you the correct commands to reprice the itinerary and clear the error.
What the Error Means
This error appears when Amadeus is unable to match pricing because one or more required elements are missing or not valid:
- No available fare for the route or date.
- Booking class (RBD) is not valid for pricing.
- Carrier is not included in the fare rule.
- Passenger type (ADT / CHD / INF) is missing or incorrect.
Cause 1: No Available Fare for the Route or Date
The fare database has no published fare for the exact combination of cities, travel dates, and carriers in your itinerary. This often happens with seasonal routes, new city pairs, or dates outside the fareโs validity period.
Cause 2: Booking Class (RBD) Is Not Valid for Pricing
The booking class (RBD) stored in the segment does not match any fare that can be priced for that route. For example, the segment may be booked in a class that exists for availability but not for the fare the system is trying to apply.
Cause 3: Carrier Is Not Included in the Fare Rule
One of the airlines in the itinerary is not covered by the fare rule you are trying to apply. This is common with interline itineraries, codeshare flights, and mixed-carrier routings where only some carriers participate in the fare.
Cause 4: Passenger Type (PTC) Is Missing or Incorrect
The passenger type code (ADT, CHD, INF) in the PNR does not match any valid fare, or it has been entered incorrectly. A child priced as an adult โ or an infant with no type code โ will trigger the same error.
How to Fix It
Reprice the itinerary using one of the following commands:
FXRor:
FXBFXR uses the lowest available fare and applies the best matching fare for the itinerary.
FXB prices the itinerary using the fares already stored in the TST or the fare basis you have specified, without searching for new fares.
If the Error Persists
If FXR and FXB both fail, work through the four causes one at a time:
- Verify the travel dates are inside the fareโs validity period.
- Check the RBD of each segment and confirm it is a bookable class for the fare.
- Confirm every carrier in the routing participates in the fare rule.
- Verify the PTC (ADT / CHD / INF) matches the passengers in the PNR.
Quick Fix Checklist
- Confirm the error message reads
*NO FARES/RBD/CARRIER/PASSENGER TYPE. - Reprice the itinerary using
FXR. - If that fails, try
FXB. - Check the travel dates against the fare validity period.
- Verify the RBD on every segment.
- Confirm all carriers participate in the fare.
- Verify the passenger type code (ADT / CHD / INF).
Frequently Asked Questions
What does *NO FARES/RBD/CARRIER/PASSENGER TYPE mean?
It means Amadeus cannot match a fare because one or more required elements โ fare, booking class (RBD), carrier, or passenger type โ is missing or invalid.
Which commands should I use to fix it?
Reprice the itinerary with FXR or FXB. FXR searches for the best available fare; FXB prices using the stored fare basis.
Why does the same error appear for different problems?
Because Amadeus returns one combined message for all four possible causes. You must check each element โ fare, RBD, carrier, and PTC โ to find the one blocking your pricing.
Conclusion
The *NO FARES/RBD/CARRIER/PASSENGER TYPE error is a catch-all message for four different pricing problems. The first response should always be to reprice with FXR or FXB, which resolves the majority of cases by refreshing the fare search. If the error persists, work through the four causes systematically: check that a fare exists for the route and date, that the RBD is valid for pricing, that every carrier participates in the fare rule, and that the passenger type (ADT / CHD / INF) matches the travellers in the PNR. Identifying the correct cause takes a minute and prevents repeated failed pricing attempts.
