In short
A booking record is the reservation record that stores the details of a trip, including travellers, flights, status, contact details, and servicing history. It is the shared reference point used to understand what was booked, what has changed, and what still needs action before or after travel.
What a booking record contains
A booking record is broader than an itinerary. The itinerary explains the trip sequence, while the record stores the information needed to manage that trip. That can include travellers, flights, status, contact details, payment context, and servicing history.
The exact shape varies by system and channel, but the purpose is consistent. It holds the operational view of the reservation so the parties involved can work from the same facts.
How it differs from a ticket
A ticket confirms the commercial right to travel. A booking record is the live reservation workspace around the trip. A trip may be booked before ticketing, and a ticketed trip may still need further servicing later.
That difference matters because travellers ask practical questions about the whole journey, not only the ticket. Sellers need to know both what has been issued and what remains changeable.
| What the traveller holds | What it proves | Who honours it at the airport |
|---|---|---|
| A reservation | That the trip is held, with travellers and flights recorded | Nobody by itself. It is a working file, not an entitlement |
| A ticket | The commercial right to travel under the attached fare conditions | The operating airline, at check-in and at the gate |
| A paid extra | That money changed hands for a service on this trip | The airline, but only if its own reservation shows the extra |
Why it matters
Booking records are central to servicing. When a flight changes, a traveller updates details, or an option is added, the record is where the current state of the reservation is understood.
For educational purposes, think of it as the trip's working file rather than the ticket itself.
That working file changes over time. A useful seller reads the current state of the reservation, not only the state that existed when the traveller first paid.
What the booking record costs your service desk
Booking records decide whether a post-booking sale is real. A traveller who pays you for a seat or an extra bag expects the airline to honour it at the airport, and that recognition can only come from the reservation the airline itself can see. When an extra is sold but never reflected there, the failure surfaces late, at a check-in desk, where your agent cannot fix it and the traveller wants their money back, as a refund or as a chargeback.
For a commercial leader, that makes the booking record a revenue question rather than an operational detail. Ask any ancillary platform how a sale reaches the reservation, and how you find out when it did not. DepartCart is built to sit on top of whichever system holds the booking, so the answer should not change with your source mix. The integration options vary; the outcome should not.
Frequently asked questions
What is a booking record?
It is the reservation record that stores the traveller, journey, status, and servicing details for a trip.
Is a booking record the same as an itinerary?
No. The itinerary describes the journey, while the booking record stores broader reservation and servicing information.
Why does a booking record matter?
It gives airlines and sellers a shared place to understand what was booked and what has changed.