Passenger Name Record (PNR)

A Record Locator (also called a PNR Code, a Booking Reference, or a Reservation Code) is a 6-character alphanumeric code assigned to a travel reservation made by a travel advisor or automated booking engine.

For the PNR (Passenger Name Record) to be considered legal and saved in a GDS database, it should include five essential elements:

• Name Element: All of the passengers’ full legal names and titles on the record.
• Itinerary Element: Individual transport elements (flights, rail legs, or hotel attachments) and the status of those elements (e.g., HK for confirmed, HL for waitlisted).
• Contact Information: Passenger’s or travel agency’s telephone or e-mail contact details.
• Ticketing Element: Information about the means and time of issuance of tickets, or the date of expiration (TTL).
• Received-From Element: A field recording the person or application that created or edited the booking (such as an agent ID or API application name).

Aside from required fields, PNRs contain optional elements such as Special Service Requests (SSRs) for dietary preferences or wheelchair assistance, Other Service Information (OSI) notes for crew, and payment method authorization tokens.

PNRs are dynamic, ever-changing files that can be modified during the travel life cycle. Modern travel technology platforms manage PNRs across complex operational workflows:

• Queue management: PNRs are managed in an automated queue mechanism based on operational triggers in GDS networks. If the airline changes the flight time, the system pushes the corresponding PNR to a queue for the airline schedule change, which the agency or portal can use to inform the passenger.
• If a travel agent books a multi-carrier trip, a Super-PNR or Master PNR is produced in the travel agent’s GDS. That GDS then issues Claim PNRs through the API or EDIFACT messages and creates them directly in each operating airline’s native reservation system.
• Mid-office parsing: Live PNR data streams are captured through software tools, and passenger metadata is directly extracted and fed to external Customer Relationship Management (CRM) solutions, corporate expense solutions, and automated invoicing engines.

The legacy Passenger Name Record (PNR) system has been used for decades and has a lot of technical debt. Legacy PNRs use cryptic, mid-20th-century-designed, text-heavy EDIFACT messaging standards that separate the booking record (the PNR) from the financial record (the electronic ticket/e-ticket), and ancillary purchases (EMDs).

The travel industry is transitioning towards IATA’s ONE Order initiative along with NDC (New Distribution Capability):

• Legacy: A complex triad made up of a PNR, electronic ticket, and Electronic Miscellaneous Document (EMD) for add-on.
• Modern: One single, XML/JSON-based Order Record where a modern retail transaction integrates the passenger identity, flight segments, dynamic baggage add-ons, seat assignment, and payment tokens.