Group bookings are different from individual reservations.
When handling large passenger numbers (20–100+), even small mistakes can cause major operational issues.This guide explains how to create a Group PNR in the three main GDS systems:
Amadeus, Travelport Galileo, and Sabre GDS.
Amadeus Group PNR Commands
| Step | Command | Description |
|---|---|---|
| Create Group | NG80 GROUPNAME | Define group PNR (80 passengers) |
| Sell Segment | SS SM502U22MAYSHJCAIGK80 | Sell group seats (GK status) |
| Add Fare Note | SRGRPF-FARE 100AED | Add group fare as a remark |
| Phone | AP 0501234567 | Contact number |
| Received From | RFGROUP | Mandatory field |
| Ticketing | TKOK | Ticketing instruction |
| End PNR | ER | Save booking |
Galileo (Travelport) Group Commands
| Step | Command | Description |
|---|---|---|
| Create Group | N.G/80 GROUPNAME | Define group booking |
| Sell Segment | 0SM502U22MAYSHJCAIAK80 | Sell seats for group |
| Phone | P.0501234567 | Contact number |
| Received From | R.GROUP | Mandatory field |
| Ticketing | T.T* | Ticketing instruction |
| End PNR | ER | Save booking |
Sabre Group Commands
| Step | Command | Description |
|---|---|---|
| Create Group | -C/80 GROUPNAME | Define group PNR |
| Sell Segment | 0SM502U22MAYSHJCAILL80 | Sell group seats |
| Phone | 9 0501234567 | Contact number |
| Received From | 6GROUP | Mandatory field |
| Ticketing | 7TAW/ | Ticketing deadline |
| End PNR | ER | Save booking |
Important Operational Notes
- Group status codes (GK / AK / LL) depend on airline rules
- Always verify group inventory before selling seats
- Missing Received From may cause PNR rejection
- Group ticketing deadlines are stricter than individual bookings
- Some airlines require SSR/OSI for group reference handling
Common Mistakes to Avoid
- Using incorrect group status codes
- Forgetting mandatory fields (RF, phone, ticketing)
- Ending PNR before completing ticketing logic
- Not checking airline group contract rules
Issue EMD Services in Amadeus & Galileo
