Home โ€บ Blog โ€บ Amadeus FXR Command: Lowest Fare, No TST Stored

Amadeus FXR Command: Lowest Fare, No TST Stored

A complete guide to the FXR command in Amadeus โ€” how to price the itinerary at the lowest possible fare and rebook automatically when required, without storing a TST.

Sometimes you want to see how much lower the fare could be if the itinerary were rebooked in a cheaper class โ€” but without committing to any change. The FXR command is designed for exactly this situation. It searches for the lowest available fare for the itinerary and automatically rebooks the segments if a lower booking class is required, but unlike FXB, it does not create or store a TST. This makes FXR a safe way to check lower-fare options and preview the effect of a possible rebooking before deciding whether to proceed. This guide explains what FXR does, the syntax, and when it should be used.

What Does the FXR Command Do?

FXR is the Amadeus GDS command used to price the itinerary with the lowest possible fare, rebook the itinerary when required, but without storing a TST.

Category: Informative Pricing.

The FXR command searches for the lowest available fare and automatically rebooks the itinerary if a lower booking class is required. Unlike FXB, it does not create or store a TST.

This combination โ€” rebooking but no TST โ€” makes FXR a preview tool. You see the effect of the rebooking and the fare that would result, but nothing is committed to the ticket record. If you then decide to proceed, a confirmed pricing command stores the TST.

Syntax & Examples

Price the complete itinerary at the lowest possible fare, rebook if necessary, and do not store a TST:

FXR

Price a specific segment at the lowest possible fare:

FXR/S3

This prices segment 3 at the lowest possible fare, without affecting the rest of the itinerary.

Price a specific passenger at the lowest possible fare:

FXR/P2

This prices passenger 2 at the lowest possible fare, which is useful in multi-passenger PNRs where individual travellers may need different fare treatment.

When to Use FXR

Use FXR when you want to find the lowest possible fare and rebook the itinerary without creating a TST. It is useful for checking lower-fare options before storing the final pricing. Typical scenarios include:

  • Previewing the effect of a rebooking before committing to a change.
  • Checking whether a lower fare is available in a different booking class.
  • Quoting a lower price to a customer who may want to change their booking.
  • Testing alternative booking classes without affecting the stored pricing.
  • Comparing fares between the current booking and the lowest available option.
  • Optimising a booking where the customer has not yet confirmed the change.
  • Supporting a reissue or exchange where the new fare needs to be checked first.

How FXR Fits Into Your Pricing Workflow

A typical pricing session using FXR might look like this:

  • Retrieve the PNR and confirm the itinerary is complete.
  • Enter FXR to search for the lowest fare and preview the rebooking if necessary.
  • Use FXR/S3 or FXR/P2 for segment or passenger-specific checks.
  • Review the result โ€” the PNR may now show new booking classes and the new pricing.
  • Confirm with the customer that the rebooking is acceptable.
  • Run FXB or FXP to store the TST.
  • Review the TST with TQT and issue with TTP once everything is confirmed.

How FXR Relates to Other Pricing Commands

  • FXR โ†’ lowest-fare pricing with automatic rebooking, but no TST stored.
  • FXB โ†’ lowest-fare pricing with automatic rebooking and TST storage.
  • FXP โ†’ standard pricing of the itinerary as booked, with TST storage.
  • FXX โ†’ prices the itinerary without storing a TST and without rebooking.
  • FXA โ†’ lists lower applicable fares without rebooking or pricing.
  • FXL โ†’ displays the lowest possible fare regardless of availability.
  • FXE / FXF โ†’ informative pricing for the ATC reissue process.
  • FXO / FXQ โ†’ confirmed pricing with TST creation for ATC reissue.

The key distinctions: FXR rebooks but does not store, FXB rebooks and stores, FXP stores without rebooking, and FXX does neither.

Important: FXR rebooks the itinerary when a lower booking class is available, even though it does not store the TST. This means the booking class on one or more segments may change after running FXR. Confirm with the customer that the change is acceptable before proceeding.

If you want to store the new pricing after the FXR preview, run a confirmed pricing command such as FXB or FXP.

Frequently Asked Questions

What does FXR do in Amadeus?

FXR prices the itinerary at the lowest possible fare, rebooks it automatically if a lower booking class is available, but does not create or store a TST.

Does FXR store a TST?

No. Unlike FXB, FXR does not create or store a TST. If you want to commit the pricing, use FXB or FXP afterwards.

What is the difference between FXR and FXB?

Both search for the lowest fare and rebook if necessary. FXB stores the TST; FXR does not.

Can I use FXR on a specific segment or passenger?

Yes. Use FXR/S3 for a specific segment or FXR/P2 for a specific passenger.

Conclusion

The FXR command is the preview tool for lowest-fare pricing in Amadeus. Use FXR to search for the cheapest available fare and rebook the itinerary automatically if a lower booking class is required, without creating or storing a TST, or use FXR/S3 and FXR/P2 to limit the check to a segment or passenger. It is ideal for quoting lower fares, verifying the effect of a rebooking, and testing alternatives before committing. Because FXR may change booking classes, always review the PNR after the command and confirm the change is acceptable to the customer. When you are ready to store the pricing, switch to FXB or FXP. Paired with FXX, FXA, TQT, and TTP, the FXR command completes your pricing toolkit and helps you offer the most competitive fare without committing prematurely.