Airline E-ticket Code Generator

Booking code (PNR) vs e-ticket: what each one is

A booking code — also known as PNR (Passenger Name Record), locator, booking reference or confirmation code — is a short 5- to 6-character alphanumeric string generated by the Global Distribution System (GDS) the moment a reservation is created. It identifies the reservation, not the payment. The e-ticket number (13 digits, XXX-NNNNNNNNNN) only exists after the ticket has been issued against a form of payment. Example PNRs in real-world systems: ABC123 (Sabre/Amadeus 6-char style), 4F8XYZ (Galileo), KLM92P. Letters I and O and digits 0/1 are often avoided because they look alike on printed itineraries.

GDS players: Sabre, Amadeus, Travelport

Three Global Distribution Systems dominate the planet:

• Sabre — born inside American Airlines in the early 1960s as Semi-Automated Business Research Environment; today an independent NYSE-listed company strong in the Americas.
• Amadeus — founded in 1987 by Air France, Iberia, Lufthansa and SAS; headquartered in Madrid, dominant in Europe.
• Travelport — operates the Galileo, Worldspan and legacy Apollo systems; popular among US travel agencies.

Since 2014 the IATA NDC (New Distribution Capability) XML standard has been gradually replacing the 1980s EDIFACT messaging of the GDS, letting airlines distribute rich content (seat photos, ancillaries, bundles) directly to agencies and OTAs (Decolar, Expedia, Booking, Kayak).

Booking lifecycle: from search to boarding

A typical funnel: shopper search → fare quote → PNR created (locator returned) → option/hold in some fares (PNR reserved for 24h without payment) → payment → e-ticket issued (TKTT message) → check-in (24-48h before departure) → boarding pass with BCBP bar code. The PNR can later be split into sub-PNRs for multi-passenger groups, and on code-share flights the PNR may live in a GDS belonging to a different carrier than the one operating the aircraft. PNRs accumulate a forensic trail (IP, geolocation, payment instrument, agency office ID) regularly used in anti-fraud and law-enforcement investigations.

Legitimate uses of mock booking codes

Mock PNRs are useful for: building travel-app prototypes with realistic itinerary screens; running automated tests against GDS sandbox endpoints (Sabre Dev Studio, Amadeus for Developers, Travelport Universal API); seeding staging databases for OTAs; demonstrating self-service portals to call-centre trainees; classroom exercises in tourism and aviation management courses. Always label mock data clearly as test data so it is not mistaken for an actual reservation by analysts or back-office staff.

FAQ

Does the PNR ever change? The 5/6-character code itself is permanent for the reservation, but the underlying flights, dates and passenger data can be updated by the airline (irregular operations, schedule changes, name corrections).

Can I look up my booking with just the PNR? Most airlines allow Manage My Booking with PNR + passenger surname; some require the e-ticket number for full changes.

I lost my PNR — can I recover it? Yes. Contact the issuing airline or agency with the passenger name, route and approximate date; they can locate the PNR in the GDS.

Are these codes real bookings? No. They follow the visual alphanumeric pattern of a PNR but are not registered in Sabre, Amadeus or Travelport. Use them for travel-app prototypes, sandbox tests against GDS APIs, UX research and classroom demos — never to claim or modify a real reservation, which is a fraud offence.