PNR
A reservation record containing passenger and itinerary information. A PNR can represent booking state but is not proof of ticket issuance or payment settlement.
Why it matters
In the flight domain, itinerary, leg, segment, carrier and seller identity are distinct. Flattening them too aggressively mixes schedule, fare, agent and booking rules. The search UI can be simple, but the source model needs enough detail for repricing and handoff.
What does it look like in practice?
The same itinerary can be sold by multiple agents with different fare brands, baggage and booking conditions. Segment schedule and seller/offer identity are different concepts.
Implementation questions
- Which legs and segments form the itinerary?
- Are marketing and operating carriers separated?
- Is agent/provider identity retained?
- Is the source reference available for repricing?
Common mistakes
- Modeling an offer as flight number plus price
- Mixing marketing and operating carriers
- Embedding agent identity into itinerary identity
Where does it appear in the travel stack?
PNR commonly appears across flight layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
Duplicate Property Detection Playbook
Detect the same hotel living under multiple canonical records using name, geo, address and supplier-mapping evidence.
Explore →Travel Payment Ownership: Merchant of Record, Seller of Record and Collect Models
Separate Merchant of Record, Seller of Record, agency collect, hotel collect and pay-at-property models across booking and reconciliation.
Explore →Travel PII and Passenger Data Boundaries
Design safe boundaries for passenger identity, contact, payment and travel-document data across search, booking, logging and provider integrations.
Explore →Canonical Hotel Entity Model
Design a canonical hotel identity layer that maps multiple supplier property records into one traceable entity with provenance and merge history.
Explore →Flight Reprice, Schedule Change, Ticketing and Order State
Separate reprice, schedule change, order, PNR, payment and ticket/document states across the flight-booking lifecycle.
Explore →Hotel Rebrand / Rename Reconciliation Playbook
Preserve canonical hotel identity across name and brand changes while managing aliases, source mappings and downstream invalidation.
Explore →