Overbooking and channels that don't talk: hospitality loses money between Booking, the site and the phone

The room sold twice

There’s a recurring nightmare for whoever runs an accommodation — a hotel, a B&B, a guesthouse, a residence: the room sold twice. A Booking reservation arrives for that date, and shortly after another for the same period from your site, or on the phone, or on another portal. You don’t notice immediately, because the channels don’t talk and you update availability by hand. Then on arrival day you have two guests for one room, and the disaster starts: someone has to be moved, sent elsewhere, refunded, and — almost always — they leave a furious review that will cost you other bookings. Overbooking isn’t only lost revenue: it’s revenue plus reputation lost together.

The underlying problem is that hospitality today sells on many channels that don’t communicate with each other. There’s Booking, there are the other portals (the OTAs, Online Travel Agencies), there’s your site, there’s the phone, there’s the walk-in who shows up at the door, there’s WhatsApp. Each of these sells the same rooms, but if each has its own idea of availability — or if you update availability by hand on each, in a hurry, between one check-in and the next — it’s only a matter of time before two channels sell the same room. And in the meantime you also lose money the other way: rooms that stay empty because you forgot to reopen them on a channel after a cancellation.

This article is for whoever lives on hospitality and loses revenue and reviews between channels that don’t talk. Let’s see what a single calendar actually means (it isn’t a shared Excel sheet), what the customer has to see on your site, why managing prices and restrictions by hand is the recipe for getting it wrong, and — with honesty, because here it’s fundamental — when a ready-made channel manager is enough and when instead you need a custom piece.

OTAs, site, walk-in, WhatsApp: the channel chaos

Let’s line up the channels bookings can arrive from, because it’s the multiplication of these that generates the chaos. There are the OTAs (Booking and the other portals): they bring you lots of customers, but they take an important commission and “own” the customer. There’s your site, where bookings don’t cost you commissions and it’s the channel you’d like to push. There’s the phone, still very alive in hospitality. There’s the walk-in, whoever shows up in person. And there’s WhatsApp, more and more used to ask availability and book.

Each of these channels, if managed separately, is a source of bookings and a source of errors. Because every time you sell a room on one channel, you have to remember to take it off availability on all the others — or you risk selling it again. And every time a cancellation frees a room, you have to remember to reopen it everywhere — or you leave it empty. Doing this by hand, on five channels, while running a property, is impossible without getting it wrong: sooner or later you skip an update, and you pay with an overbooking or an unsold room.

The point is that the channels aren’t the problem — on the contrary, more channels means more customers. The problem is that they don’t talk. Each lives on its own, with its idea of availability, and you act as the human bridge between them, with all the errors a human bridge implies. It’s the same pattern of WhatsApp as a cable and not as a system that I talk about for bookings in general: the channel carries the message, but you need a system underneath that holds the single truth of availability.

The bill: overbooking and commissions

Let’s put some numbers, declared as estimates but easy to redo on your property, because “you lose money between the channels” stays vague until you tie it to euro. The cost hides in three items.

Overbooking: every room sold twice is a guest to relocate (sometimes paying a more expensive property out of your pocket), a refund, and — the most expensive item — a negative review that will cost you future bookings. Even only a few overbookings a year, between direct costs and reputational damage, easily add up to thousands of euro.

OTA commissions: the portals take an important percentage on every booking — often 15–20%. On room revenue of, say, €200,000 a year with 80% of bookings via OTA, that’s tens of thousands of euro in commissions. Every booking you move from the OTA to your direct site is that percentage saved: recovering even only a slice of direct is worth a lot.

Item	Estimate
Overbooking (relocations, refunds, reviews)	thousands of €/year
OTA commissions (15–20% on most of revenue)	tens of thousands of €/year
Unsold rooms from missed update after cancellations	invisible lost revenue

The third item, invisible, is unsold rooms: when a cancellation frees a room and you forget to reopen it on the channels, that night stays empty — lost revenue you don’t see. Adding overbooking, commissions and unsold rooms, the chaos of channels that don’t talk isn’t “a nuisance”: it’s a consistent slice of your margin. And it’s the same kind of measurable, attackable hole I talk about for everything that revolves around bookings and scheduling: once you quantify it, the decision to solve it makes itself.

The single calendar: it isn’t an Excel sheet

The solution has a name: single calendar. But watch out, because “single calendar” is immediately misunderstood as “a shared Excel sheet where we mark the bookings”. It isn’t that, and understanding the difference is everything. A sheet is passive: someone writes on it by hand, and it’s only valid as long as everyone remembers to update it — that is, you’re back to the human bridge, with the same errors.

The real single calendar is a system that is the single source of truth of availability, and that syncs automatically with all the channels. When a booking arrives from Booking, the calendar records it and takes that room off availability on all the other channels, in real time, on its own. When you sell on the phone, you mark it once in the calendar and it disappears from all the portals. When there’s a cancellation, the room reopens everywhere, automatically. Nobody acts as a hand bridge: the system keeps all the channels aligned, always.

This is what eliminates overbooking at the root: not “being more careful” (impossible by hand), but removing the very possibility of selling twice, because there’s one truth of availability and all the channels respect it. It’s the same single source of truth principle that holds everywhere in data: as long as availability lives in five different places updated by hand, errors are guaranteed; when it lives in one place that feeds everyone, they disappear. The single calendar isn’t a sheet: it’s the engine that keeps the channels synced.

What the customer sees on YOUR site: real availability

A piece that’s worth direct revenue: what happens when a customer tries to book on your site. Because your site is the channel you love — no commissions, your customer — but it only works if it shows real availability and lets them book for real, immediately. If on your site the customer sees “contact us for availability” or a form that sends you an email you answer hours later, you’ve lost: that customer, while they wait, books on Booking (where availability is certain and confirmation immediate), and you pay the commission for a customer you could have had for free.

With the single calendar underneath, your site can show real availability in real time and let them book and pay on the spot, with the same certainty as an OTA — but without commission. The customer picks the dates, sees the rooms that are actually free (because the site reads from the single calendar), books, gets confirmation. And that booking enters the calendar and takes the room off all the other channels, like the others. Your site becomes a real sales channel, not a showcase that sends people to the phone — the same difference as a site that makes things happen and one that only shows them.

Pushing direct bookings on your own site is, for a property, one of the most effective ways to increase margin: every direct booking is an OTA commission saved. But it only works if the experience on your site is at least as good as the one on Booking: real availability, immediate booking, secure payment. A site that doesn’t show real availability isn’t a channel, it’s a leaflet.

Prices and restrictions: if they’re by hand, you get them wrong

Beyond availability, there’s a second level that, if managed by hand, makes you lose money and errors: prices and restrictions. In hospitality prices aren’t fixed: they change by season, by day of the week, by events, by how full you are. And there are restrictions: minimum stay in certain periods, closed arrivals on certain dates, special offers. Managing all this, on all channels, by hand, is a nightmare that generates two types of error: wrong prices (you sell at an old price, you lose margin, or you put an absurd price and you don’t sell) and restrictions not applied (you accept a one-night stay when you wanted a three-night minimum).

A serious system lets you manage prices and restrictions once, in one place, and propagates them on all channels. You change the price for a weekend with an event, and it changes everywhere; you set the minimum stay for high season, and it holds on all portals. Some systems get as far as suggesting prices based on occupancy and demand (revenue management), but even only managing them in one place and propagating them without errors is already a huge gain versus doing it by hand on five channels. Because every wrong price is lost margin, and every skipped restriction is a stay you didn’t want at conditions you didn’t want.

The rule is the same as availability: one source of truth, propagated everywhere, instead of five updates by hand. Prices and restrictions done by hand on many channels aren’t “a bit more work”: they’re guaranteed errors that cost margin.

When a channel manager is enough (often)

Now the honesty I owe you, and in hospitality it’s particularly important: for most properties, a ready-made channel manager is the right solution. The “channel manager” is exactly the software category that does what I described: single calendar, automatic sync with the OTAs, management of prices and restrictions propagated on the channels, often with a booking engine for your site. It’s a mature market, with proven products, at a monthly cost accessible even for a small B&B. It would be stupid — and I say this even though I build custom software — to have a channel manager built from scratch when excellent ready-made ones exist.

When is the channel manager enough? When you run a property (or a few) in a fairly standard way: rooms, rates, the usual channels, a booking engine on the site. In that case, a good ready-made channel manager gives you 90% of the value — end of overbooking, synced availability, propagated prices, direct bookings — at a fraction of the cost of any custom. Take one, configure it well, and concentrate energy on hospitality. The message of this article — stop losing revenue and reviews between the channels — for most properties is realised by choosing a channel manager well, not by building software.

Just watch two things when you choose: that it actually covers the channels you use (and keeps them updated when the OTAs change the rules, which they do), and that it gives you a decent booking engine for your site (to push direct). With those checks, you avoid the most common traps.

When you need a custom piece

And so when does something custom make sense, on top of the channel manager? When you leave the standard cases ready-made products cover. Some concrete scenarios:

You sell experiences, not only rooms. If you offer packages, experiences, extra services, activities — things that have to be booked, combined, sold together with the stay in particular ways — standard channel managers handle this complexity badly. Selling experiences tied to the room, with its rules, is often a custom piece on top of the channel manager.

You have more properties with shared logic. A small chain, more houses, more locations, with the need to manage them together, move guests between properties, have an overview, shared rules. Past a certain complexity, products designed for the single property creak.

You have a B2B or groups channel. If you work with agencies, companies, groups, tour operators, with contracts, allotments, negotiated rates — that’s a world consumer channel managers don’t cover well, and you often need a dedicated piece.

You want a customer experience that distinguishes you. If the booking and stay experience is part of your value (not an accessory), building it custom — maybe integrated with the channel manager for the channel part — makes sense. The rule is always the same: how much of your way of working sits in that 20% the ready-made doesn’t do? If the heart sits there (experiences, multi-property, B2B), custom is justified; otherwise the channel manager wins, and whoever pushes you to custom “always” isn’t looking at your interest.

Reviews and no-shows: the circle closes

There’s a circle that ties everything, and it’s worth closing it because it shows how the pieces hold together. Overbooking generates negative reviews (the guest who was moved or refunded is furious), and negative reviews lose you future bookings: less visibility on the OTAs, less trust on your site. So solving overbooking doesn’t only save today’s revenue, it protects tomorrow’s revenue through reputation. In hospitality, where reviews are everything, this circle is central.

And there’s the theme of no-shows and cancellations, which ties to what I wrote for whoever sells time and loses slots to no-shows: a room booked and not honoured is lost revenue, and deposit and cancellation policies (managed consistently on all channels) serve precisely to protect that revenue. A system that handles availability, prices, restrictions and cancellation policies well, consistently on all channels, closes the circle: less overbooking → fewer negative reviews → more bookings; fewer no-shows → more actual revenue. The pieces aren’t separate: they’re a system, and the value comes from holding them together.

A typical case: from the human bridge to the single calendar

A typical profile, architectural, no names. An accommodation sold on Booking, on a couple of other portals, on the phone and with a site that only had a “request availability” form. Availability was kept by the owner, updating it by hand on the various channels between one task and the next. Overbookings happened — not often, but enough to leave a few terrible reviews and to cost refunds and stress. And the site sold nothing: whoever arrived there, not finding immediate booking, went to Booking, and the property paid the commission.

What was done — starting, honestly, from a good ready-made channel manager. For the bulk of the need it was enough: single calendar, automatic sync with the OTAs (end of overbookings, because availability was one and it propagated), prices and restrictions managed in one place, and a decent booking engine on the site to push direct. Only one piece was off-standard — selling some experiences tied to the stay, with particular rules — and that was built custom on top of the channel manager, not instead of it.

At regime, the difference wasn’t “we have software”: it was that overbookings disappeared (one truth of availability), negative reviews from a room sold twice ended, and the site started bringing direct bookings — OTA commissions saved, margin recovered. The owner stopped acting as the human bridge between the channels. The honest note: most of the value was given by the ready-made channel manager; custom was a targeted piece on the experiences, not the solution — for a standard property, the channel manager alone would have been enough.

It’s for you if / it isn’t for you if

It’s for you if: you run one or more accommodations and sell on more channels (OTAs, site, phone, walk-in) that don’t talk; you’ve had overbookings, or you lose time updating availability by hand everywhere; your site doesn’t sell because it doesn’t show real availability; you sell experiences, you have more properties or a B2B channel that standard products handle badly (for custom).

It isn’t for you if: you run a property in a standard way and you don’t yet have a channel manager — in that case the first thing to do is take a good one (ready-made, accessible), not build custom; you have very few rooms you manage perfectly on a single channel; you don’t sell on more channels and you don’t have the sync problem. For the majority of properties, the ready-made channel manager is the answer, and saying so is part of the job.

Frequently asked questions

How do I eliminate overbooking? With a single calendar that is the single source of truth of availability and syncs automatically with all the channels: when you sell on one channel, the room disappears from all the others in real time. Overbooking isn’t solved by “being more careful” (impossible by hand on five channels), but by removing the very possibility of selling twice. A channel manager does exactly this.

Isn’t the “single calendar” a shared Excel sheet? No. A sheet is passive: it’s only valid as long as everyone updates it by hand, that is you’re back to the human bridge with the same errors. The real single calendar is a system that syncs automatically with the channels: it records bookings from everywhere and propagates availability on all of them, without manual intervention. It’s the engine that keeps the channels aligned, not a file.

Is a ready-made channel manager enough? For most properties, yes, and it’s the right choice: it’s a mature, accessible software category that does single calendar, OTA sync, prices/restrictions and a booking engine for the site. Custom is only needed if you sell complex experiences, have more properties with shared logic, or a B2B/groups channel. Check that it covers your channels and gives you a good engine for the site.

Why should I push bookings from my site? Because every direct booking is an OTA commission saved — pure margin. But it only works if your site shows real availability and lets them book and pay immediately, with the same certainty as Booking. With the single calendar underneath, the site can do it. A site that sends people to the phone or an email isn’t a sales channel: it’s a leaflet, and in the meantime the customer books elsewhere.

And prices and restrictions? They have to be managed in one place only and propagated on all channels: you change a price or set a minimum stay once, and it holds everywhere. Doing it by hand on five channels generates guaranteed errors — wrong prices (lost margin) and restrictions not applied. A good system takes this work and these errors away; some also suggest prices based on demand.

How much do reviews matter? A lot: overbooking generates furious reviews (the guest who was moved or refunded), and negative reviews lose you future bookings. Solving overbooking doesn’t only save today’s revenue, it protects tomorrow’s through reputation. In hospitality, where reviews decide visibility, this circle is central.

When does custom make sense? When you leave the standard cases: you sell experiences and packages with particular rules, you manage more properties with shared logic, you have a B2B/groups channel with contracts and allotments, or you want a customer experience that distinguishes you. In these cases custom (often on top of a channel manager for the channel part) is justified. For a standard property, no: ready-made is enough.

Where do I start if I have nothing? From a good ready-made channel manager: it solves the bulk (overbooking, sync, prices, booking engine) at contained cost and in fast times. Only afterwards, if you have off-standard needs (experiences, multi-property, B2B), you evaluate a custom piece on top. Starting by custom-building what a channel manager already does is a waste.

In one line

If your property sells on more channels that don’t talk — Booking, other portals, site, phone, WhatsApp — updating availability by hand is the guaranteed recipe for overbooking: the room sold twice, which costs you revenue and reviews. The solution is a single calendar (not a sheet: a system that syncs the channels automatically), a site that shows real availability and lets them book immediately (commissions saved), and prices/restrictions managed in one place and propagated everywhere. And the honesty: for most properties a good ready-made channel manager is enough; custom is only needed for experiences, multi-property or B2B.

If you lose revenue and reviews between the channels and you want to understand whether a channel manager is enough or you need a custom piece, look at the projects I’ve built or drop me a line: we start from your real channels and from what you sell besides rooms, not from a demo.