The travel wholesaler technology stack nobody demos

Every travel wholesaler technology stack is sold the same way: the demo starts on the search screen. Somebody types Dubai to London, a page of fares comes back, a price gets clicked, a PNR appears, and everyone in the room nods. Then the laptop closes, and nobody has shown you what happens on Tuesday morning — when a sub-agent in Sharjah wants yesterday's ticket moved to Friday, an airline has changed the schedule on six of your bookings overnight, and your accountant is asking why the supplier statement and your own sales report disagree by an amount nobody can explain.
That second half is what the stack is really for. A search screen is the part anyone can buy. The consolidator back office — the queues, the reissues, the money that moves after the ticket — is the part that decides whether you can grow from twenty sub-agents to two hundred without hiring a person for every ten.
This piece is about that half: what to ask for, what to test before you sign, and where wholesalers usually discover too late that something was missing.
Two halves of a travel wholesaler technology stack
Split the system in your head before you evaluate anything. The front half sells: availability, pricing, markups by sub-agent, booking, ticketing. The back half services what was sold: changes, cancellations, refunds, debit and credit memos, sub-agent credit, settlement, and the reports that turn all of it into numbers your finance team will sign.
Vendors spend their demo time on the first half because it is visual. Wholesalers lose their money in the second half because it is not.
The mid-office: where tickets go after they are sold
"Mid-office" is the trade's name for everything between the booking and the books. It is unglamorous, and it is where staff time quietly disappears.
Queues
Every wholesaler runs queues, whether or not they call them that: bookings on hold that must be ticketed before a time limit, schedule changes waiting for someone to accept or rebook, refund requests waiting on the airline, sub-agent messages that need an answer. The question is not whether your system has a screen called "queues". It is whether each item has an owner, a deadline and a visible state — so that the booking whose ticketing time limit runs out at 23:40 does not depend on somebody remembering it.
If your queue today is a WhatsApp group and a shared inbox, write down every type of item that lands there for one week. That list is your mid-office requirement, and it is more useful than any vendor's feature sheet.
Reissues
A reissue is never just a new ticket. There is a fare difference, a change penalty, sometimes a tax difference, and a decision about who pays which part: the passenger, the sub-agent or you. A system that reissues correctly at the airline but leaves the sub-agent's balance untouched has created a debt nobody will find until month-end.
Refunds
Refunds run on two clocks. The airline refunds you on its schedule; your sub-agent wants the money on theirs. Your stack has to hold the states separately — refund requested, refund received from the supplier, refund passed on to the sub-agent — or your team will be paying out refunds you have not received yet, and now and then ones you never will.
Memos
Agency debit memos arrive weeks after the sale, usually for something a sub-agent did: the wrong fare basis, a no-show that was never cancelled, a duplicate booking. If your system cannot tie the ADM back to the original booking and the sub-agent who made it, you absorb it. The habits that stop ADMs arriving in the first place are in our consolidator checklist for avoiding airline ADMs; the mid-office job is making sure the ones that do arrive land on the right account.
Reporting your finance team will actually accept
Finance does not want a dashboard. It wants rows that tie out. Ask any wholesaler booking system for these, as data you can export rather than a chart you can admire:
- Every booking with its net cost, your markup, the sub-agent's selling price and the sub-agent who sold it, on one line.
- Changes and refunds as rows of their own, linked to the original booking — not edits that overwrite it.
- A balance per sub-agent that matches what you have invoiced them.
- Totals by supplier for the same period, so the supplier's statement can be checked against something.
The last point is where most reconciliations break. A report of what you sold is not a report of what you owe, and an accountant who has to rebuild the second from the first in a spreadsheet will do it every month, by hand, for as long as you run the business.
Sub-agent credit belongs in the same place. Credit limits and settlement invoices should be records inside the system, not a spreadsheet beside it, because the moment they live in a spreadsheet a booking can be issued against credit that was already spent. We wrote separately about how to set and police sub-agent credit limits.
Staff roles and who can see net
Net fares are a wholesaler's crown jewels. In a small office everyone sees everything, because everyone is trusted. Past a certain headcount that habit becomes the way a net rate ends up with a competitor, or a markup gets cut to close one sale and is never put back.
Here is a starting split. Yours will differ, and it should — the point is to have decided it rather than inherited it.
| Role | Sees net cost | Changes markups | Refunds | Sub-agent credit |
|---|---|---|---|---|
| Owner / director | Yes | Yes | Approves | Sets |
| Finance | Yes | No | Approves | Sets |
| Ticketing / operations | Yes | No | Processes | No |
| Sales / account manager | Arguable | Within a band | No | Requests |
| Sub-agent's own staff | Never | Their own markup only | Requests | No |
The row people argue about is sales. Some wholesalers want account managers to see net so they can negotiate on the spot; others keep net for finance and give sales a floor price instead. Either is defensible. What is not defensible is a system in which the choice cannot be made at all, because the only roles it knows are "admin" and "user".
The integration points that always get retrofitted
Every wholesaler eventually connects its booking system to something else. These are the connections that get forgotten during selection and bolted on later, at a higher price:
- Accounting. Bookings, refunds and memos have to reach your ledger. Ask exactly how: a scheduled export, a file your accountant imports, or nothing at all.
- Payment collection. Card and bank payments from sub-agents need matching to invoices. If that matching is manual, at volume it is somebody's full-time job.
- Your largest sub-agents' own systems. The big ones will eventually ask for an API instead of a portal. Find out before they ask whether your platform can offer one, and on what terms.
- Supplier statements. The data you reconcile against has to come from somewhere. Find out what format each supplier actually sends.
None of these appear in a demo. All of them appear in the second year.
What this costs you if you get it wrong
A thin back office does not fail loudly. It leaks. A refund paid twice. An ADM written off because nobody could prove which sub-agent caused it. A reissue whose fare difference was never charged on. A sub-agent who ran past their credit because the limit lived in one person's head. Each one is small enough to absorb, which is exactly why they keep happening — and together they come straight out of the thin margin a wholesaler lives on.
The other cost is people. Without the mid-office inside the system, growth is linear: more sub-agents means more operations staff, and your cost per booking never falls. Breaking that line is the whole point of the stack.
So when you evaluate a platform, bring your own Tuesday morning. Take last week's list of queue items, one real reissue, one real refund and one real ADM, and ask the vendor to walk each through their system while you watch. If you want to run that exercise with us, tell us how your office works today and we will go through it in the admin panel rather than on a slide.
A search screen tells you what a system can sell. The back office tells you whether you can afford to sell through it.