Every travel business that gets past a certain size has this conversation. The agent network is growing, the spreadsheet is groaning, and somebody says: we should build a portal.
Sometimes that is right. More often it is the most expensive way to discover what the requirements were. Here is how to tell which case you are in, without spending a year finding out.
What "white-label" has to mean
Before comparing options, be precise about the word, because vendors are not.
A genuinely white-label portal means your agents never encounter the platform underneath. Concretely:
- Your domain. Agents type your address, not somebody else's with your name in a subdirectory.
- Your brand throughout. Logo, colours and type on the portal, the login screen, the confirmation email and the voucher.
- Your documents. The voucher your agent forwards to their client carries your licence number and your support line.
- No platform mention anywhere an agent can reach. Not in the footer, not in the email headers, not in the page title.
If a system is white-label everywhere except the emails, it is not white-label. Emails are where agents look most.
The three options, honestly
Build it yourself
When it makes sense: your inventory or your commercial rules are genuinely unusual, and that unusualness is your competitive advantage.
What it actually costs: the booking flow is the easy part. The expensive parts are the ones nobody scopes — the ledger that has to reconcile, the availability that has to be consumed under a lock so two agents cannot take the last seat, the snapshotting so a voucher reprinted next year shows last year's policy, the tax and currency handling, the audit trail, the password resets, the second factor, the backups, the person who is on call when it breaks at 3am on a Saturday.
The trap: you will get a working demo in six weeks and spend eighteen months on the last 20%. That last 20% is entirely made of the cases that lose money when they are wrong.
Adapt a consumer booking engine
When it makes sense: almost never, but it is tempting because these are cheap and plentiful.
Why it usually fails: consumer engines assume one price for everyone, a card at checkout, and a traveller at the other end. B2B needs per-agent pricing, credit balances, and an agent acting for somebody else. You can bolt those on. What you cannot bolt on afterwards is a correct ledger.
Use a white-label B2B platform
When it makes sense: your inventory is hotels, tours and transfers in recognisable shapes; you sell to an agent network; you want to be selling next quarter rather than next year.
What you give up: you work within someone else's model of a rate plan. If your business genuinely does not fit that model, this is a real cost, not a small one.
What you get back: the unglamorous 80% — ledger, locking, snapshots, auth, backups, deliverability — already built and already having failed in other people's businesses first.
The question that decides it
Not "can we build this?" — you probably can.
The question is: is your booking system the thing your customers pay you for?
For a DMC, it is not. Agents pay for your contracts, your ground knowledge, your ability to fix a problem in-destination on a Sunday. The portal is how they reach that. It has to work, it has to carry your brand, and it has to be invisible. It is plumbing.
For a technology company selling travel software, it obviously is the product. Different answer.
A checklist for evaluating a platform
If you land on buying, these are the questions that separate a system you will still be using in three years from one you will migrate off:
On inventory
- Can it hold a hotel as room type × rate plan × season, with per-occupancy prices and real allotment — not just a nightly rate?
- Can a tour have several options, each with its own capacity, operating days and time slots?
- Are transfers priced per vehicle and per seat, or only one of the two?
- What happens on a date you close? Does it override everything, or does something else quietly re-open it?
On money
- Is the agent balance a ledger you can export and reconcile, or a field?
- Does a booking hold funds before it debits them?
- What happens to the money if a booking fails halfway?
- Can you set a different margin for a different agent without maintaining a second rate sheet?
On the brand
- Can you point your own domain at it?
- Are the vouchers and the emails yours, or theirs with your logo in a corner?
- Does the platform's name appear anywhere an agent can see?
On the boring things that matter later
- Can you export everything — bookings, products, agents, ledger — without asking permission?
- Is there an audit trail of who changed what?
- Is two-factor authentication available for the people who can move money?
- Where are the backups, and has anyone restored from one?
On the answer you should be suspicious of
Ask what the system does badly. A vendor with no answer either has not run it in production or is not going to be straight with you about the parts that will annoy you.
The middle path most people miss
You do not have to choose once and forever.
Start on a platform. Sell. Learn what your agents actually use, which is never what you predicted. If, two years in, you have found something genuinely specific to your business that no platform will do — build that, and keep buying the plumbing.
The mistake is not buying, and it is not building. It is building the plumbing, badly, in year one, when you did not yet know what your business needed.