Real GDS Commands, Airline Policy Notes, and Practical Agent Tips
Group bookings are very different from normal individual reservations.
When you’re handling 20, 50, or even 100 passengers, small mistakes can cause major operational issues.
In this guide, I’ll walk you through how to create a Group PNR across the three major GDS systems — Amadeus, Galileo (Travelport), and Sabre — based on real agency workflow.
This is not just command theory — this is what agents actually use in daily operations.
What Is a Group PNR?
A Group PNR (Passenger Name Record) is a reservation created for multiple passengers traveling together under one group name instead of individual passenger names.
Airlines usually require:
- Minimum passenger count (varies by airline)
- Special group inventory
- Different ticketing deadlines
- Manual confirmation process
That’s why the command format differs from standard bookings.
Step 1: Create the Group Name Field
The first step is declaring the booking as a group reservation.
Each GDS uses a different format.
Amadeus
NG80 GROUPNAME
- NG = Name Group
- 80 = number of seats
- GROUPNAME = agency-defined group identifier
Example:
NG80 ALNASSRTEAM
Galileo (Travelport)
N.G/80 GROUPNAME
Example:
N.G/80 ALNASSRTEAM
Sabre
-C/80 GROUPNAME
Example:
-C/80 ALNASSRTEAM
After this step, the system recognizes the PNR as a group booking.
Step 2: Sell the Group Flight Segment
Unlike individual bookings, group segments are usually sold using group status codes such as GK, GL, AK, or LL depending on airline policy.
Let’s assume:
- Flight: SM502
- Class: U
- Date: 22 May
- Route: SHJ to CAI
- Seats: 80
Amadeus
SSSM502U22MAYSHJCAIGK80
- GK = Group confirmed status (subject to airline rules)
⚠ Always check airline group policy before using GK or GL.
Galileo
0SM502U22MAYSHJCAIAK80
Status codes vary per airline agreement.
Sabre
0SM502U22MAYSHJCAILL80
LL is often used for long sell / waitlist in group bookings.
Step 3: Add Mandatory PNR Elements
A valid PNR must contain essential fields before ending the transaction.
These include:
- Phone field
- Received From
- Ticketing field
Add Phone Field
Amadeus
AP 0501234567
Galileo
P.0501234567
Sabre
9 0501234567
Add Received From Field
This is mandatory for audit tracking.
Amadeus
RFGROUP
Galileo
R.GROUP
Sabre
6GROUP
Step 4: Add Ticketing Field
For group bookings, ticketing is often managed offline or given a time limit.
Amadeus
TKOK
Galileo
T.T*
Sabre
7TAW/
Airlines may provide specific ticketing deadlines for group contracts.
Step 5: End and Retrieve the PNR
After entering all required elements:
ER
This saves the PNR and generates the record locator.
The command ER works in all three systems.
Important Operational Notes
From real-world experience:
- Never assume GK works for all airlines.
- Always confirm group inventory before selling large seat blocks.
- Some airlines require OSI or SSR entries for group reference numbers.
- Ticketing deadlines for group PNRs are stricter than individual bookings.
If the airline rejects the segment, you may need to re-sell with updated status.
Common Mistakes Agents Make
- Forgetting Received From field
- Using wrong status code
- Ending transaction without ticketing field
- Not verifying group fare agreement
These mistakes can cause PNR auto-cancellation.
Final Thoughts
Creating a Group PNR across Amadeus, Galileo, and Sabre requires attention to command syntax and airline policy.
While the structure is similar across systems, small command differences can affect the booking outcome.
If you work regularly with group bookings, mastering these entries will save time and prevent costly errors.
Read also :
Issue EMD Services in Amadeus & Galileo
How to Create a PNR in Galileo
