The short version
- A white label travel portal is a ready-built booking platform sold under your brand. The variation between providers is enormous.
- The three pricing models — monthly SaaS, per-booking commission, and one-time licence — have very different economics as you scale.
- Ask what happens to your data, your customers and your platform if you stop paying. The answer defines the relationship.
- “Source code included” means different things to different vendors. Get the specifics in writing.
The phrase “white label travel portal” covers everything from a rebranded iframe to a complete booking platform with your own supplier contracts and source code in your possession. Two providers can use identical language and offer fundamentally different products. This guide is about telling them apart.
What a complete platform actually contains
Before comparing vendors, it helps to know the full scope. A production travel platform is far more than a search box.
Customer-facing
- Search and results for each product you sell — flights, hotels, tours, car hire, transfers — with filters, sorting and comparison.
- A booking flow that collects passenger details correctly for each supplier’s rules, including child ages and document requirements.
- Payment, in the currency the customer expects, with 3-D Secure and proper failure handling.
- Confirmation documents: e-tickets, hotel vouchers, activity vouchers, and tax invoices that satisfy your jurisdiction.
- Account area, booking history, cancellation requests.
Behind the scenes
- Supplier connections with search, price re-check, book, retrieve and cancel.
- Markup rules — by product, supplier, route, channel and customer tier.
- An agent channel with wallets, credit limits, tiered pricing and top-up approval, if you sell B2B.
- Accounting: what you charged, what the supplier charged you, what margin remains, and what tax is owed.
- Refunds and cancellation handling that moves money correctly, not just a status change.
- Admin tooling: supplier credentials, content management, staff roles, audit logs.
Any provider whose demo covers only the first list is showing you a shopfront, not a business. The second list is where operational cost lives, and it is the part that is expensive to add later.
The three pricing models
| Model | How it works | Best when |
|---|---|---|
| Monthly SaaS | A recurring fee, often tiered by bookings or users. The vendor hosts everything. | You want low upfront cost, are testing the market, and are comfortable that the platform is not yours. |
| Per-booking commission | A percentage or fixed fee on every transaction, sometimes with a smaller base fee. | Volume is low or unpredictable. Becomes the most expensive option at scale — the cost grows precisely as you succeed. |
| One-time licence | A larger upfront payment for the platform, often including source code, with optional support. | You expect meaningful volume, want predictable costs, and want control over the roadmap. |
Run the arithmetic at your expected volume rather than today’s. A 2% per-booking fee is trivial at ten bookings a month and material at a thousand. Conversely, a large upfront licence is poor value if you are still validating demand.
Six traps to check for before signing
1. “Source code included” that is not what it sounds like
This phrase is used loosely. Ask precisely: do you receive complete, readable source for the whole application, or compiled and obfuscated components? Are you permitted to modify it? Can another developer maintain it without the vendor? Get the answer in the contract, not the sales call.
2. Lock-in through supplier relationships
Some providers place your supplier connections behind their own accounts. It looks convenient — no contracts to sign, instant content. The consequence is that leaving the vendor means losing your inventory, and you never build direct supplier relationships or negotiate your own rates. Ask whether you can use your own supplier credentials.
3. No data export
Your customer list, booking history and financial records are your business. Confirm you can export them in a usable format at any time, without a fee and without notice. If the answer is vague, treat it as a no.
4. Hidden per-transaction costs
A low headline price can conceal charges on payment processing, per-booking fees, SMS or email costs, or a markup applied to supplier rates before you see them. That last one is worth checking carefully: if the platform silently marks up net rates, your margin is smaller than you think and you cannot see it.
5. Customisation that requires the vendor
If every change — a new field, a different tax rule, a design tweak — requires a paid vendor request, your roadmap is not yours. Ask what you can change yourself through configuration, and what needs development.
6. Abandonment risk
Travel software vendors do go quiet. If yours stops maintaining the platform, what happens? A hosted product simply degrades. Holding the source code at least means another developer can take over. This is the strongest practical argument for licensed source over pure SaaS.
A useful test question: “If I stop paying you tomorrow, what do I still have?” The answer tells you whether you are buying an asset or renting a service. Both can be right — but you should know which one you chose.
Build, buy, or licensed source?
There are three honest routes, and the right one depends on your capital, timeline and ambition.
Build from scratch. Total control, and a multi-month project before your first booking. You will rebuild things that are already solved — markup engines, invoicing, wallet accounting, voucher generation, supplier quirks. Worth it only if your product is genuinely different from what exists, or you have engineering capacity to spare.
SaaS. Fastest to launch, lowest upfront cost, least control. Sensible for testing a market. The economics deteriorate at volume and you are dependent on someone else’s roadmap and continued existence.
Licensed platform with source. A middle path: you launch quickly on proven code, but you hold the source, host it yourself, keep your own supplier contracts and can modify anything. Higher upfront cost, no per-booking tax on your growth. This suits agencies that intend to build a real business rather than run an experiment.
Questions to ask every provider
- Which suppliers are connected, and can I use my own supplier accounts?
- Do I receive complete source code? May I modify it? May another developer maintain it?
- Where is it hosted, and can I host it myself?
- Can I export all my data — customers, bookings, financials — whenever I want?
- What is the total cost at 100 bookings a month? At 1,000?
- Are there per-booking, payment, or messaging fees on top of the headline price?
- Is the platform marked up before I see supplier rates?
- Which currencies can I sell and settle in?
- Does it produce tax-compliant invoices for my jurisdiction?
- Can I run both B2C and a B2B agent network on the same platform?
- What happens to my platform if you cease trading?
- Who owns the customer relationship and the customer data?
Regional considerations most vendors ignore
Generic platforms are usually built for a generic market, which means they miss things that matter locally.
Currency. Selling in AED, SAR or INR while your supplier prices in EUR requires deliberate handling. The customer should see, pay and be invoiced in one consistent currency — not a converted display price with a foreign-currency charge behind it.
Tax invoicing. UAE VAT rules require specific invoice content, and foreign-currency invoices must show the tax amount converted to AED. India’s GST has its own requirements for travel. A platform that produces a generic receipt is not compliant, and compliance is not optional.
Payment methods. Regional gateways matter. So does the settlement currency your gateway supports.
B2B habits. In the GCC and South Asia, a large share of travel is sold through sub-agents. If your platform cannot run an agent channel with wallets and credit, you are excluded from most of the market.
How to evaluate a demo properly
Sales demos are choreographed. To get past that:
- Ask to complete a real booking end to end, including payment, and to see the voucher and invoice it produces.
- Then cancel that booking and watch what happens to the money.
- Ask to see the admin side — markup rules, supplier configuration, accounting reports — not just the customer-facing pages.
- Search a route or destination you actually sell and compare prices with what you can find elsewhere.
- Ask to see a tax invoice for your jurisdiction.
A provider confident in their product will show you all of it. Reluctance is information.
The decision, simplified
If you are validating an idea and cash is tight, start on SaaS and accept the constraints. If you have committed to travel as a business and expect volume, a licensed platform with source access almost always works out cheaper and safer within two years — not because the software is better, but because you are not paying a tax on your own growth, and you cannot be switched off.
Ownership, resale rights and what the licence actually permits
“You own the source code” is one of the most loosely used phrases in this market, and it conflates several distinct rights. It is worth separating them explicitly before signing, because they are usually different.
- Access — can you read the complete source?
- Modification — may you change it, and does doing so void support?
- Hosting — may you run it on infrastructure you control, or only on the vendor’s?
- Number of deployments — one domain, or several brands?
- Resale — may you sell the platform on to others? Almost always no, and reasonably so.
- Intellectual property — who owns the underlying code, as distinct from your right to use it?
A typical and entirely fair arrangement is: full source access, freedom to modify, self-hosting permitted, one or more named domains, no resale rights, and IP retained by the vendor. That gives you operational independence and protects the vendor’s business. What you want to avoid is discovering after purchase that “ownership” meant a licence to use a hosted instance.
Ask for the licence agreement before you pay, and read the termination clause specifically. What happens to your deployment if the agreement ends is the clause that matters most and is read least.
Migration: what moving actually involves
Whatever you choose, there is some chance you will move within a few years. Understanding what that entails changes how you evaluate providers.
Moving a travel platform means transferring customer records, historical bookings, financial records and any content you have created; re-establishing supplier connections with your own or new credentials; reconfiguring markup rules and tax settings; migrating agent accounts and wallet balances if you run B2B; and doing all of it while continuing to trade. Historical bookings matter more than people expect, because customers travel months after booking and you must service what you sold.
The practical implication is to check export capability before you commit rather than when you leave. Ask whether you can export customers, bookings, financial records and agent balances in a structured format, on demand, without a fee. A provider that answers cleanly is confident in their product. A vague answer is itself the answer.
Frequently asked questions
What is a white label travel portal?
A ready-built travel booking platform sold under your own brand. Customers see your name, logo and domain; the underlying technology and supplier connections come from the provider. Offerings range from hosted software you rent to a complete platform whose source code you hold.
How much does a white label travel portal cost?
It depends entirely on the model. Monthly SaaS typically runs from a few hundred dollars a month upward. Per-booking commission models charge a percentage of each transaction. One-time licences involve a larger upfront payment, often including source code, with optional ongoing support. Compare total cost at your expected volume, not the headline price.
Do I need my own supplier contracts?
Not always, but it is usually better. Using a provider's supplier accounts is faster to launch but creates dependency — leaving the provider means losing your inventory. Your own contracts mean your own negotiated rates and a relationship that survives a change of platform.
Can I run both B2C and B2B on one platform?
A capable platform supports both from the same system: a public website for direct customers, and an agent channel with logins, wallets, credit limits and tiered pricing. In the GCC and South Asia this matters, because a large share of travel is sold through sub-agents.
What happens if the provider goes out of business?
With hosted SaaS, typically your platform stops working and you migrate under pressure. If you hold the source code and host it yourself, the platform keeps running and another developer can maintain it. This is the strongest practical reason to prefer licensed source over pure SaaS for a business you intend to keep.
See it working, not just described
Travelzop is a white-label travel platform built and run in the UAE — flights, hotels, tours, car hire and transfers, with your brand on it and the source code in your hands.
Talk to us →