How e-tickets and hotel vouchers are issued after booking

After a customer pays, a travel booking goes through one more important stage: issuing the documents that let them travel. For flights, the e-ticket issuance process turns a held booking into a paid, confirmed ticket with its own ticket number. For hotels, the booking system turns the supplier's confirmation into a voucher the guest can show at check-in. Both steps depend on supplier data, and both can be delayed or fail, so a good booking platform handles them carefully and keeps the customer informed.

An e-ticket, or electronic ticket, is the airline's record that a passenger has paid for a seat. A hotel voucher is a document confirming a hotel booking and what it includes. This guide explains what happens behind the scenes and how to handle problems. If you are building a travel booking platform, our OTA platform service page explains how we work.

The e-ticket issuance process: why booking and ticketing are separate

In flight bookings, creating a booking and issuing a ticket are usually two distinct actions.

1. The booking reserves seats for named passengers and returns a booking reference, often called a PNR (passenger name record). At this stage, seats are held but usually not yet paid for with the airline.
2. The ticketing step pays for the seats through the supplier and creates electronic tickets. Only then is the booking fully confirmed with the airline.

The two steps are separate for practical reasons:

• Payment can be checked between them. The agency can confirm the customer's payment before committing money to the supplier.
• Held bookings have a deadline. Suppliers usually set a time limit for issuing tickets, after which the held seats may be released.
• Some checks happen at ticketing. Fare rules, price changes or supplier credit limits can cause ticketing to fail even when the booking succeeded.

Your booking platform should treat these as separate states, with a clear status for each: booked, ticketing in progress, ticketed or failed.

Hotels work differently

Hotel suppliers usually confirm the booking in a single step after a price check, often called prebook. There is no separate ticketing stage. Instead, the confirmation response contains the details needed to produce a voucher.

What an e-ticket number means

When ticketing succeeds, the supplier returns an e-ticket number for each passenger, and sometimes for each part of the journey.

• It proves payment. The ticket number shows that the seat has been paid for with the airline.
• It is different from the booking reference. The PNR identifies the booking; the ticket number identifies the paid ticket. Customers and support staff sometimes confuse the two.
• Airlines use it for check-in, changes, refunds and handling problems at the airport.
• Each passenger has their own, even when several travel on one booking.

Your system should store every ticket number with the booking and each passenger, and show both the booking reference and ticket numbers on the confirmation and in the admin panel.

A common mistake and its fix

A common mistake is sending customers a confirmation that shows only the booking reference, labelled as their "ticket number". When the customer contacts the airline or checks in, the reference may not be accepted as proof of a ticket, and your support team gets an urgent call.

The fix is simple: label each number clearly on the confirmation and in the admin panel, such as "Booking reference" and "E-ticket number" for each passenger, and only show e-ticket numbers once ticketing has actually succeeded.

Generating hotel vouchers from supplier data

A hotel voucher is produced by your system from the booking confirmation returned by the hotel supplier.

A clear voucher usually includes:

1. Your booking reference and the supplier's reference, and where available, the hotel's own confirmation number.
2. Guest names as sent in the booking.
3. Hotel name, address and contact details.
4. Check-in and check-out dates.
5. Room type, board type (such as breakfast included) and number of guests.
6. What has been paid and any charges payable at the hotel, such as local taxes.
7. The cancellation policy that applied at the time of booking.
8. Special requests, marked clearly as requests rather than guarantees.

Supplier data varies in quality and format, so map it carefully into your own voucher template. Check that names, dates and room details match exactly what the customer booked.

Sending documents the customer can trust

Customers rely on these documents at airports and hotel desks, often far from home. They should be accurate, consistent and easy to find.

1. Send a confirmation email straight away, stating clearly whether tickets are issued or still being processed.
2. Attach or link the documents in a format that works on phones and can be printed.
3. Use consistent branding and clear language, so the documents look official and trustworthy.
4. Make them available again. Customers should be able to find their documents in their account or a "manage booking" page using their booking reference.
5. Store exactly what was sent, so your support team can see the same documents as the customer.
6. Send updates when something changes, such as a schedule change or a cancellation, with new documents where needed.

Avoid sending an e-ticket style document before tickets are actually issued. A confirmation that says "ticket pending" is honest; a document that looks final but is not can leave a customer stranded.

Handling delayed or failed ticketing

Ticketing does not always succeed on the first attempt, and sometimes the outcome is unclear.

1. Run ticketing as a background task. The customer should see a clear "confirming your booking" message instead of a page that hangs.
2. Watch the ticketing deadline. Store the supplier's time limit and alert your team if a booking approaches it without tickets.
3. Do not repeat ticketing blindly. If a ticketing request times out, check the booking status with the supplier before trying again, to avoid issuing duplicate tickets.
4. Handle clear failures quickly. If ticketing fails because of a price change or a supplier issue, decide whether to rebook, offer alternatives or release the customer's payment.
5. Put unclear cases in an operations queue. Give your team the booking, payment status and supplier logs they need to resolve it.
6. Keep the customer informed. Tell them what is happening and when they will hear from you, and follow up once it is resolved.

Our guide on why travel bookings fail at confirmation covers operations queues and status checks in more detail. For the screens around this step, see our guide on how to design a flight booking flow customers finish, and for the hotel side, our guide to the hotel prebook step.

Summary

• Flight bookings are usually booked first and ticketed later; the e-ticket confirms payment with the airline.
• The booking reference and e-ticket numbers are different, and both should be stored and shown.
• Hotel vouchers are generated from supplier confirmation data and should include references, dates, room details and policies.
• Send clear, honest documents straight away, keep them available and store exactly what was sent.
• Run ticketing in the background, watch deadlines, never repeat it blindly and give your team a queue for problems.

Reliable documents are what customers remember when they travel. If you're building or improving a travel booking platform, you can tell us about it here.