What is a GDS and how does it affect corporate travel?
A Global Distribution System (GDS) is a technology intermediary that aggregates airline, hotel, and car rental content and sells access to that inventory to travel management companies (TMCs) and corporate booking tools. GDS platforms like Sabre, Amadeus, and Travelport were established on EDIFACT messaging standards developed in 1960–1980. For corporate travel programs, GDS dependence means higher costs, limited content, inconsistent servicing, and less visibility into traveler data.
How does a GDS work?
A GDS acts as a clearinghouse between travel suppliers (airlines, hotels, car rental companies) and the TMCs and corporate booking tools that need access to their inventory. Airlines load their fares and availability into the GDS and partner systems, and in exchange, the GDS distributes that content to thousands of connected buyers, taking a per-segment fee for every booking made through its system.
As airlines built direct distribution capabilities under the NDC (New Distribution Capability) standard and proprietary APIs (Application Programming Interfaces), the intermediary model introduced costs and content constraints that aren't present in direct connections — including richer content, dynamic pricing, and ancillaries that EDIFACT, the GDS messaging protocol, was not designed to carry.
What are three ways GDS architecture affects corporate travel programs?
1. Cost
GDS fees are baked into every air booking. Airlines and hotels pay the GDS to distribute their content; that cost is recovered through higher fares, room rates and fees. TMCs and corporate booking tools receive incentives from GDSs which can influence how travel options are displayed. They also pass along additional GDS transaction fees, typically $5–15 or more per booking. Enterprise buyers absorb it, often without seeing it itemized.
2. Content limitations
Airlines have invested heavily in NDC to offer better fares and richer products directly to buyers. Major GDS platforms have begun distributing NDC content alongside their traditional EDIFACT feeds, so NDC availability through a GDS is not zero. But EDIFACT, the protocol that has powered GDS distribution since the 1980s, was never designed to carry the structured data NDC requires. When NDC content is forced through EDIFACT pipes, the translation is lossy: bundled fare families get stripped, ancillaries drop off, and dynamic pricing reverts to static fare buckets.
The deeper problem emerges when a booking originates in one format and gets serviced in another. A traveler who books an NDC offer through a GDS-connected tool may find that their seat selection, baggage, or upgrade doesn't survive a modification, because the servicing layer was built for EDIFACT records, not NDC orders. This fragmentation isn't just a content problem. It creates downstream failures in expense capture, reconciliation, and duty of care that compound through the life of the trip.
3. Servicing friction
When a booking originates in the GDS and a traveler needs to change or cancel, the modification often must flow back through the same GDS channel it was booked in. This creates servicing restrictions, delays, and data mismatches, particularly when travelers book in one channel and service in another.
How does Blockskye addresses this?
Blockskye is NDC-first, using GDS only when a supplier has not yet offered a direct connection. Rather than routing all bookings through GDS rails, Blockskye connects directly to airlines and hotels using NDC and API-based supplier connections that deliver consumer-platform fares, full ancillary access, and real-time content not always accessible through GDS-connected tools. Every booking, regardless of channel, is written to an immutable ledger, eliminating the PNR fragmentation common in GDS-based servicing. The result means enterprise travel programs get better fares, richer content, and cleaner data.
Frequently asked questions
Is GDS going away in corporate travel?
GDS platforms still distribute a significant share of global airline inventory, and many TMCs and corporate booking tools remain reliant on them. It’s a high-cost channel to distribute and access content and the broader shift is that direct and NDC-connected bookings are growing as a share of total volume as airlines expand direct distribution. Programs that haven't added NDC or direct connections may find their content options narrowing over time.
What is the difference between a GDS and an OBT?
A GDS (Global Distribution System) is the backend content aggregator that holds airline inventory and pricing. An OBT (Online Booking Tool) is the front-end interface that business travelers use to search and book. Most OBTs source their content from GDS platforms, though modern OBTs like KAYAK for Business can also connect directly to airlines via NDC, giving corporate travelers access to a broader range of fares and ancillaries.
How does NDC compare to GDS?
GDS platforms distribute both EDIFACT and NDC content, so the distinction isn't simply GDS versus NDC. The difference is in how that content is handled. EDIFACT remains the primary content type across most GDS connections, and its structural limitations mean that NDC offers passing through a GDS may lose bundled fare data, ancillaries, or dynamic pricing in translation. TMCs that have built direct NDC connections, bypassing the EDIFACT layer entirely, can access that content in its complete form. The practical gap shows up most clearly in ancillary display, fare accuracy, and post-booking servicing.
Do all TMCs use the GDS?
All TMCs have some GDS connectivity, and many legacy programs are built primarily around it. The difference lies in how much direct and NDC connectivity a TMC has built alongside it. Blockskye is built NDC-first, using GDS only as a fallback for content not yet available through direct channels.
Can a company's travel program be GDS-free?
Not entirely, yet. Some airlines and hotels still publish content exclusively through GDS channels, making it a necessary fallback for full inventory coverage. A GDS-minimal approach, using NDC and direct connections wherever possible, and falling back to GDS only when no direct channel is available, is the current best practice for modern corporate travel management. This is how Blockskye operates: maximizing direct content while retaining full coverage.
Related terms
EDIFACT
Content Fragmentation
Supplier Direct Content
PNR (Passenger Name Record)
Travel Infrastructure
