Short answer: a bed bank is a business-to-business hotel wholesaler. It contracts net rates and room allocations from hotels, then resells that inventory through an API or extranet to travel agencies, tour operators and websites, which add their own margin before selling to the traveller. Bed banks never sell to the public; they exist so that thousands of resellers do not each need thousands of hotel contracts.
What a bed bank actually is
A bed bank, also called a hotel wholesaler or accommodation consolidator, sits between hotels and travel sellers. On one side, its contracting teams negotiate net rates, allotments (blocks of rooms) and sometimes guaranteed commitments with individual hotels, chains and other suppliers. On the other side, it distributes that pooled inventory to travel agencies, tour operators, airlines, and online travel websites through an API or an agent extranet.
The defining feature is that the bed bank is strictly B2B. Industry references such as AltexSoft, Hotel Tech Report and SiteMinder all describe the same shape: the wholesaler aggregates supply, the reseller owns the traveller relationship, and the traveller usually never learns a wholesaler was involved. If you are building a white label hotel booking website or a B2B portal, a bed bank is very often the first source of inventory you connect.
How the commercial model works
The economics are simple in outline, even if the contracts are not. In general terms:
- Net rates in. The hotel gives the bed bank a rate below its public selling price, either from a static contracted rate sheet, a dynamic feed from its channel manager, or both.
- Margin out. The bed bank adds its own margin and passes the rate to resellers. Resellers add their markup on top before showing a price to the traveller.
- Volume is the point. Each individual margin is thin, so bed banks compete on breadth of inventory, rate competitiveness and API reliability rather than on brand.
Payment typically runs on agency credit lines, deposits or virtual cards between reseller and bed bank, with the bed bank settling with the hotel. Exact terms vary by contract and region, which is one reason the same bed bank can look very different to two different resellers.
Named bed banks and how they differ
A few names come up in almost every conversation about wholesale hotel inventory:
- Hotelbeds (part of HBX Group) is the best known name in the category. Its APItude API suite is widely integrated by online travel sites, and coverage tilts strongly toward leisure destinations.
- WebBeds grew quickly through acquisitions of regional wholesalers and, by property count, is reported by sources such as Mews and AltexSoft to have reached a scale comparable to Hotelbeds.
- TBO is a large India-headquartered distribution platform popular with agencies across India, the Middle East and emerging markets.
- RateHawk (a brand of Emerging Travel Group) is known for a developer-friendly API and strong coverage in Europe and surrounding regions.
They differ mainly in regional depth, the split between directly contracted and third-party inventory, payment options and API quality. Because much bed bank inventory is itself sourced from other wholesalers, two feeds frequently contain the same room at different prices, which is why hotel room mapping matters as soon as you connect more than one supplier.
Bed bank vs channel manager vs direct contract
These three terms get mixed up constantly because all of them touch hotel rates. They solve different problems:
| Model | Who uses it | What it does |
|---|---|---|
| Bed bank (wholesaler) | Travel sellers needing inventory | Aggregates net-rate inventory from many hotels and resells it B2B through one API and one contract. |
| Channel manager | Hotels | A tool the hotel uses to push its own rates and availability out to many channels (OTAs, bed banks, GDS) from one screen. |
| Direct contract | Larger OTAs, DMCs, tour operators | A rate agreement negotiated directly between one seller and one hotel or chain. Best margins, highest workload per property. |
| Hotel aggregator / switch | Travel sellers | A technology layer that connects many bed banks and channels through a single normalised API, without contracting hotels itself. |
In short: a channel manager is hotel-side software, a bed bank is a middleman with its own inventory contracts, and a direct contract removes middlemen at the cost of doing all the contracting yourself. Most growing travel businesses combine a bed bank or two with a handful of direct contracts in their core destinations.
Why wholesale rates come with strings attached
Wholesale rates are cheaper than public rates for a reason: hotels protect their direct channels. Contracts commonly restrict how wholesale rates may be displayed or sold, for example limiting some rates to packages (bundled with a flight or transfer) or to closed user groups such as logged-in members. Cloudbeds and SiteMinder both note that wholesale rates are generally not meant to be shown openly on the public web at the bare net price.
For a website owner this means two practical things. First, read the rate usage rules in your bed bank agreement and build your display logic around them. Second, do not assume every cheap rate is safely resellable in every market; your booking flow and terms need to reflect the rate conditions the supplier passes along, which is part of what we implement in every hotel booking engine build.
What integrating a bed bank involves
Access starts with a commercial agreement: you sign directly with the bed bank, receive test credentials, and get production access after their checks. Nothing about that step is technical, but nothing works without it. On the technical side, a typical integration covers:
- Static content sync: downloading hotel descriptions, images, amenities and geodata into your own database on a schedule.
- Search and availability: live pricing calls at search time, with caching rules that respect the supplier's fair-use limits.
- Booking, modification and cancellation flows, including handling of cancellation deadlines and supplier confirmations.
- Mapping and deduplication against your other suppliers, so one hotel appears once with the best available price.
- Certification: most bed banks review your test transactions before enabling production.
This is the core of our hotel API integration service, and the same pattern applies whether the supplier is a bed bank, an aggregator or a direct connect. The wider context of connecting flights, hotels and ancillaries into one platform is covered on our travel API integration page.
What to watch before you rely on one
- Overlap between suppliers. Adding a second bed bank rarely doubles your inventory; much of it will be the same hotels again. Judge suppliers by unique, bookable inventory in your target destinations.
- Rate display rules. Breaching package-only or closed-group conditions can get your access suspended.
- Search fair-use limits. Wholesalers monitor your look to book ratio; a site that searches heavily and books rarely will hear about it. See our guide to the look to book ratio.
- Relocation and failure handling. Occasionally a confirmed room is not honoured by the hotel; understand the bed bank's relocation policy before it happens to your customer.
- Payment and credit terms. Deposit and credit models affect your cash flow more than the headline margin does.
None of these are reasons to avoid bed banks; they are reasons to integrate them properly, with mapping, caching and error handling designed in from the start rather than bolted on later.
This article is general information about travel technology and online marketing. It is not legal, tax or financial advice, and advertising platform policies change often. Check the current policy documents and take professional advice for your own situation.