NDC beside GDS and LCC: a practical approach for agencies

Three channels, one order

GDS EDIFACT, airline NDC and LCC web APIs each use different models and vocabulary. Trying to keep three tools in sync leads to duplicate searches, inconsistent pricing and servicing dead‑ends. The pragmatic target is a single result set and a single order flow, with the source labelled so agents can see whether a fare is GDS, NDC, LCC or your own contract.

At search time, normalise and deduplicate. At booking time, ticket through the appropriate channel but record one order with the same documents and accounting fields whichever route issued it. Agents and mid‑office teams should not need to know which pipe was used to perform a change or refund.

When to prefer NDC, when to keep GDS

NDC brings richer content, ancillaries and airline‑controlled pricing. GDS remains strong for breadth, familiar servicing patterns and agency tooling. A sensible rule set is: prefer NDC when content is materially better or a product is only in NDC; prefer GDS when servicing is more robust there or when the airline’s NDC is not certified for a required flow. LCC APIs remain the source of truth for those carriers.

The key is that the choice should be policy‑driven, not manual. The agent sees one fare with a source tag; the platform routes to the right channel based on market, airline and capability.

Servicing without channel whiplash

After ticketing, handling changes, cancellations, refunds and involuntary schedule changes should follow one order model. The platform owns the orchestration to the right underlying system and surfaces status and documents consistently. That eliminates “this ticket must be changed in tool X” conversations and keeps travellers and finance in step.

Aggregator expectations

An NDC aggregator hides the per‑airline differences and tracks schema versions so you do not have to. Expect a published schema, clear capability flags per carrier, and a roadmap of airlines and features. Enable carriers per market as you sign commercial terms, without additional integration work per airline.

Where Elkanio fits

Elkanio provides an airline NDC aggregator alongside GDS and LCC connections through Synapse. The unified schema returns one set of results, with branded fares, seat maps and ancillaries where available. Agencies run this feed directly, and products like Nucleus bring the agent UI, multi‑tier control and mid‑office links on top.

Operational considerations

Train agents on one screen and one set of cues instead of three tools. Ensure your mid‑office understands the order model so reconciliation and reporting do not depend on the issuing channel. Measure outcomes like attachment of ancillaries and servicing time — not as vanity metrics, but as signals that agents are selling the richer content well.

Implementation checklist

• Pick five airlines and two markets to start
• Enable both GDS and NDC for those carriers
• Roll the unified search and order model to a pilot group
• Observe servicing edge‑cases for a month before expanding

Aim for confidence that the same flow works whichever channel wins a fare.