Short answer: most low cost carriers historically avoided GDS distribution because per-booking distribution fees are large relative to their low base fares. Their inventory sits in their own reservation systems and is reached through their websites, direct APIs for selected partners, or specialist aggregators. Integrating it means handling ancillary-heavy pricing, instant payment and servicing without a classic PNR/ticket model.
Why LCCs sit outside the GDS
The LCC business model minimises cost per seat, and classic GDS distribution charges the airline a fee per booking segment. On a long-haul business fare that fee is noise; on a short-haul fare it can be a meaningful percentage of the ticket. So carriers like Ryanair, easyJet, and their many peers built their retail around their own websites and apps, keeping inventory in their own reservation platforms, commonly hosted systems such as Navitaire (owned by Amadeus) or Radixx. AltexSoft's overview of low-cost distribution describes exactly this economics-driven split: direct channels first, selective everything else.
The picture is not absolute. Some LCCs do file limited content in GDSs, often aimed at corporate agencies, and hybrid carriers sit in between. But as a rule of thumb, if you only have a GDS integration, you are blind to a large slice of short-haul supply, which is precisely why mixed-content search exists as a product category.
The three access paths to LCC content
Direct connect means an agreement with the airline itself and an integration against its API. It gives the freshest availability and full ancillary access, but each carrier is a separate negotiation, a separate contract, and a separate integration to maintain.
Aggregators such as Travelfusion (which aggregates a large portfolio of LCC and hybrid carriers through one direct-connect platform), Mystifly, Kiwi.com or regional consolidators like TBO wrap many carriers behind one API and one commercial agreement. You trade some freshness and a per-booking cost for enormous breadth and one integration.
Selective GDS filing covers carriers that have chosen to appear in GDS channels, sometimes as ticketless entries with restricted servicing.
Direct connect vs aggregator
| Factor | Direct connect | LCC aggregator |
|---|---|---|
| Coverage | One carrier per integration | Dozens to hundreds of carriers behind one API |
| Commercials | Your own agreement with the airline; terms vary widely | One contract with the aggregator; per-booking or markup pricing |
| Data freshness | Best available; you talk to the source | Good, but adds a hop; some content is scraped or cached depending on provider and carrier |
| Ancillaries | Full depth the airline exposes | Depends on provider mapping; commonly bags, seats, sometimes meals |
| Payment | Airline-defined: your card, customer card or agency wallet | Often the aggregator handles the merchant relationship |
| Maintenance | You absorb every airline-side API change | The aggregator absorbs carrier churn for you |
Most agencies and startups begin with an aggregator, then add direct connects for the two or three carriers that dominate their traffic. That is also the pattern we recommend in flight API integration projects: breadth first, depth where volume justifies it.
Ancillary-heavy pricing
An LCC price is a starting point, not a total. The base fare buys a seat and little else; bags, seat selection, priority boarding, meals, even airport check-in are priced separately. For your platform this has three consequences:
- Comparability breaks. A bare LCC fare next to a full-service fare with a bag included is not a like-for-like comparison. Serious platforms compare a defined bundle (for example, fare plus one cabin bag) or clearly label what each price includes, a problem shared with branded fares on full-service carriers.
- The booking flow grows. Ancillary selection is part of purchase, not an afterthought, so your UI needs paid-extras steps and your API layer must price them live; ancillary prices change like fares do.
- Margin often lives in extras. The carriers themselves earn a substantial share of revenue from ancillaries, and an agency reselling LCC content without ancillary support both degrades the customer experience and gives away revenue.
Practical integration differences
Compared with a classic GDS flow, expect these differences in build and operations:
- No hold, instant purchase: most LCC bookings are pay-at-booking, ticketless, with no unticketed PNR stage or time limit to manage
- Different confirmation model: you get the carrier's own booking reference rather than a GDS record locator and a 13-digit ticket number; reconciliation logic must not assume tickets exist
- Payment complexity: card acceptance, surcharges and 3-D Secure flows vary by carrier and by aggregator; agree early who is merchant of record
- Volatile caching: LCC fares move quickly, so cached prices need short lifetimes and a verify-before-pay step in the flow
- Schedule change handling: notifications may arrive by email to the booking contact rather than through structured queues, so servicing needs its own monitoring
None of this is a reason to avoid LCC content; it is a reason to model it separately inside your booking engine rather than forcing it through GDS-shaped assumptions.
Servicing LCC bookings
Changes and cancellations on LCCs are usually self-service against the carrier's own systems, under retail-style rules (fixed change fees plus fare difference, limited refunds). When you book through an aggregator, servicing runs through the aggregator's API or support desk, and its depth varies by provider and carrier. Before launch, script your top five servicing scenarios, including a name correction, a date change, a cancellation and a schedule change, and test each through the actual channel your customers will depend on. If you plan to combine LCC segments into self-connect itineraries, the risk handling described in our virtual interlining guide becomes part of servicing too.
Choosing your approach
Match the channel to your business: a metasearch or flight aggregator website can start with aggregator content only, because it needs breadth and price freshness more than deep servicing; an OTA selling packages needs ancillary depth and reliable post-booking flows, which pushes toward stronger aggregators and selected direct connects; a corporate agency may find its LCC needs partly covered inside its existing GDS. Whichever mix you choose, keep supplier-specific logic behind one internal interface so adding the next carrier is configuration, not a rebuild.
This article is general information about travel technology and online marketing. It is not legal, tax or financial advice, and advertising platform policies change often. Check the current policy documents and take professional advice for your own situation.