Amadeus Commands Cheat Sheet

Before you can search, sell, or ticket anything, you need to sign in and set up your session. These commands cover agent sign-in, creating new agent IDs, and accessing reference data like city and airport codes.

Amadeus returns far more data than fits on a single screen. These commands let you move around the display — scroll down, go back up, jump to the top or bottom, and redisplay a cleared screen. They become muscle memory within your first week.

Every booking starts here. You search available flights on a route and date, then check schedules, flight status, minimum connecting times, and aircraft types before selling a segment. Getting availability right is what separates a fast agent from a slow one.

Once you’ve found flights, you build the Passenger Name Record: add passenger names, sell segments, add contact details, ticketing arrangements, and received-from information. This is the core of daily agency work and the area where small mistakes cost the most time.

Nothing you do in a PNR is saved until you end the transaction — and forgetting to do it is one of the most common beginner mistakes. These commands save, file, or discard your work, and control whether the PNR stays open or drops out of your session.

Special Service Requests (SSRs) and remarks are how you communicate passenger needs to airlines — wheelchair assistance, meal preferences, corporate references, OSI messages. Getting these wrong can mean a passenger is denied boarding, so accuracy matters more here than almost anywhere else in Amadeus.

Loyalty program data matters for earning miles, applying status benefits, and in some cases applying corporate or alliance fares. These commands handle frequent flyer entries, airline agreements, and redemption bookings.

These commands control which offices and agents can access a PNR — essential in multi-branch agencies or when a booking needs to be restricted from general view. Fewer commands, but high-stakes if used incorrectly.

Advance seat requests (ASR) and seat maps let you assign or request specific seats before check-in. Unlike SSRs, these interact directly with airline seat inventory — so a seat request can be confirmed, waitlisted, or refused in real time.

You’ll constantly need to pull up PNRs — by record locator, passenger name, flight, or queue. These commands also cover PNR history, purged records, and claiming PNRs across offices, which matters when bookings move between branches.

Printing PNRs, copying itinerary elements between records, and replicating bookings for group or return trips saves hours of manual re-entry — and reduces the errors that come with it. These are the commands agents reach for once they’re past the beginner stage.

Plans change. These commands let you change flights, cancel segments, delete inactive elements, and update passenger names when corrections are needed. Some overlap with other categories because the same command often serves multiple purposes.

Group bookings work differently from individual PNRs — they use a name list, group fare SSRs, and specific workflows airlines require for group reservations. If your agency handles tours, corporate travel, or sports teams, this section is essential.

Before you can ticket, you need to price the itinerary. These commands display fares, calculate mileage, convert currencies, and store fare information in the PNR. Pricing is where most agents spend the most time — get comfortable with FQD, FXP, and FXX first.

The full ticketing workflow: store a Transitional Stored Ticket (TST), add forms of payment, issue the ticket, and handle reissues and refunds. Errors here are costly — a wrongly issued ticket can mean debit memos and unhappy clients — so learn it thoroughly before working live.

Queues are how agencies track pending work — schedule changes, ticketing deadlines, waitlists, customer requests. If you work in a busy agency, you’ll spend part of every day processing queues. These commands let you view, process, and manage queue items efficiently.