Connecting a Legacy Reservation System to Modern Records

What they had

The corporate travel team used a global distribution system, or GDS — the command-line reservation system that still powers most airline, hotel, and car bookings behind the scenes. Agents typed short codes to build itineraries, check availability, and issue tickets. It was fast once you knew it, but every booking started from scratch.

Client details — passport numbers, visa status, frequent flyer numbers, meal and seat preferences — lived in paper files, spreadsheets, or the agent's memory. Agents had to look these up manually and retype them into the GDS for every trip. The same information was entered again and again.

What broke

The process was slow and error-prone. Retyping passport numbers or frequent flyer codes led to typos. Visa requirements changed, and the team had no easy way to know which client needed what. New agents spent weeks memorizing client quirks. Experienced agents carried most of the knowledge in their heads.

The GDS itself was not the problem. It was reliable and fast. The problem was the gap between the GDS and the client information the agents needed to use it.

Why the old system is still there

GDS interfaces are still command-based because the travel industry runs on speed and precision. A trained agent can build a complex itinerary in seconds with short commands. A graphical interface adds clicks, load times, and abstraction layers that slow down high-volume booking environments. The command line also keeps agents close to the raw data, which matters when a single typo can strand a traveler or invalidate a ticket.

The industry has layered modern tools on top of the GDS, but the core reservation engine remains text-based. Replacing it would mean retraining thousands of agents, rebuilding integrations with hundreds of airlines, and accepting slower workflows in a business measured in seconds.

What we chose

I worked with IT to build a Microsoft Access travel document database. The database stored each corporate client's key details in one place: passport, visa, frequent flyer numbers, seating and meal preferences, and special requirements. Agents could open a client record, copy the relevant codes, and paste them directly into the GDS.

It was not a full integration. It was a practical bridge between a modern record-keeping tool and a legacy reservation system that was not going anywhere.

The database covered:

Passport and visa records. Quick access to document numbers and expiry dates for international bookings.
Frequent flyer numbers. Airline loyalty programs stored by client and carrier.
Preferences and special requests. Seat, meal, accessibility, and billing notes.
Corporate client profiles. Contact details, approval contacts, and travel policy notes.

My role

I led this as the corporate travel team manager. I defined what information the agents needed at the point of booking, designed the database tables and forms with IT, tested the workflow with the team, and trained the agents on how to use it alongside the reservation system.

Outcome