Skip to content
Voraal

Guide · Air aggregation

Integrating multiple airline suppliers without breaking search

Adding a second or third airline source rarely fails on connectivity. It fails on what happens next: the same flight appearing three times at three prices, fare families that do not line up, and tickets issued through the wrong channel. This guide covers the design decisions that make multi-supplier air content work.

Built for

  • Consolidators
  • OTAs
  • Corporate booking tools
  • Agencies with in-house developers
  • Travel startups

Short answer

How do you integrate multiple airline suppliers?

Integrate multiple airline suppliers by calling each source in parallel within a fixed time budget, normalising fares, baggage and brands into one model, de-duplicating identical flights with clear rules, ranking by total cost to the traveller, routing booking and ticketing to the source that sold the fare, and reconciling each source separately. Voraal's Rezencia and Avunzo aggregate GDS, NDC and LCC content this way.

By the Voraal team · Updated · 7 min read

Why integrate more than one airline source?

Because no single channel carries every fare. GDSs remain broad, some airlines publish certain fares and bundles through NDC, and many low-cost carriers sell mainly through their own APIs or websites. Each additional source can lower the price on some routes, add a carrier, or bring a richer product.

The cost is complexity. This guide does not repeat the channel comparison in GDS vs NDC; it assumes you have decided to combine sources and explains how to do it without degrading search speed or booking accuracy.

What is the right sequence for adding airline suppliers?

  1. 01

    Start with your primary GDS

    Get one source fully working, including ticketing, voids, refunds and schedule changes. It becomes the reference for everything else.

  2. 02

    Add sources by route value

    List your top routes and carriers by revenue. Add the NDC or LCC source that changes price or availability on those routes first.

  3. 03

    Define the common model

    Before connecting the second source, agree the internal representation of segments, fares, brands, baggage, ancillaries and rules.

  4. 04

    Write de-duplication rules

    Decide how the same flight from two sources is detected and which one wins. Document the rule so sales and support can explain results.

  5. 05

    Route servicing by source

    Store the source on every booking, and send changes, refunds and voids to that source. Never assume one channel can service another's booking.

  6. 06

    Reconcile per source

    Each source has its own settlement: BSP for GDS tickets, airline statements or BSP for NDC, card or deposit for LCCs. Reconcile them separately before combining.

How should parallel searches be timed?

Set a total time budget for search and give each source a timeout within it. Results that arrive inside the budget are shown; late sources are either dropped or streamed in as they arrive.

The budget is a commercial choice. A longer wait may surface a cheaper fare from a slow source, but travellers and agents abandon slow pages. Measure per-source response times on your real routes and set timeouts from data, not defaults. Cache low-volatility results, such as schedules and fare families, more aggressively than live prices.

How do you decide which duplicate fare to show?

When the same flight and cabin appear from more than one source, apply rules in a fixed order.

Rule (in order)What it checksWhy it matters
1. IdentitySame marketing carrier, flight numbers, dates and booking class or brandConfirms the results are truly the same product
2. Product contentBaggage, change and refund conditions, seat and meal inclusionsA cheaper fare with no bag is not the same offer
3. Total cost to travellerFare plus taxes plus mandatory fees in the selling currencyPrevents a low base fare hiding high fees
4. Your net cost and marginNet fare, commission, override and channel feesTwo equal selling prices may earn different margins
5. Ticketing and servicing abilityWhether you can ticket, void and refund on that sourceA fare you cannot service is a support risk
6. Source reliabilityRecent booking failure and price-change ratesAvoids routing traffic to an unstable connection

Some businesses show duplicates as separate fare options when the product content differs. Others collapse them. Either way, apply the same rule every time.

How do you normalise fares from different channels?

Map every source into one internal fare model with explicit fields, rather than passing raw supplier text to the screen.

Baggage is the most common gap: one source returns a piece allowance, another a weight, another only a fare-family name. Brands and fare families also differ, so build a mapping table per carrier and source that translates them into consistent labels such as light, standard and flexible, while keeping the airline's own name visible. Fare rules should be stored in full, with key conditions extracted for display. Tools that read fare rules automatically help, but keep the original text available for agents.

Worked example: one route, three sources

Consider a Karachi to Dubai search on a date with good availability. A carrier's flight appears through the GDS at a published fare with a checked bag, through that carrier's NDC connection at a slightly lower price in a light brand without a bag, and a separate low-cost carrier appears only through its own API. The engine recognises that the first two are the same flight but different products, so it shows them as two fare options under one flight, labelled by baggage. The low-cost option is a different carrier and is ranked on total cost including the bag the traveller selected. Booking routes to whichever source the traveller chose, and the booking record stores that source for later servicing. This is illustrative; actual content depends on each carrier's distribution policy.

What operational issues appear after launch?

  • Content parity drift

    A carrier changes what it sells through each channel. Monitor price differences by source on top routes so you notice when a source stops being competitive.

  • Credential and quota limits

    Sources may limit searches or bookings per credential. Track usage per source and adjust caching before you hit throttling.

  • Schedule changes

    Each source notifies schedule changes differently. Normalise them into one queue so agents act on them in time.

  • Payment differences

    GDS tickets often settle through BSP, while some LCC and NDC bookings need card or deposit payment at booking. Fund and reconcile each correctly.

  • Support knowledge

    Agents and support staff need to know which source a booking came from and what that means for changes. Show it plainly on the booking.

How do you measure whether each source is earning its place?

Review these per source every month. A source that looks good on price but fails on servicing can cost more than it saves.

MetricWhat it tells youAction if it worsens
Share of results that win the rankingHow often the source has the best offerCheck fare content and markups on that source
Price-change rate at re-pricingHow stale or volatile its search prices areShorten cache time or re-price earlier
Booking failure rateConnection or data-quality problemsRaise with the supplier; reduce traffic if needed
Average response timeImpact on your search time budgetAdjust timeout or move to streamed results
Servicing effort per bookingStaff time for changes, refunds and disputesPrice the effort into fees or limit products
Margin per bookingCommercial value after fees and overridesRenegotiate or reduce priority in ranking

Do ticketing deadlines differ by source?

Yes, and the difference catches many teams. GDS bookings usually carry a ticketing time limit set by the airline, after which an unticketed booking may be cancelled. Many NDC and low-cost carrier bookings are paid and confirmed immediately, with no hold period at all, or with a short paid hold.

Your checkout and queues must reflect this. A booking flow that lets an agent hold every option for a day works for some GDS fares and fails for an instant-purchase carrier. Store the deadline type and time on each booking, route expiring holds to a queue, and show agents clearly which options can be held and which must be paid now.

How Voraal fits

Voraal aggregates Amadeus, Sabre and Travelport GDS content, NDC airlines and low-cost carriers into one flight model, available in Rezencia for agencies and in Avunzo as an API. Rule-based ticketing selects the right channel, and the dynamic multi-GDS ticketing case study shows the routing logic, while unified flight search covers result merging. Service details are on the airline content aggregation, multi-GDS integration and low-cost carrier integration pages.

Key takeaways

  • Make one source work end to end before adding the next
  • Add sources in order of the revenue they affect
  • Define the internal fare model before connecting the second source
  • Write and document fixed de-duplication rules
  • Set search timeouts from measured response times
  • Book, ticket and service on the source that priced the fare
  • Reconcile each source on its own settlement before combining

FAQ

Frequently asked questions

Questions buyers ask about how to integrate multiple airline suppliers.

Ask us anything
  • Can the same booking be ticketed through a different GDS than the one that priced it?

    Sometimes, but it needs care. Moving a booking between systems can change availability and price. Most businesses ticket on the source that priced the fare unless a ticketing rule deliberately routes it elsewhere for commercial reasons.

  • How many airline sources does an agency actually need?

    Enough to cover the carriers and routes that make up most of its revenue. For many agencies that is one GDS plus a handful of NDC and LCC connections, not every possible source.

  • Why does the same flight show different baggage from different sources?

    Airlines may distribute different fare families or brands through different channels. A fare without a checked bag through one channel and with a bag through another are different products, even on the same flight.

  • What should happen when one airline source is down?

    Search should continue with the remaining sources and hide or flag the missing content. Alert operations so they know the outage is affecting results.

  • Is it worth integrating low-cost carriers if margins are small?

    Often yes, because travellers expect to see them and their absence makes your search look incomplete. Service fees and ancillary sales can make LCC bookings worthwhile even when commission is low.

  • Should one supplier be marked as preferred when prices are equal?

    Yes. When total cost and product are identical, a documented preference based on margin, servicing ability or reliability keeps results stable and stops ranking from flipping between sources on every search.

Sources and further reading

Regulations, airline programmes and supplier terms change. Confirm requirements with the relevant authority or supplier before acting. Contact [email protected] if you spot something out of date.

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.

WhatsApp