B2B travel portal vs white label portal: buy or sell?

The request usually arrives in one line: "We need a B2B portal." Sometimes it comes from an agency owner in Lahore who has watched three regular customers drift to an OTA app. Sometimes it comes from a two-person outfit in Sharjah that wants cheaper fares than its current supplier gives it. Same words, opposite problems. The first wants somewhere travellers can book under the agency's name; the second wants somewhere to buy. Settling the B2B travel portal vs white label portal question before you sign anything is what stops you paying a year of fees for the wrong half of your business.
Follow the money, not the feature list
Every comparison sheet for these products lists the same things — flight search, hotel search, a booking flow, a dashboard — and that is exactly why they confuse people. The screens look alike. What differs is the direction the money moves through them.
A B2B travel portal is where you buy. Someone upstream — a consolidator, a wholesaler, a bedbank — publishes net fares and net rates behind a login, and agencies sign in to book against them. Your markup gets added somewhere else: on the phone, on WhatsApp, on an invoice typed after the fact. The portal's customer is you.
A white label portal is where you sell. It is a storefront carrying your brand, your domain and your prices, and your customers search and book on it. The markup is applied inside it, by rules you set. The storefront's customer is the traveller — or, if you sell to other agencies, the agency below you.
Put like that, it sounds obvious. It stops being obvious the moment a vendor runs a demo, because a well-built B2B portal looks almost exactly like a storefront with a login screen in front of it.
B2B travel portal vs white label portal, side by side
Three kinds of business ask for "a portal". This is what each of them actually needs.
| Who you are | What you need | Who logs in | Where your margin lives |
|---|---|---|---|
| Sub-agent buying net fares | A B2B portal from a supplier | You and your staff | Added outside the portal, by hand |
| Agency selling retail under its own name | A white label storefront | Your travellers (or nobody — guests can book) | Markup rules in your own admin panel |
| Consolidator distributing to sub-agents and selling retail | Both, ideally from one account | Your sub-agents and your travellers | Net to the sub-agent, marked-up retail to the public |
The row people push back on is the first. Plenty of sub-agents say a login is all they will ever need, because their customers always phone. That holds until the customer who used to phone at eleven at night stops phoning.
Why one platform can be both
The distinction is about direction, not software, so nothing stops one system from carrying both directions at once. On this platform, that is how the pieces fit.
A storefront can require sign-in before anyone searches, and it can register business customers — other agencies — with an optional manual verification step before they get in. Switch that on and the storefront behaves as a B2B portal: verified agencies sign in, see your prices and book. Leave it off and the same engine is a retail site for travellers. Sub-agent credit limits and settlement invoicing are built-in concepts, so the agency that buys from you on account is not tracked in a spreadsheet sitting next to the portal.
Above that sits the reseller account, opened from the consolidator sign-up. It can sell white-label sites to other agencies, share its supplier content with a network, and act as a consolidator. Content moves through supplier groups rather than one-to-one deals: an agency sees the suppliers its groups grant it, which is how a consolidator decides who gets which inventory without negotiating every connection separately. Each tenant still has its own admin panel, with its own bookings, customers, markups and reports.
So the interesting businesses do not choose. A consolidator in Dubai can sell net to forty sub-agents through a sign-in-only storefront and sell retail to the public through a branded one, with a single set of supplier relationships underneath both. If the sub-agent side is what you are building, the longer piece on running a B2B portal for sub-agents goes through onboarding and credit in detail.
The mistake that looks like progress
Here is how it usually goes wrong. An agency wants its own online presence, hears "B2B portal" from a supplier's salesperson, and signs up. It gets a login. The fares are good. It puts the login address on its website, or posts a screenshot on Instagram, and waits for customers to book.
They cannot. A B2B login is issued to an agency, under the supplier's terms. A traveller has no account on it and should not have one, because what sits behind that login is net pricing the supplier never meant the public to see. The best case is that nobody books. The worse case is that the agency starts sharing its own credentials so a few loyal customers can "check prices" — and now its net fares are in front of people who will happily compare them with what the agency charges.
The reverse happens too, less often. A consolidator buys a retail white label to serve its sub-agents, then discovers the storefront cannot tell an agency from a tourist: no credit line, nothing to settle against. Every sub-agent ends up paying by card like a member of the public.
What getting it wrong costs
Not the subscription. That is the small number.
The real cost is a year spent reselling at someone else's markup. An agency with only a B2B login sells every ticket by hand: it quotes on WhatsApp, adds its margin in its head, takes payment, books on the supplier's portal, forwards the e-ticket. Every booking needs a person, so volume is capped by how many conversations the staff can hold at once. Meanwhile the customers who wanted to book themselves at midnight are doing exactly that — somewhere else, under another brand, which keeps the margin and the next booking as well.
Twelve months of that and the agency has the customer list it started with, slightly shorter. What it does not have is a booking history under its own name, a domain search engines have started to trust, or markup rules it would have tuned by now if they had lived in software rather than in someone's head. A storefront accumulates those things. None of them can be bought back later.
Four questions before you sign
- Who will type into the search box? Your own staff, agencies below you, or travellers. If the answer is travellers, a buying login is not the product.
- Where is the markup applied? If the honest answer is "by us, by hand, afterwards", you are buying, not selling.
- Will agencies buy from you on credit? Then you need credit limits and settlement, not just a checkout.
- Whose name is on the confirmation? The brand on the e-ticket email is the brand the customer comes back to.
Answer those and the vocabulary stops mattering. Most agencies that work through them find they need the sell side first, and the buy side from a supplier they already have. Consolidators usually find they need both, and should be asking whether one account can carry them. How you price the sell side is a separate decision; the guide to online markup strategy picks that up.
If you would rather see the sell side than read about it, the signup wizard provisions a branded storefront on a platform subdomain straight from the form, without asking for a card. It is a quicker way to learn which side of this you are on than another sales demo.