Reservations & ticketing Travel technology glossary

PNRPassenger Name Record

Also called passenger name recordbooking recordrecord locatorbooking reference

Definition

A PNR (passenger name record) is the reservation record that a GDS, airline or other travel supplier creates for a traveller or group. It holds the names, itinerary, contact details, ticketing arrangement and service requests, and is retrieved by a short alphanumeric code called the record locator.

What PNR means

The PNR is the basic unit of work in airline reservations. Every booking made in a GDS or an airline reservation system lives in one, and every later action (pricing, ticketing, a seat request, a schedule change) is recorded against it.

A PNR is not a ticket. It is the reservation: who is travelling, on which flights, and what has been agreed. The e-ticket and any EMDs are separate accounting documents that are linked back to the PNR once payment is taken.

Each PNR is identified by a record locator, typically six alphanumeric characters. When an agency books through a GDS, the airline (the vendor) usually holds its own copy of the booking and can return a separate vendor locator, so one trip may carry two references.

Systems will not save a PNR until certain elements are present. Sabre summarises the minimum as PRINT: phone, received from, itinerary, name and ticketing time limit. Other systems use similar rules under different names. Beyond the mandatory fields, a PNR can carry special service requests (SSRs), other service information (OSI), remarks, frequent flyer numbers, form of payment and secure flight data.

Because the PNR is shared between the agency, the GDS and each airline in the itinerary, it is also the channel through which airlines send schedule changes and ticketing deadlines back to the seller, usually via GDS queues.

How PNR works

A PNR moves through a predictable life cycle from first availability check to final travel.

  1. Sell the segmentsThe agent or booking engine checks availability and sells flight segments in a chosen booking class. The segments sit in a work area until the record is saved.
  2. Add mandatory elementsNames, a contact phone number, a received-from entry and a ticketing arrangement or time limit are added. Without them the system refuses to end the transaction.
  3. Save and generate the locatorEnding the transaction stores the PNR and returns a record locator. The GDS sends booking messages to each airline, which may reply with its own locator.
  4. Price and ticketThe fare is stored, then an e-ticket is issued and its number is written into the PNR. Ancillary services may be paid with EMDs that are also linked to the record.
  5. Service after bookingChanges, schedule-change notices, seat requests and refunds are all handled against the same PNR, often prompted by queue messages from airlines.
  6. Travel and purgeAfter the last segment is flown, the record is eventually archived or purged according to each system's retention rules.

PNR in practice

The layout below is illustrative only. It is not a real booking and each GDS formats its display differently.

ElementIllustrative content
Record locatorX7KQ2M
Name1.1RAHMAN/AYESHA MS
Itinerary1 XX 101 Y 12MAR DOHDXB HK1 (XX is a placeholder airline code)
PhoneDXB 971 4 000 0000 AGENCY
TicketingTKTL 10MAR
Special requestSSR VGML (vegetarian meal)
Received fromRF AYESHA

Once ticketed, the time limit line is replaced by the 13-digit ticket number, and the record now links the reservation to its accounting document.

Who uses it

Travel agenciesAgents create, price, ticket and service bookings through PNRs, and work queue messages that airlines attach to them.
AirlinesAirlines use their copy of the PNR for inventory control, check-in, disruption handling and revenue integrity checks such as duplicate or inactive segments.
Booking engines and OTAsOnline systems create PNRs through GDS or airline APIs and store the record locator so customers can retrieve or change their trip.
Mid and back-office systemsAccounting and reporting tools read PNR data to raise invoices, reconcile tickets and measure agency productivity.

Advantages and limitations

Advantages

  • One shared record lets the agency, GDS and every airline on the itinerary work from the same booking data.
  • Mandatory elements enforce a minimum standard of contact and ticketing information before a booking is held.
  • The record locator gives travellers and staff a short, memorable key for retrieval.
  • A full history of changes supports audits, dispute handling and customer service.

Limitations

  • PNR formats and commands differ between GDSs, so staff and software need system-specific knowledge.
  • Agency and airline copies can fall out of step, for example after a schedule change that has not been actioned.
  • Unticketed or inactive segments left in PNRs can trigger airline penalties and debit memos.
  • PNRs hold personal data, so agencies must manage access and retention under data-protection rules.

Frequently asked questions about PNR

Is a PNR number the same as a ticket number?

No. The PNR's record locator is usually six letters and digits and identifies the reservation. The ticket number has 13 digits, starts with the issuing airline's three-digit code, and identifies the paid accounting document. One PNR can hold several ticket numbers, one per passenger, plus EMD numbers for extras.

Why does my booking have two different reference codes?

When an agency books through a GDS, the GDS creates its own record locator and the airline's reservation system creates another for its copy of the booking. Both point to the same trip. Airline websites and check-in usually need the airline locator, while the agency services the booking with the GDS locator.

What are the mandatory fields in a PNR?

Each system sets its own rules, but the core is consistent. Sabre's developer guide lists PRINT: phone number, received from, itinerary, name and ticketing time limit. Without these the system will not save the booking. Agency and traveller identifiers are also required.

Can a PNR be transferred to another passenger?

Generally not. Airline fare rules usually make bookings and tickets non-transferable, so a name change normally means cancelling and rebooking. Some airlines allow minor spelling corrections under their own policy, so check the carrier's agency guidelines before editing a name field.

Run your agency on one booking platform

ReservationHub's Subscription Cloud Edition gives agencies GDS, NDC and low-cost content, B2B and B2C sales, and back office in one hosted platform.

See the SaaS platform

Sources and further reading

  1. Sabre Dev Studio — Intro to PNRs
  2. Sabre Dev Studio — Glossary
  3. AltexSoft — Record locator
  4. Travelport — Pre-assigned queues
  5. Iberia — What is the ticket number and where can I find it?