The B2B travel portal guide for agencies and consolidators

1. What a B2B travel portal is

A B2B travel portal is the booking and management system a travel business gives to other businesses rather than to leisure consumers. Its users are sub-agents, corporate travel desks, and the agency's own consultants — each with different fares, credit terms, and permissions on the same inventory.

That makes three things non-negotiable: many supplier connections behind one search, a tenant hierarchy that keeps each party's pricing private, and an audit trail for every booking, approval and payment.

2. Multi-agency and multi-corporate structure

A consolidator typically sits at the top, with sub-agencies beneath it and corporate clients beneath either. Each level needs its own branding, users, roles, fare visibility and reporting, while the parent retains oversight.

3. Supplier connectivity: GDS, consolidator, NDC, LCC

"GDS integration" is only one of four common content sources, and most agencies end up running several at once — often one GDS credential per country of registration.

A portal should treat each of these as a configurable connection with its own environment (test or production), its own labels, and its own on/off switch — not as hard-coded code paths.

4. Making search fast with route-scoped offer profiles

Once fifteen connections exist, polling all of them on every search is slow and pointless. A domestic India search rarely benefits from a Finnish GDS office, and a Frankfurt–Madrid search rarely benefits from an Indian LCC feed.

The fix is to scope search by route and business context. Define profiles such as "Europe intra" or "India domestic", list only the suppliers worth polling for each, give them a priority order, and keep one catch-all default. Each search resolves the highest-priority matching profile, queries only its enabled sources in parallel, and still shows every returned fare side by side for comparison.

• Scope by origin/destination country or region, plus agency, corporate or trip type.
• Choose parallel, sequential or hybrid polling per profile.
• Rank results by price, duration, preferred carrier or supplier reliability.
• Add fallback rules for empty or timed-out responses so a search never dead-ends.
• Simulate a test route before publishing the profile.

5. Corporate policy, approvals and requisitions

Corporate buyers judge a portal on control as much as on fares. Practical requirements: travel requisitions raised before booking, approval chains by amount, grade or cost centre, blanket approvals for recurring travel, in-policy and out-of-policy grading shown at search time with a reason capture, and expense capture that reconciles back to the trip.

6. Sub-agency wallets, fees and incentive revenue

B2B distribution runs on credit and margin. Sub-agencies book against a wallet or credit limit with a visible ledger; each level can add its own service fees; and the parent agency's own earnings — airline productivity bonuses, contracted incentives on specific booking classes — accrue internally on top of what the sub-agency pays.

Those incentives are the parent's commercial arrangement with the airline, so they should be recorded against the airline contract, calculated on a defined base (base fare, base plus YQ/YR, or total), and reported only to the roles entitled to see them.

7. Evaluation checklist

• Can you add a new GDS, consolidator, NDC or LCC connection without a code change?
• Can you control which suppliers are polled for which routes?
• Can sub-agencies be white-labelled with their own fares and fees?
• Do corporate policy, approvals and requisitions work before ticketing, not after?
• Is every wallet movement, fee and incentive traceable to a booking?
• Can each tenant export its own reporting without exposing the parent's margin?