What Happens After a Flight Is Booked?

After a flight is booked, the booking enters a servicing lifecycle. First it must be ticketed before its ticketing time limit, or the seat can be released. Once ticketed, four kinds of event can reach it. The customer can ask for a change. The airline can change the schedule. The booking can be cancelled, with or without a refund. And small requests keep arriving: seats, bags, name fixes and travel documents. Each event follows the fare rules and the airline's policy, never the seller's preference. For a travel agency, the hard part is rarely the rules themselves. The hard part is applying them across GDS, NDC and low-cost bookings that each notify and process changes in their own way.

Definitions.

• PNR: the passenger name record a GDS or airline system creates when a booking is made. It holds the itinerary, passenger names, contact details and the ticketing time limit. See GDS.
• Order: the NDC equivalent of a PNR and its ticket. An NDC order holds the offer the customer accepted and is changed through order-change messages. See NDC.
• Ticketing time limit: the deadline by which a held booking must be ticketed. After it passes, the airline can cancel the reservation and release the seat.
• Fare rules: the conditions filed with a fare, including change fees, cancellation penalties and refund eligibility. The fare basis code identifies which rule set applies to a ticket.
• Void: cancelling a ticket on the same sales day it was issued, usually with no penalty. After the void window closes, changes and cancellations follow the fare rules.
• Reissue and revalidation: a reissue replaces a ticket with a new one when the itinerary or fare changes. A revalidation updates an existing ticket for a minor change, such as a new flight number, without issuing a new ticket.
• Involuntary change: any change the airline makes to a booked flight, such as a new departure time, a new flight number or a cancellation.
• ADM (agency debit memo): a charge an airline raises against an agency when it finds a ticketing or servicing error, such as a wrong fare or a waiver that was never authorised.

TL;DR

• Confirmation is not ticketing. A held booking has a ticketing time limit, and missing it can release the seat.
• Customer changes follow the fare rules of the ticket: a change fee, a fare difference, or no change allowed.
• Airline schedule changes follow the airline's policy. The airline sets the rebooking options and fee waivers, and the agency executes them.
• Refund eligibility depends on the fare basis and on who cancelled. A voluntary cancellation and an airline cancellation on the same ticket can end very differently.
• Servicing work grows with every content source an agency runs separately, because GDS, NDC and low-cost sources each notify and process changes differently.
• altovo (formerly easyGDS), a travel commerce platform, lets an agency team search, filter and manage all bookings from a single screen in one agent portal.

What happens between booking confirmation and ticketing?

A confirmation creates a PNR or, on NDC, an order. The seat and the fare are held. No ticket has been issued yet.

Every held booking carries a ticketing time limit. The fare, the airline and the source set it. Some limits run for days. Others expire within hours of booking, especially close to departure or on promotional fares. If the booking is not ticketed in time, the airline can cancel it and release the seat.

Low-cost carriers often work differently again. Many take payment and issue the booking in a single step, so there is no hold to track. The trade-off is that payment is taken at once, and any later change follows the carrier's own terms.

A missed time limit is a quiet failure. Nothing errors on screen. The booking simply lapses, and the agency finds out when the customer asks for the e-ticket. Agencies that run several sources track a different time-limit logic per source, and that is where most of these misses happen.

How do customer-requested changes work after ticketing?

Once a ticket is issued, any change the customer asks for is checked against the fare rules of that ticket. Three questions decide the outcome. Does the fare allow changes at all? Is there a change fee? Is there a fare difference between the old fare and the new one?

Basic and promotional fares often allow no changes, or only for a fee close to the ticket price. Flexible fares usually allow changes for the fare difference alone. The agency cannot override any of this. Waiving a fee the fare does not waive is a common cause of an ADM later.

Name corrections are a special case. Most airlines allow a minor spelling fix under their own policy and treat a change of person as a new booking. Policies vary by carrier, so the safe habit is to check the airline's rule before touching the name field.

The void window sits before all of this. A ticket voided on the day it was issued is usually reversed with no penalty. Once that window closes, the same cancellation falls under the fare rules. Agencies that catch customer mistakes on the day of issue save their customers real money.

What happens when the airline changes the schedule?

An airline schedule change is an involuntary change. The airline retimes a flight, changes a flight number, swaps the aircraft or cancels the flight outright. The fare rules of the ticket stop being the main reference. The airline's own schedule-change policy takes over.

The airline's policy decides three things. First, whether the change is significant enough to give the passenger rebooking or refund rights. Second, which alternative flights are offered. Third, whether change fees and fare differences are waived.

The agency's role is execution. Someone has to spot the notification and contact the customer. Someone has to confirm whether the new timing works, then reissue or revalidate the ticket under the airline's waiver. Connections need checking too. A retimed first leg can break a connection the customer never mentions.

Notification format is where the work splits by source. A GDS booking usually shows the change as a status update in the PNR, often placed on a queue. An NDC booking receives an order-change notification. A low-cost booking may only show the change in the carrier's own portal or in an email to the passenger. Missing one of these messages is one of the most common service failures in flight retailing.

When does a cancelled flight mean a refund?

A cancellation does not produce a refund on its own. Two things decide the outcome: who cancelled, and the fare basis of the ticket.

When the customer cancels voluntarily, the fare rules apply. A refundable fare returns the fare minus any penalty. A non-refundable fare may return only some taxes and fees. Some fares return nothing at all.

When the airline cancels, or makes a significant schedule change, the rules shift in the customer's favour. In many markets a passenger who declines the alternative is entitled to a refund of the unused ticket, whatever the fare type. Passenger rights rules such as EU261 in the European Union and UK261 in the United Kingdom add duties of care and, in some cases, compensation on top. In the United States, the Department of Transportation refund rule sets when a cancelled or significantly changed flight must be refunded.

Refunds also take time. A void cancels the sale before settlement. A refund moves through the airline and the settlement system, and the customer may wait weeks to see the money.

Getting the voluntary or involuntary label wrong is a common source of disputed refunds. Process an involuntary case as voluntary and the customer loses money. Process a voluntary case as involuntary and the airline may raise an ADM.

Why do more content sources make servicing harder?

The rules in the table come from airlines and stay the same whatever technology an agency uses. What technology changes is how much of the work an agency absorbs by hand. Each separate source adds one more place to watch for schedule changes and one more time-limit logic. Each also adds one more refund process and one more workflow to train.

The comparison of GDS, NDC aggregators, consolidators and flight APIs covers who settles and services the ticket in each sourcing model.

How should an agency build a servicing routine?

A servicing routine can start before any new software arrives. A few habits, run every day, prevent most of the expensive mistakes.

• Check time limits daily. List every unticketed booking with its deadline, across every source. Ticket or release each one before the limit.
• Work schedule-change queues first. Involuntary changes have the shortest response windows and the highest customer impact.
• Read the fare rule before quoting a change. Quote the change fee plus the fare difference. Never waive what the fare does not waive.
• Label every cancellation. Record whether it is voluntary or involuntary before the refund is processed.
• Keep one record per booking. Note who changed what and when, so a disputed refund can be answered from one place.
• Use the void window. Review the day's tickets before the sales day closes.

What this means for a travel agency or OTA

Servicing is where customers judge an agency. A fast booking earns a sale. A fast, correct answer after a schedule change earns the next one.

Servicing is also a cost that agencies underestimate until volume grows. An agency running GDS, NDC and low-cost bookings through three interfaces trains staff three times. Staff watch three sets of notifications and rebuild three audit trails when a refund is disputed. None of that shows on the booking itself. The cost shows up in response times, in missed schedule-change windows and in staff hours spent after the sale.

For an OTA, the same problem arrives at scale. Volume turns every manual step into a queue. A process one agent handles from memory has to become a rule in the system once thousands of bookings are live.

When you evaluate a technology provider, ask how changes, cancellations and refunds work for each content source. Ask who receives the notifications, and in what form. Booking capability is only half of the decision.

Where altovo fits

altovo is a travel commerce platform. For travel agencies, it puts GDS, NDC and low-cost content behind one search, with 650+ airlines bookable, including NDC. In the agent portal, teams can search, filter and manage all bookings across the team from a single screen, and cancel and amend without contacting suppliers. See altovo for travel agents and the inventory behind it.

Recent releases, listed on what's new, add servicing detail. Bookings show the airline's own booking reference next to the booking-system reference. A booking activity log records who changed what, when, how and from where. Cancellation fees no longer include the agent's own markup, and long-pending cancellations escalate to operations automatically. Every plan includes 24/7 ticket support. Self-serve travel agent accounts can be live in under 10 days, from sign-up to live bookings.

Talk to altovo

Frequently asked questions