Tourism Information and Reservation Systems
This domain covers tourism information sources and the reservation systems used to hold and confirm travel. The exam tests PNR, GDS and CRS, booking steps and the difference between a reservation and a ticket.
Information and systems
Tourist information comes from official tourism boards, tourist offices, websites, brochures, maps, guides and reviews. A CRS (computer reservation system) holds inventory for one provider or group; a GDS (global distribution system) connects agencies to many airlines, hotels and car suppliers. Amadeus, Sabre and Travelport are GDS examples.
Reservation basics
A PNR (passenger name record) is a record locator holding passenger, itinerary, contact and ticketing details. It is not a ticket. Booking steps: enquiry, availability, hold, name, payment, ticket or time limit, confirmation. Fare rules govern changes, refunds and baggage.
Worked example
A client has a PNR with two flight segments but no ticket number. Reasoning: the seat is held, not purchased; if the ticket time limit passes, the hold can cancel. The PNR confirms the booking record; the e-ticket confirms payment and the contract of carriage. Do not tell the guest that the ticket is confirmed until the ticket number is issued.
Traps that cost marks
Treating a PNR as a ticket; assuming a GDS is an airline; ignoring fare rules and time limits; and confusing an SSR (special service request) with a confirmed seat.
Key points
- A PNR is a booking record, not a ticket.
- A GDS connects agencies to many suppliers.
- A CRS often holds one provider's inventory.
- Ticket time limits can cancel a hold.
- Fare rules control changes, refunds and baggage.