Services · GDS, NDC & airline
Multi-GDS integration with rules for every overlap
Connecting a second or third GDS doubles your content and your problems: the same flight appears twice at different prices, one system is slow, and staff must remember which GDS issues for which airline. Voraal's multi-GDS integration searches Amadeus, Sabre and Travelport in parallel and settles each overlap by rule.
Built for
- Consolidators with two or more GDS contracts
- Wholesale agencies
- OTAs comparing GDS fares
- Businesses with fares filed to different systems
In brief
What is multi-GDS integration?
Multi-GDS integration connects one booking platform to more than one GDS at the same time and decides, by rule, which source to search, which duplicate to show, what to do when one system fails and which GDS issues the ticket. Voraal does this across Amadeus, Sabre and Travelport using the business's own credentials on each, inside Rezencia and through Avunzo.
By the Voraal team · Updated
Why businesses run more than one GDS
Running two GDSs is rarely about content breadth alone. More often, an airline has filed a negotiated fare to an office on one system, a productivity agreement rewards segments on another, and a third gives better coverage in one market. Each reason is commercial, and each means the cheapest-looking result is not always the one the business should sell or ticket on.
Multi-GDS integration is therefore a decision layer as much as a connection layer. Voraal treats each GDS as one source under the same normalised flight model, then applies rules for four questions: where to search, how to merge duplicates, what to do when a source misbehaves, and where to issue. The single-system groundwork is covered in GDS integration; this page is about what changes when there is more than one.
How a multi-GDS search is resolved
- 01
Decide which sources to ask
Search rules can include or exclude a GDS by market, route or agent, so you do not pay the look-to-book cost of asking every system every time.
- 02
Fan out in parallel
Requests go to each selected GDS at once, each with its own time budget.
- 03
Collect within the budget
Results arriving on time are used. A source that times out or errors is logged and skipped, and the search returns what it has.
- 04
Normalise
Every response is mapped to the same itinerary, fare and tax structure so like can be compared with like.
- 05
De-duplicate
Identical journeys are detected and one is kept according to your preference rules, with the alternatives retained internally.
- 06
Book and ticket where the rules say
The PNR is created on the source of the kept fare, and ticketing follows your per-airline routing rule.
De-duplication: deciding which copy of a flight to show
Two results are treated as the same offer only if the journey and the fare match closely enough. When they do, a preference order decides the winner.
| Check | What is compared | Why it matters |
|---|---|---|
| Same journey | Carrier, flight numbers, dates and times for every segment | A different connection is a different product |
| Same booking class | Reservation booking designator per segment | Different classes carry different rules and seat counts |
| Same fare | Fare basis and fare type (published, private, negotiated) | A private fare on one office may undercut a public fare on another |
| Total price | Base fare plus taxes, after your markup | The traveller sees the all-in price |
| Preference rule | Preferred GDS per airline or contract | Keeps segments where your incentives or ticketing authority are |
When journeys match but fares differ, both can be shown as different fares on the same flight, or the lower one kept, depending on your rule.
Key features
Rule-based de-duplication
Merge identical offers by journey, class and fare, with a preference order you control.
Source selection
Choose which GDSs to search per market, route or agent, to control search cost and latency.
Per-source time budgets
Each GDS gets a time limit; slow sources are dropped from that search rather than holding it.
Ticketing routing by airline
The airline on the booking decides which GDS issues, as in dynamic multi-GDS ticketing.
Source visibility
Back-office users see which GDS a fare came from and what was discarded, so pricing disputes can be traced.
Isolation
An error or outage on one GDS does not break bookings on the others.
Single GDS versus multi-GDS, operationally
One GDS
- One office, one set of credentials, one message set
- No duplicates to resolve
- If the GDS is down, flights are down
- Fares filed only to other systems are out of reach
Several GDSs through Voraal
- Several offices managed in one place
- Duplicates merged by your preference rules
- Other sources keep returning results if one fails
- Fares filed to each office are searchable together
Business applications
Consolidator with split contracts
Fares from each GDS reach sub-agents as one list, while tickets go through the GDS each airline deal requires.
Agency chasing GDS incentives
Preference rules keep segments on the system where your segment targets are, unless another GDS is meaningfully cheaper.
OTA in several markets
Each market searches the GDS with the best coverage there, under one storefront. For adding NDC and low-cost sources as well, see airline content aggregation.
Implementation process
- 01
Inventory your contracts
List each GDS office, the fares filed to it and any segment or incentive terms that should affect preference.
- 02
Write the rules
Source selection, de-duplication preference and ticketing routing are configured in Rezencia.
- 03
Test overlaps
Known routes are searched on all systems to check that duplicates merge as intended and the right fare survives.
- 04
Monitor after launch
Response times, timeouts and discarded duplicates are reviewed so the rules can be tuned.
Common challenges
False duplicates
Merging two results that differ in booking class hides a cheaper or more flexible fare. The match must include class and fare basis.
Search cost
Every extra GDS call has a cost and counts toward look-to-book ratios. Search only the sources that can add value on that route.
Wrong-channel tickets
A ticket issued on the wrong GDS usually means a void and reissue. Routing by rule removes the decision from staff.
How Voraal delivers this
The products behind it.
If the same flight comes back from two GDSs, which one do travellers see?
The one your preference rule selects. By default the lower all-in price wins; you can prefer a specific GDS per airline where contracts or incentives make that worthwhile.
What happens when one GDS is slow or down?
Each source has a time budget. Results from the others are returned on time, the failing source is logged, and bookings on the other systems carry on.
Can we restrict a GDS to certain routes or agents?
Yes. Source-selection rules include or exclude a GDS by market, route or agent, which also helps control search costs.
Can the booking be made on one GDS and ticketed on another?
Ticketing normally follows where the PNR is held. Voraal's routing rule decides at booking time which GDS the PNR is created on, so it can be issued where the airline deal requires.
Do we need separate credentials for each GDS?
Yes. Each GDS connection uses its own office credentials under your agreement with that GDS. Voraal manages them together in one platform.
Let’s build what comes next.
Tell us how your travel business works. We’ll recommend the right products and walk you through them on your own use case.