Skip to content
Blog

Hotel consolidator platform: contracts beside bedbank rates

Tekravel Editorial
Written with the help of AI

You contracted a block of winter rooms at a four-star in Deira. Three weeks later a sub-agent books that same hotel, for the same nights, through your own portal, at a bedbank rate that came in lower than your contract. Your rooms sit unsold until the release date, and the hotel takes them back.

Nobody made a mistake. The portal did what it was built to do: show the cheapest price. That is the problem a hotel consolidator platform has to solve, and it is a different problem from the one flight consolidators face. Airline net fares rarely compete with themselves. Hotel rates do, constantly, because the same room reaches your search results through a contract you negotiated and through two or three wholesale feeds you did not.

This piece is about running both side by side without the second quietly eating the first.

Three kinds of hotel rate, one result list

Most of the confusion starts because "hotel rates" gets used as if it were one thing. For a wholesaler it is at least three, and they carry different risk.

Static allotmentFree-saleLive (bedbank / dynamic)
What you holdA fixed number of rooms per night, at a contracted rateThe right to sell at a contracted rate until the hotel says stopNothing until you book; you resell someone else's rate
How availability is knownYour own count, reduced with each bookingAssumed open; closed by a stop-sale messageAsked for at search time
Who carries the riskYou, until the release dateMostly the hotel, but you carry the overbooking falloutThe bedbank, within its own terms
Where it goes wrongRooms unsold past release; count drifts from realityA stop-sale that arrives after the bookingPrice moves between search and book; the feed sells your contracted hotel cheaper
What it is good forPeak dates you know you can fillSteady shoulder-season volumeBreadth: every hotel you will never contract

You could argue with the last row, and you should. Some consolidators run free-sale as their main product and keep allotments only for events. The point of the table is not the ranking; it is that each column needs its own rules in the booking engine. Treat them as one stream and the engine will rank them as one stream, by price, which is exactly how the Deira rooms went unsold.

Why the cheapest rate is not always the one to show

When the same property arrives from your contract and from a live feed, something has to decide what the sub-agent sees. "Cheapest wins" sounds fair and is usually wrong for a wholesaler, because the cheapest rate is not the cheapest for you. An unsold allotted room costs you money whether or not anyone books it. A bedbank room you never sell costs you nothing.

So the rules that hold up look more like a precedence order than a price sort:

  • While allotment is open and the release date has not passed, your contracted rate is the one shown for that hotel and those nights.
  • Once allotment is exhausted or released, the live rate takes over, with your normal markup.
  • For hotels you hold on free-sale, the contract leads until a stop-sale closes it, and the live feed is the fallback, not the competitor.

The other lever is markup by source. If your contracted net is close to the bedbank's net, a flat markup across both will sometimes put the bedbank on top. Pricing each source on its own terms keeps your contract competitive without giving margin away on every live booking. We went through how to set markup rules that survive a customer comparing tabs in the markup strategy piece; the same logic applies here, one level up the chain.

Rate parity is a contract clause, not a checkbox

Your hotel contract almost certainly says something about where your rate may appear. The usual shape: you may sell the net rate to the trade, but you may not publish it to the open public below the hotel's own public price, unless it is hidden inside a package. Bedbanks put similar terms on their wholesale rates. The wording varies by contract, which is the reason to read yours rather than trust a summary like this one.

What matters for the platform is that parity is enforced by where a rate is visible, not only by what it costs. Three practical consequences:

Your sub-agent channel should sit behind a login. A B2B rate that any visitor can see without signing in is, as far as a revenue manager is concerned, a public rate. The storefront can require sign-in before search and register agency customers with manual verification, which is the arrangement most contracts quietly assume.

Your public, traveller-facing site, if you run one, needs its own pricing. Not the B2B price with a smaller markup — a separate rule that respects the floor the hotel set.

And you need to be able to answer the hotel when it calls with a screenshot. Knowing which channel showed which rate, to whom, on what date, is what turns an awkward call into a short one.

Release periods and cut-offs belong in the engine

The release period is the date by which unsold allotted rooms go back to the hotel. The cut-off is how close to arrival you can still sell. A stop-sale closes dates before either. All three are dates, and all three are routinely managed in someone's head or in a spreadsheet that is current on Monday and wrong by Thursday.

That is fine at five hotels. At fifty, with sub-agents booking at night in three time zones, it is how you sell a room you no longer hold. Whatever engine you run, these are the questions to put to it:

  • Can a contract carry its own release period, per hotel and per season, and does the allotment stop selling on that date without anyone touching it?
  • Is the cut-off enforced at search time, so a sub-agent never sees a room it cannot book, rather than at confirmation, where it becomes an apology?
  • Does a stop-sale close the contract rate and fall back to the live feed, or does it remove the hotel from results entirely?
  • When allotment runs out, does the count stop at zero, or does it go negative and leave you to explain it?

If the answer to any of these is "your staff handle that", you have a spreadsheet with a booking engine attached, not the other way round.

What your sub-agents should never see

A sub-agent needs a price, availability, the cancellation terms, and a way to book. Almost everything else you hold is leverage you lose the moment it leaks.

Your net rate. They see their price, with your margin already in it. If they can reverse-engineer your net from the screen, so can the next consolidator they show it to.

The source. Which bedbank supplied a room, or that a rate is contracted at all. A sub-agent who learns the name of your wholesale supplier has learned where to open their own account.

Your allotment count. "Three rooms left" is fine as a sales nudge. "Three of the thirty we contracted" tells the market how big your commitment is and how worried you should be about it.

Each other. One agent's markup, credit line or booking history is nobody else's business.

This is where the structure of the platform matters more than any single setting. On ours, supplier content is shared through supplier groups rather than one-to-one deals, so a tenant only sees the suppliers its groups grant it, and each tenant has its own markups, bookings and reports. Credit limits and settlement invoicing for sub-agents are built into the same system rather than kept in a separate sheet — which matters, because the agent who is about to exceed their credit should be stopped at booking, not chased at month end. We covered that side of the loop in distributing net fares to sub-agents; hotels add the allotment problem on top of it.

What it costs when this goes wrong

The losses here rarely show up as one bad day. They accumulate.

Unsold allotment on a guaranteed contract is paid for whether or not a guest arrives. Rooms released unsold year after year teach the hotel that your block is too big, and the next contract is smaller or the rate is worse. A parity complaint can end a contract outright, and a revenue manager who has caught one leaked rate starts looking for the next. A sub-agent who finds out where your rooms really come from does not need you next season.

None of that is a software failure in the narrow sense. Each one is a rule that lived with a person instead of in the system, and the person was asleep, on leave, or simply busy when it mattered.

Before you choose a hotel consolidator platform

Write your rules down before you choose any tool: which source leads for which hotel, how each source is marked up, where each channel may show a rate, and what happens on the release date. If they fit on a page, a platform can enforce them. If they do not, no platform will fix that for you.

If you are setting up as a wholesaler and want sub-agents booking from their own B2B portal next to your public site, the consolidator account is the starting point: it lets you share your supplier content with a network and sell white-label sites to the agencies in it. Bring the page of rules with you. It is the most useful thing you will have.

Tekravel Editorial

Travel technology desk

The Tekravel travel-technology desk writes for the trade: agency owners, consolidators and the developers who integrate them. Every article is checked against the platform it describes before it is published.