A booking extranet is a private, login-only website that a travel company opens to its partners, so they can manage or book inventory without access to its internal systems. Hotels use one to set their rates on a booking site; travel agencies use one to book a wholesaler’s rooms and fares. Tripgic works on the other side of that line: it is a travel API that platforms connect to directly once booking by hand in a portal is no longer enough.
This guide explains the different kinds of booking extranet, how each works, who uses them, their limits, and how to tell when a business should move from an extranet to an API.
Looking for the Booking.com Extranet login? It is reached through the Booking.com Partner Hub. This article explains what extranets are and how they work across travel.
What Is an Extranet?
An extranet is a private network or website that a company opens to selected outside partners. It sits between two familiar ideas:
| Who can use it | Travel example | |
|---|---|---|
| Internet | Anyone | A hotel’s public website |
| Extranet | Selected partners with a login | An agency booking portal, a hotel’s channel extranet |
| Intranet | The company’s own staff | A tour operator’s internal reservations system |
Each partner gets its own login and sees only what it is allowed to see: its own hotel, its own contracts, its own bookings. In travel, “extranet” almost always means one of these partner portals.
The Two Directions of a Booking Extranet
The word is used for two systems that face opposite ways. Most confusion about extranets comes from mixing them up.
| Supplier extranet | B2B agent extranet | |
|---|---|---|
| Who logs in | Hotels, tour suppliers, transfer companies | Travel agencies, tour operators, corporate bookers |
| What they do | Load and manage what they sell | Search and book inventory to resell |
| Who runs it | The sales channel — an online travel agency, wholesaler or marketplace | The wholesaler, bed bank or consolidator |
| Direction of inventory | Into the channel | Out to the agent |
| Example | The Booking.com Extranet | A bed bank’s agent portal |
A wholesaler often runs both: a supplier extranet where hotels load contracted rates, and an agent extranet where agencies book them.
Supplier Extranets: How Hotels and Suppliers Sell
What a hotel does in a channel extranet
A hotel listed on an online travel agency manages that listing through the channel’s extranet. Typical tasks:
- Rates — set prices per room type, rate plan and date.
- Availability — open and close rooms, set how many to sell.
- Restrictions — minimum stay, closed to arrival, release periods.
- Content — photos, descriptions, facilities, policies.
- Reservations — view, confirm and manage bookings.
- Messages and reviews — reply to guests and to the channel.
- Finance — invoices, commission statements and payouts.
The Booking.com Extranet is the best-known example. Other large channels run their own: Expedia’s is called Partner Central, and Trip.com Group’s hotel extranet is often called eBooking. Hotel searches for “Ctrip extranet” and “ebooking extranet” are looking for that one.
Tour, activity and transfer suppliers
Activity marketplaces and transfer platforms give suppliers similar portals, usually called supplier portals or management centres. A tour company uses one to load products, departure times, capacity, prices and cancellation rules, and to see bookings as they arrive.
Wholesaler and DMC contracting extranets
A wholesaler or destination management company that contracts hotels directly often gives each hotel an extranet to load its contracted rates, allotments and stop-sales. The hotel updates one place; the wholesaler sells those rooms through its own channels.
Channel managers: the extranet’s replacement for busy hotels
A hotel on ten channels would otherwise update ten extranets by hand. A channel manager connects to each channel through its API and pushes rates and availability to all of them from one screen. The extranet stays useful for content, messages and checking what the channel shows, but day-to-day rate work moves to the channel manager. This is the same pattern as the agent side: once there are many systems and much volume, an API replaces manual work in portals.
B2B Agent Extranets: How Agencies Book
What an agent extranet does
A B2B agent extranet — also called an agent portal or B2B booking portal — lets a travel agency search and book a supplier’s inventory at net or commissionable rates:
- Search hotels, flights, transfers, activities or tours.
- See net rates, the price before the agency’s own margin.
- Book and pay, often against a deposit or credit limit.
- Download vouchers and booking documents.
- Manage bookings — amendments, cancellations, refunds.
- Report — sales, outstanding payments, statements.
Who runs agent extranets
| Provider | What their extranet sells |
|---|---|
| Bed banks and hotel wholesalers | Hotel rooms at net rates |
| Consolidators | Airline tickets, often with special fares |
| DMCs | Ground services in their destination |
| Activity and transfer wholesalers | Tours, tickets and transfers |
| Airlines’ agency portals | Direct bookings and servicing for agents |
Who uses agent extranets
- Small and mid-sized travel agencies that book by phone, email or in the office.
- Tour operators building packages by hand for groups.
- Corporate travel teams booking hotels for staff.
- New OTAs testing a market before building a booking engine.
How a Booking Extranet Works Behind the Scenes
An extranet is a web application on top of the provider’s reservation system:
- Login and permissions. Each partner sees only its own data and allowed actions.
- Inventory and rates. For supplier extranets, data entered is saved to the channel’s system. For agent extranets, the portal reads live inventory from the provider’s own contracts and connected suppliers.
- Booking. A booking made in the portal goes into the same reservation system used by the provider’s API customers and staff.
- Payment and credit. Deposits, card payment or credit terms, depending on the contract.
- Documents. Vouchers, confirmations and invoices generated from the booking.
Often the same reservation system serves both an extranet and an API. The extranet is the screen for people; the API is the door for software.
Benefits of a Booking Extranet
- No development. Any staff member with a browser can use one.
- Fast to start. Sign a contract, get a login, start booking or selling.
- Low cost. Usually no integration fee; you pay per booking or through the rate.
- Good for low volume. Ten bookings a day do not justify an integration.
- Good for complex one-off work. Groups and special requests are often easier by hand.
- Visibility. A supplier can see exactly how its product looks on a channel.
Limits of a Booking Extranet
The same features that make an extranet easy also limit it as a business grows.
One portal per supplier
An agency working with five wholesalers has five logins, five search screens and five sets of vouchers. Comparing prices means searching five times.
Manual work does not scale
Every search, booking and change is done by a person. A busy agency hits the limit of staff time long before it hits the limit of demand.
No booking on your own website
An extranet sells to you, not to your customers. Travellers cannot book on your website through someone else’s portal. To sell online, you need the inventory inside your own system — which means an API.
Your data stays in their system
Bookings live in each provider’s portal. Reporting across providers means exporting and combining files.
Mistakes from re-typing
Copying traveller names, dates and prices between systems creates errors that are costly in travel — a wrong name on a ticket, a wrong date on a hotel.
Booking Extranet vs Travel API

| Booking extranet | Travel API | |
|---|---|---|
| Used by | People, in a browser | Software, automatically |
| Setup | A login | An integration project |
| Developers needed | No | Yes |
| Booking on your own website | No | Yes |
| Volume | Limited by staff time | Limited by the system |
| Combining suppliers | One portal each | One integration can cover many through an aggregator |
| Your own pricing and margin rules | Manual | Automatic |
| Your own customer data | Spread across portals | In your system |
| Best for | Low volume, complex one-off work | Online sales, scale, automation |
They are not rivals. Many agencies keep a portal for groups and odd requests while their website books through an API. For a deeper look at the API side, see what a travel API aggregator is.
When to Move From an Extranet to an API
Signs that a business has outgrown booking by hand:
- You want customers to book on your own website or app. An extranet cannot do this; an API can.
- Staff spend hours searching several portals for the same trip.
- Re-typing errors reach customers.
- You need your own pricing rules — margins by market, product or customer.
- Reporting across suppliers takes days of spreadsheet work.
- Search volume is growing faster than the team.
What changes when you move
| Area | Before (extranet) | After (API) |
|---|---|---|
| Searching | Staff, one portal at a time | Your system, many suppliers at once |
| Selling | Phone, email, office | Your website, app or booking engine |
| Pricing | Calculated by staff | Rules applied automatically |
| Booking data | In each supplier’s portal | In your own database |
| Team | Booking staff | Developers plus a smaller servicing team |
What the move needs
- A developer or a technology partner to build or adapt the booking flow.
- A sandbox to test searches and bookings without real charges.
- A plan for servicing — changes, cancellations and refunds through the API.
- Time — usually weeks for one product line on a modern API, longer when several products and suppliers are involved. See our travel API integration timeline.
Between booking on someone else’s extranet and building on an API sits a third option: running your own booking site without writing it. Reservationhub, a sister product of Tripgic, offers one as a managed cloud service or as source code you license. Our travel booking software guide compares the options.
What to Look for in a Booking Extranet
If an extranet is the right step today, judge it on:
| Question | Why it matters |
|---|---|
| Is the inventory live? | Cached prices that fail at booking waste time and lose customers |
| Are rates net and clear? | You need to see your cost and add your margin |
| How are payments handled? | Deposit, card or credit — each affects cash flow |
| Can bookings be changed and cancelled in the portal? | Servicing by email is slow |
| Are vouchers and invoices automatic? | Saves hours each week |
| Does the provider also offer an API? | So you can move without changing supplier or contract |
| What support is there? | A failed booking at 2 a.m. needs a person |
The question about an API is the one most worth asking early. Moving from a portal to an API with the same provider is far easier than changing provider and integration at the same time.
What to Look for in an Extranet if You Are a Supplier
For hotels, tour companies and transfer suppliers using channel extranets:
- A channel manager connection, so rates and availability are updated from one place.
- Clear commission and payment terms shown in the extranet.
- Reservation alerts that reach the right person at once.
- Content control — photos and descriptions you can update yourself.
- Reports on bookings, cancellations and revenue by channel.
Extranets in Corporate Travel
Companies that book travel for their staff meet extranets too. A travel management company may give a corporate client a portal to request or book trips within its travel policy, see invoices and download reports. Hotels with corporate rates may give large accounts an extranet to check their negotiated prices. As volume grows, the same pattern repeats: the portal is replaced or joined by an online booking tool connected by API, so policy, approval and reporting run automatically. Our corporate travel API guide covers that side.
Security in Extranets
An extranet is open to outside users, so access control matters:
- One login per person, not shared accounts.
- Two-step login where the provider offers it.
- Roles — a junior agent may book but not issue refunds.
- Removing access the day someone leaves.
- Watching for phishing. Fake extranet login pages and messages are a known way for criminals to steal hotel and agency logins and then contact guests. Only log in through the address you normally use, never through a link in an unexpected message.
The same principles apply to API keys. Our travel API security guide covers that side.
Extranet Terms You Will Meet
| Term | Meaning |
|---|---|
| ARI | Availability, rates and inventory — what a supplier updates in a channel extranet |
| Rate plan | A price with its own conditions, such as breakfast included or non-refundable |
| Allotment | A block of rooms a hotel holds for a wholesaler or tour operator |
| Release period | Days before arrival when unsold allotment rooms return to the hotel |
| Stop-sale | An instruction to stop selling a room or rate for certain dates |
| Net rate | The price to the agent before its own margin |
| Commissionable rate | A public price on which the agent earns a commission |
| Credit limit | How much an agency can book before it must pay |
| Voucher | The document the traveller shows to the hotel or supplier |
| Channel manager | Software that updates many channel extranets at once |
A Worked Example: One Booking, Two Ways
An agency in Dhaka has a corporate client who needs three nights in Dubai for two staff, with an airport transfer.
Through extranets:
- An agent logs into a bed bank portal and searches hotels near the client’s office.
- The agent logs into a second portal to compare the same hotels, because the first one’s prices look high.
- The agent books the hotel in the cheaper portal and downloads the voucher.
- The agent logs into a transfer supplier’s portal and books the transfer, re-typing the names and flight times.
- The agent writes the quote, adds the margin by hand and emails the client.
- When the client moves the trip by a day, the agent repeats steps in two portals.
Through an API inside the agency’s own system:
- The agent — or the client, on the agency’s website — searches once.
- The system shows hotels from several suppliers, with the agency’s margin already applied.
- Hotel and transfer are booked in one flow, with names entered once.
- The booking, vouchers and invoice live in the agency’s own system.
- A date change is made from one screen.
Both work. The difference is minutes per booking — and over hundreds of bookings a month, that difference is a team’s time.
Common Mistakes With Booking Extranets
- Sharing one login across the office. Nobody knows who booked what, and a leaver keeps access.
- Not checking cancellation deadlines. Portals show them; staff under pressure miss them, and a free cancellation becomes a charge.
- Comparing prices without comparing conditions. A cheaper rate may be non-refundable or without breakfast.
- Keeping bookings only in the portal. If the supplier relationship ends, the history goes with it. Export regularly.
- Staying too long. Running a growing online business through portals means paying staff to do what software could.
- Moving too early. Building an integration for twenty bookings a month costs more than it saves.
How Tripgic Fits: The API Side of the Line
Tripgic is a travel API, built for platforms that want inventory inside their own product rather than in someone else’s portal.
- One integration with 73 documented endpoints across 8 product families, listed in the API documentation.
- Flights from 800+ airlines, through GDS, NDC and low-cost carrier connections.
- Hotels — 2M+ properties from 50+ suppliers in 190+ countries through the Hotel API.
- One JSON format for every product, so search, validation and booking follow one pattern.
- A free sandbox with the same schema as production, available through the contact page.
- A per-booking fee model shown on the pricing page.
For an agency that books in five portals today and wants travellers to book on its own website tomorrow, that one integration replaces the five logins with one connection its own system controls.
Final Thoughts
A booking extranet is a partner portal: suppliers use it to manage what they sell on a channel, and agencies use it to book a wholesaler’s inventory. It is the right tool when volume is low, work is complex or there are no developers. It stops being enough when a business wants customers to book on its own website, needs its own pricing rules, or spends more time searching portals than selling.
That is the point to move to an API. If you want flights, hotels and more through one integration, book a demo with Tripgic and test it in the sandbox first.
Mehadi Hassan






Akhirul Islam