Skip to content
Voraal

Services · GDS, NDC & airline

Aggregating airline content so every channel is comparable

Airline content is now split three ways: fares through GDSs, offers through NDC, and bundles from low-cost carriers' own systems. Selling from only one channel means missing fares; selling from all three without a plan means confusing results. Voraal's content aggregation brings the channels together and makes the results comparable for agents and travellers.

Built for

  • OTAs
  • Consolidators
  • B2B platforms
  • Corporate booking tools
  • Fintech and super-apps adding flights

In brief

What is airline content aggregation?

Airline content aggregation combines flight content from different distribution channels, typically GDSs, airline NDC connections and low-cost carrier APIs, into one search and one result list. Good aggregation normalises fares, bundles and inclusions so they can be compared fairly. Voraal aggregates GDS, NDC and LCC content in Rezencia for agents and in Avunzo for teams building their own front end.

By the Voraal team · Updated

The fragmentation problem

For a long time, a single GDS connection was close to complete airline content for most agencies. That is no longer true. Some airlines put their richest fares and bundles into NDC; some charge extra for bookings made through legacy GDS connections; many low-cost carriers never filed into a GDS at all. The same city pair can have its cheapest fare in one channel and its most flexible fare in another.

Airline content aggregation is the answer at platform level: ask every relevant channel, convert the answers into one shape, and present them so a traveller or agent can choose. The difficulty is not the fan-out; it is the comparison. A GDS fare with a checked bag, an NDC bundle with a seat, and an LCC base fare with nothing included are three different products that look like three prices.

GDS, NDC and LCC content compared

Each channel has a different shape of data. Aggregation has to respect the differences, not erase them.

CharacteristicGDSNDCLow-cost carrier API
Who pricesGDS from filed faresAirline, per requestAirline, per request
Typical recordPNR and e-ticketAirline orderAirline booking
Bundles and ancillariesBranded fares where filed; extras via EMDBuilt into offersSold as add-ons at booking
Coverage per connectionMany airlines through one contractOne airline per connection, or via aggregatorOne airline per connection
SettlementOften through BSPOften through BSP or direct, by airlineUsually direct
HoldingUntil ticketing time limitPer offer and payment time limitsRarely possible

These are typical patterns. Each airline sets its own policies for every channel.

How Voraal aggregates and presents content

  1. 01

    Select channels per search

    Rules decide which GDS, NDC and LCC sources are asked for a given market, route and customer type.

  2. 02

    Collect in parallel

    All sources are queried at once, each within a time budget, as described in unified flight search.

  3. 03

    Normalise inclusions

    Bags, seat selection, changeability and refundability are mapped to common attributes, whatever the source called them.

  4. 04

    Apply pricing

    Your markups, fees and commissions are applied consistently across channels, so channel does not distort the comparison.

  5. 05

    Rank and display

    Results are sorted and labelled with their inclusions. Duplicates are resolved by rule.

  6. 06

    Book through the source

    The chosen option is booked back through the channel it came from, inside one booking flow.

Key features

  • Common attribute model

    Bags, seats, change and refund conditions expressed the same way for every channel.

  • Channel rules

    Choose which channels serve which markets, routes or customer types, and in what order.

  • Transparent display

    Inclusions are shown on each result, so a base fare is not mistaken for a full-service fare.

  • Channel-neutral pricing

    One markup rule set across GDS, NDC and LCC content, managed in flight fare management.

  • Channel reporting

    See bookings and margin by channel in Folio6, to judge where each channel earns its cost.

  • One API

    Avunzo returns aggregated content through one schema, so developers integrate once.

Business applications

  • Consumer storefronts

    Show travellers a complete choice with clear inclusions, built on Avunzo or the flight booking API.

  • B2B distribution

    Sub-agents see every channel in one list, priced with the consolidator's rules.

  • Corporate travel

    Policy compares fares fairly when a bag or a change is part of the requirement.

Implementation process

  1. 01

    Map your routes to channels

    List the routes and airlines that make your revenue and which channel serves each best.

  2. 02

    Connect the sources

    GDS offices, NDC airlines and LCC accounts are connected under your agreements.

  3. 03

    Agree the display

    Decide default sorting, how bundles are labelled, and whether to show one fare or several per flight.

  4. 04

    Review with real searches

    Compare aggregated results against manual checks on key routes before launch.

Common challenges

  • Apples and oranges

    Sorting by price alone favours bare fares. Display inclusions, or offer sorting by total trip cost with bags.

  • Slowest source sets the pace

    Without time budgets, one slow channel delays every search. Budgets keep results timely.

  • Channel costs

    Every channel has a cost: GDS fees, airline surcharges on some GDS bookings, LCC payment fees. Measure margin per channel, not per booking alone.

FAQ

Frequently asked questions

Questions buyers ask about airline content aggregation.

Ask us anything
  • Why not just use one GDS for all airline content?

    Because some fares and bundles are only available through NDC or directly from low-cost carriers, and some airlines price GDS bookings differently. A single channel can leave cheaper or richer options unsold.

  • How are bundles from different channels compared?

    Each result's inclusions, such as bags, seat choice and changeability, are mapped to common attributes and shown on the result, so travellers compare what they actually get.

  • Does aggregation make searches slower?

    Not if each source has a time budget. Sources answering in time are shown; slow ones are skipped for that search and logged.

  • Can we turn a channel off for one market?

    Yes. Channel rules decide which sources serve which markets, routes and customer types.

  • Is aggregated content available by API?

    Yes. Avunzo returns GDS, NDC and LCC content in one schema for teams building their own front end.

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