Skip to content
Voraal

Case study · Flight ticketing

The right GDS for every airline, chosen automatically.

Agencies with more than one GDS contract stop routing tickets from memory — the airline on the booking decides which GDS issues.

Problem area
Flight ticketing
Products
Rezencia
Built for
Flight consolidators · Wholesale agencies · OTAs with more than one GDS contract

A business that holds more than one GDS contract has to decide, booking by booking, which system issues the ticket. Rezencia makes that decision by rule: the airline on the booking determines the GDS, so the ticketing desk no longer routes from memory.

01 · The problem

The problem

Many Pakistani consolidators and agencies hold accounts with two or three of Amadeus, Sabre and Travelport. No single GDS is the best choice for every airline — negotiated fares, content and commercial terms differ by carrier.

The routing knowledge usually lives in experienced staff's heads or in a spreadsheet beside the ticketing desk.

  • New staff can't be trusted to ticket until they've learned the routing
  • Busy shifts — Umrah season, Eid, fare sales — raise the error rate
  • A ticket issued on the wrong GDS means a void and reissue, if it's caught in time
  • Every new airline deal means re-briefing the whole team

02 · Why it's hard to fix

Why it's hard to fix

  • The rule is commercial

    The right GDS for an airline depends on each business's own agreements — and changes whenever a deal changes.

  • Mostly right isn't right

    A routing habit that is correct most of the time still produces a steady stream of voids and reissues.

  • Checking slows ticketing

    Asking staff to look up a rule before every ticket defeats the purpose of having a ticketing desk.

03 · What we built

What we built

Ticketing in Rezencia is dynamic. The business sets, per airline, which of its GDS connections issues that airline's tickets. When a booking is ready, Rezencia reads the airline, applies the rule and issues through the named GDS. The person ticketing never chooses a system.

  • Works with the business's existing PCC, Office ID or SID credentials
  • Nothing migrated or re-registered
  • Rules changed in one place when a deal changes

04 · How it works

How it works

  1. 1

    Connect the GDS accounts

    Existing Amadeus, Sabre and Travelport credentials are connected to Rezencia.

  2. 2

    Set the rule per airline

    For each airline, choose which GDS its tickets are issued through.

  3. 3

    A booking reaches ticketing

    Rezencia reads the airline and selects the GDS the rule names.

  4. 4

    Ticket issued

    Issuance runs through that GDS and the ticket is recorded against the booking.

05 · What changes for the team

What changes for the team

BeforeWith Voraal
“Which GDS for this airline?” answered from memory or a spreadsheetA rule set once answers it every time
New staff learn routing before they can ticketStaff ticket from one screen; routing isn't their decision
A changed airline deal means re-briefing everyoneA changed deal means changing one rule
Wrong-channel tickets found and corrected by handStaff no longer choose the channel

06 · What it does not do

What it does not do

  • Rezencia applies the rules the business sets; deciding which GDS is commercially best per airline stays with the business.
  • It does not grant ticketing authority — IATA accreditation, a host-agency arrangement or a consolidator agreement is still required.
  • It works with existing GDS accounts and does not provide GDS contracts.

See it on your own bookings.

FAQ

Questions, answered.

Short answers about this solution.

Ask us anything
  • Which GDSs are supported?

    Amadeus, Sabre and Travelport, using the business's own PCC, Office ID or SID credentials.

  • Does the person ticketing choose the GDS?

    No. The airline on the booking determines the GDS, according to the business's rule.

  • Do we have to move our GDS accounts?

    No. Existing credentials work as they are — nothing to migrate or re-register.

WhatsApp