To successfully clone PNR records is one of the most useful functions in any GDS. Travel agents use these commands to duplicate itineraries, copy passenger information, and create new bookings faster without re-entering every detail by hand.
This guide covers the exact copy commands for Amadeus, Galileo and Sabre — plus what each command carries over, what it silently drops, and the workflow rules that keep your new record clean.
Quick Answer: Copy Commands at a Glance
🔵 Amadeus
- Full PNR —
RRA - Itinerary only —
RRI - Passenger data —
RRP
🟢 Galileo
- Full PNR —
REALLSALL - Itinerary only —
RESALL - Passenger data —
REALL
🟠 Sabre
- Full PNR —
ICAPD - Itinerary only —
IC/EC - Passenger data —
ICAN P5 P9
What Is a PNR Copy Command?
A PNR copy command tells the host system to read an existing Passenger Name Record and write selected elements into a brand-new record. Depending on which variant you use, you can duplicate:
- The entire PNR — itinerary, passengers, contacts, ticketing arrangements and associated remarks.
- The itinerary only — flight segments and surface or ARNK elements, with no passenger names attached.
- Passenger data only — names, contact details and passenger-type information, with no flights.
The new record always receives its own record locator. The original PNR is never modified by a copy command — which is exactly why cloning is safer than editing an existing booking.
Copy commands only duplicate data. Fares, ticket numbers, EMDs and queue placement are never carried across — those must always be rebuilt in the new PNR.
Copy vs Clone vs Split vs Transfer: Know the Difference
These four terms are often used interchangeably, but they do very different things. Mixing them up is one of the most common causes of duplicate bookings and ticketing exceptions.
| Operation | What Happens | Original PNR | Best Used For |
|---|---|---|---|
| Copy / Clone | Creates a new PNR with duplicated elements | Untouched | Repeat bookings, family and group itineraries |
| Split | Divides one PNR into two or more records | Reduced in size | Passengers travelling separately |
| Transfer | Moves PNR ownership between offices | Changes owner | Inter-agency handover, branch moves |
| Retrieve / Display | Reads a PNR without creating anything | Untouched | Checking details, servicing, reissues |
For dividing records, see our dedicated guide to split PNR commands in Amadeus, Galileo and Sabre. For moving ownership between offices, read how to transfer a PNR in Galileo, Amadeus and Sabre.
Why Travel Agents Use PNR Copy Commands
- Save time — a six-segment multi-city itinerary duplicates in one entry instead of twenty.
- Avoid typing errors — names, dates, flight numbers and fare basis codes are never re-keyed.
- Rebook passengers quickly — rebuild disrupted bookings in seconds after a schedule change.
- Duplicate group and family itineraries — see the cross-GDS group booking guide.
- Reuse passenger information — contacts, passports and frequent flyer numbers stay consistent.
Before you copy anything, it helps to understand the structural differences between hosts. Read our Amadeus vs Sabre vs Galileo comparison.
Amadeus PNR Copy Commands
Amadeus uses a three-command family built around the RR prefix. Each variant copies a different layer of the source PNR.
Amadeus Copy Command Reference
| Function | Command | What It Copies | Reference |
|---|---|---|---|
| Copy entire PNR | RRA |
Itinerary + passenger data | RRA command page |
| Copy itinerary only | RRI |
Flight segments only | RRI command page |
| Copy passenger data only | RRP |
Names and passenger-linked data | RRP command page |
RRA — Copy the Entire PNR
RRA is the full duplication entry. Display the source PNR, then enter RRA to generate a new record containing the same itinerary and passenger structure. Use it when a client repeats the exact same trip, or when you need to rebuild a booking that was cancelled by mistake.
RRI — Copy the Itinerary Only
RRI transfers flight segments into a new PNR without carrying over names. You then add fresh passenger names manually. This is the cleanest way to reuse a routing for a completely different traveller, and it avoids re-checking availability for every leg.
If the copied routing includes surface sectors, review how to use ARNK in Amadeus, Sabre and Galileo so the new PNR prices correctly.
RRP — Copy Passenger Data Only
RRP brings passenger names and associated data into a new record without any flight segments. Use it when the itinerary is already built and you simply need the same travellers attached — for example a return trip where the outbound is already booked.
After copying passenger data, you may need to complete these elements:
- Add contact details in Amadeus, Galileo and Sabre
- Add a frequent flyer number
- Add passport data
- Change a passenger name in a PNR
Step-by-Step: Cloning a PNR in Amadeus
- Retrieve the source PNR using the record locator or RT display commands.
- Confirm the PNR is not ticketed, voided or closed. If it is closed, see how to recall a closed PNR in Amadeus.
- Enter
RRA,RRIorRRPdepending on the layer you need. - The system creates a new PNR and displays it automatically.
- Verify every element — segment status, names, contacts, ticketing arrangement.
- Add or remove elements, then save with
ETor ER.
Ticket numbers, EMDs and fare data are not carried over. Seat assignments and SSRs usually need re-entry, and queue placement is not duplicated. Re-price the copied itinerary using the Amadeus FXD guide or browse the full Amadeus commands library.
Galileo PNR Copy Commands
Galileo uses the RE family — short for “receive” — combined with sell-all triggers. The pattern to memorise is simple: RE = receive, SALL = sell all segments.
Galileo Copy Command Reference
| Function | Command | What It Copies |
|---|---|---|
| Copy entire PNR | REALLSALL |
Itinerary + passenger data into a new PNR |
| Copy itinerary only | RESALL |
Flight segments only |
| Copy passenger data only | REALL |
Passenger names and associated data |
REALLSALL — Full PNR Copy
This is the Galileo equivalent of Amadeus RRA. It receives all elements from the source PNR and sells every segment into the new record, producing a complete duplicate. It’s the go-to command for rebuilding a booking identically.
RESALL — Itinerary Copy
RESALL carries the flight segments without passenger data, letting you attach a new traveller to an existing routing. This is the workhorse command for repeat leisure bookings where the route is identical but the passenger is different.
REALL — Passenger Data Copy
REALL receives passenger-level information into the current PNR. Use it when the itinerary already exists and you only need traveller details transferred across.
Step-by-Step: Copying a PNR in Galileo
- Display the source PNR and confirm segment status.
- Note passenger numbers if you plan to copy data selectively.
- Enter
REALLSALL,RESALLorREALL. - Review the new record — Galileo shows any segments that failed to sell.
- Rebuild passenger types if needed using the passenger types in Galileo guide.
- Re-price and save the booking.
Sold-out or schedule-changed segments will not copy silently — always read the response line by line. Fare quote lines are not duplicated, so reprice using the Galileo FS commands. Complex tax structures may need manual rebuilding — see handling more than 20 taxes in Galileo.
For queue filing after a copy, read the Galileo queues guide. For a wider command refresher, see Galileo GDS guide: smart agent secrets.
Sabre PNR Copy Commands
Sabre handles copying differently. The itinerary copy function is built around the IC (itinerary copy) entry, while passenger data uses a separate format with passenger numbers.
Sabre Copy Command Reference
| Function | Command | What It Copies |
|---|---|---|
| Copy entire PNR | ICAPD |
Itinerary + passenger data |
| Copy itinerary only | IC / EC |
Flight segments into the current PNR |
| Copy passenger data only | ICAN P5 P9 |
Passenger data for specified passenger numbers |
ICAPD — Copy Itinerary and Passenger Data
ICAPD duplicates both the itinerary and the passenger data from the displayed PNR, giving you a near-complete clone. This is the fastest route to a full duplicate in Sabre, and the entry most agents use when a client rebooks the identical trip.
IC / EC — Copy Itinerary Only
IC copies itinerary segments from the source PNR into the PNR currently being built. You must have a PNR in progress with names already added. Depending on your host version and configuration, EC may be used as the alternate itinerary-copy entry.
Create the new PNR and add names first, then copy the segments. Copying into an empty PNR with no names will usually fail or produce an orphaned record.
ICAN P5 P9 — Copy Passenger Data Only
The ICAN format copies passenger-associated data for the passenger numbers you specify — in this example, passengers 5 through 9. This is invaluable for group bookings where you only want to move a subset of travellers into a new record.
Step-by-Step: Cloning a PNR in Sabre
- Display the source PNR with
*plus the record locator. - Decide whether you need a full copy, itinerary only, or passenger data only.
- For a full duplicate, enter
ICAPD. - For itinerary only, start a new PNR, add names, then enter
IC. - For passenger data only, enter
ICANwith the relevant passenger numbers. - Verify segments, reprice, then end the transaction.
Fare quotes, ticket numbers and EMD records are never copied. Seat and SSR elements must be re-entered — see the WCHC, WCHR and WCHS guide for mobility requests. Queue placement is independent, so read Sabre queue: a quick guide.
Always verify connecting times after copying — use the MCT quick guide. For a full command library, see the Sabre commands complete reference.
Master Comparison: Copy Commands Across All Three GDSs
| Function | Amadeus | Galileo | Sabre |
|---|---|---|---|
| Copy entire PNR | RRA |
REALLSALL |
ICAPD |
| Copy itinerary only | RRI |
RESALL |
IC / EC |
| Copy passenger data only | RRP |
REALL |
ICAN P5 P9 |
Command availability and exact syntax can vary by GDS version, host configuration, agency profile and market. Always confirm in your training environment before using a copy command on a live booking.
What Copies and What Doesn’t
This is the section most agents wish they had read earlier. Copy commands are not a full backup — several critical elements are always left behind in the source record.
| PNR Element | Usually Copied? | Notes |
|---|---|---|
| Flight segments | Yes | Subject to availability at time of copy |
| Passenger names | Depends on command | Only with a full copy entry |
| Contact details | Often | Verify after copying |
| Fare and pricing | No | Must be re-quoted |
| Ticket numbers | No | Issued separately to the new PNR |
| EMD records | No | Re-issue via the EMD services guide |
| Seat assignments | Rarely | Re-select seats |
| SSRs and OSIs | Sometimes | Always verify |
| Queue placement | No | File manually after saving |
| Frequent flyer numbers | Sometimes | Re-add if missing |
Best Practices for Safe PNR Copying
- Never copy a ticketed PNR into a new booking without a clear reason. Duplicate ticketed records cause accounting exceptions and ADMs.
- Verify segment status immediately. A copied segment may return as waitlisted or unconfirmed.
- Check the dates. Copying an old itinerary often carries expired dates that trigger invalid past-date segment errors.
- Rebuild ticketing arrangements. The new PNR needs its own ticketing time limit.
- Re-add retention segments if the new booking must stay active — see the retention segments guide.
- Watch infant and child associations. Review booking an infant with a seat and passenger association checks.
- Document the source PNR in a remark so future agents understand the booking history.
If you copy itineraries often, keep a personal cheat sheet of the three commands per GDS pinned to your desk. Muscle memory beats searching the help pages mid-booking.
Common Mistakes Agents Make When Cloning PNRs
- Copying into a PNR that already has segments. This creates duplicated or conflicting itineraries that are painful to clean up.
- Assuming fares carry over. They do not — always reprice the new record.
- Forgetting to split before copying a group. Copying an entire group PNR into one record produces a mess. Split first, then copy.
- Ignoring schedule changes. If a segment has changed since the source PNR was created, the copied version may be invalid.
- Not checking the name count. Copying names into a PNR that already has names creates duplicates that must be removed.
- Leaving orphan PNRs. Cancelled copies still consume record locators and clutter queues. Use the correct cancel entries — see XE segment cancellation.
Frequently Asked Questions
Does copying a PNR cancel the original booking?
No. Copy commands are read-and-create operations. The source PNR remains fully intact and untouched. Only split and cancel commands modify the original record.
Can I copy a PNR that has already been ticketed?
Technically yes in most systems, but you should avoid it. Copying a ticketed PNR creates a new unticketed record that can be mistaken for a duplicate sale. If you need to rebook a ticketed passenger, void or refund the original first — see void vs refund in aviation and how to void tickets in Sabre and Galileo.
Why did my copied itinerary show as waitlisted?
Because availability changed between the original booking and the copy. The host sells the segment at the current booking class availability, which may differ from the original. Always check the status code on every segment after copying.
Does the fare carry over when I clone a PNR?
No. Pricing is never duplicated. You must re-run the fare quote and pricing entries in the new PNR. In Amadeus use FXP or FXX; in Galileo use the FS commands; in Sabre use the standard pricing entries.
Can I copy only some passengers from a group PNR?
Yes. In Sabre, the ICAN format lets you specify passenger numbers — for example ICAN P5 P9. In Amadeus and Galileo, the cleaner approach is to split the group PNR first using the split PNR commands, then copy the relevant portion.
Where can I practise these commands safely?
Use your GDS training mode or a dedicated training PCC. Our GDS training hub includes structured lessons, and you can test your knowledge with the Amadeus basics exam or the Amadeus advanced exam.
Final Thoughts
PNR copy commands are the difference between a fifteen-minute booking and a two-minute booking. Learn the three variants in each system — full copy, itinerary only, and passenger data only — and you will handle repeat clients, group rebuilds and disruption recovery far faster than agents who re-key everything by hand.
The golden rule: copy the data, then rebuild the commercial elements. Fares, tickets, seats and queues always need to be re-created in the new record. Treat the copy command as a head start, not a finished booking.
Keep Building Your GDS Skills
Explore more command references, step-by-step tutorials and practice exams on GDS Hub.