The short answer
Availability and prices stay in sync when exactly one system holds the truth, usually the channel manager, and the portals and your own website read from it and report back to it. Overbookings almost always arise where someone still maintains rates by hand, or where a connection only updates on an hourly cycle. Your own booking flow is connected last, after a real test booking.
Key takeaways
- One source of truth for availability and prices; the next overbooking is usually caused by a second system that is maintained by hand.
- Real interfaces update within seconds; iCal connections update only at their polling interval and carry no prices.
- Set-up order: master data, rates, one portal, test, further portals, and finally your own booking flow.
- For outages, keep an emergency sheet at the front desk: who closes which portal, and with which login details.
- For a single unit on one portal, a channel manager rarely pays for its own costs.
Availability and prices only stay the same everywhere when a single system holds the truth and all others read from it. In practice that system is the channel manager: portals, booking flow and front desk report to it and draw from it.
Everything else is craft, and the errors that hurt in high season do not come from the software. They come from the places where someone else still maintains things by hand.
How the connection works technically
The channel manager holds three things per unit and per day: availability, price and booking rules such as minimum stay or arrival days. It sends these three quantities to each connected portal, and it takes in new bookings from there. If a booking comes in via Booking.com, it reduces availability and reports the new status to all other channels.
Your own website connects at the same point. The booking flow queries the free inventory, displays it and writes the booking back into the same system. Technically this happens through the provider's interface; Smoobu, for example, documents a public API with endpoints for properties, bookings and prices [Q1]. Before you choose a provider, open this documentation before you sign: anything not documented there cannot be connected later. How far you can set up your own booking flow alongside the Lodgify solution supplied is shown in the Lodgify connection to your own website.
Where overbookings actually happen
Three causes cover most cases. The first is the second place of maintenance: someone blocks a room directly in the portal extranet because it was quicker there. The channel manager knows nothing about it and opens the night again at the next sync.
The second is delay. Between a booking on one portal and the block on all others there is always a gap. With a real interface it is seconds; with an iCal connection, depending on the polling interval, minutes to hours. On a night with one last free unit, that is enough.
The third is the phone booking that nobody enters. It is the most common and the easiest to fix: every booking made by phone belongs immediately in the same system as all the others, not in the calendar on the wall.
Why iCal is too slow for availability
iCal connections are tempting because they are free and up in ten minutes. However, they only transmit occupancy periods, not prices, minimum stays or arrival rules. And they work on a pull basis: the receiving system fetches the file at a fixed interval set by the provider.
For a holiday apartment with a few bookings a year, that may be enough. Once several units run across several portals, the saved fee becomes an open flank. If you use iCal, use it for secondary channels with low occupancy, never for the channel that brings in most of your bookings.
Working through the figures for a 12-room property
A property with 12 rooms, three portals and its own website. Without a connection, the front desk opens four interfaces to enter a price change or a block. Assume ten minutes a day for this duplicate work. This is an assumption, not a measurement, so time it yourself for a week. That comes to around 61 hours a year (10 × 365 = 3,650 minutes).
Then there is the case that is not counted in minutes. An overbooking in high season means relocation to another property, the price difference there, transport, and a guest who writes a review. Use your own room rate for one night, add the difference to the alternative property, and for most properties you land in the range of several hundred euros per case. Two such cases a year would offset the running fee of a channel manager. Smoobu, for example, publishes its plans per property and month, staggered by contract term (accessed 20 September 2026) [Q2]. Compare this fee with the commission charged on every portal booking: Booking.com describes it as a percentage of the total booking value, whose level varies by country, property and the programmes booked [Q3].
Set up in this order
First the master data: units, categories, occupancy, facilities. They must be named in the channel manager exactly as in the portals, otherwise the assignments drift apart later. Then the rates: standard rate, non-refundable rate, long-stay rate, each with a clear rule and no special cases that exist only in someone's head.
Then connect a single portal and observe it for two weeks. Only when bookings, cancellations and changes arrive cleanly there does the second portal follow. Last comes your own website: your own booking flow with online payment goes onto the fully tested inventory, not onto a building site. Before switching over, make a real test booking with real payment and cancel it afterwards, because on paper every connection works.
What happens when the system fails
An outage is not an exception but an operating state, and there must be a sheet of paper for it. It lists the login details for each portal extranet, the order in which to close them, and the person who decides.
The rule itself is simple: if the sync fails and the property is tightly booked, close the portals by hand, starting with the largest. Your own booking flow stays open longest, because there you see for yourself what comes in. After restoration, do not simply carry on, but reconcile: which bookings came in during the outage window, are they all in the system, and is the inventory correct for the next 14 days? Whoever skips this check finds the error on the arrival day.
How to tell that the sync has quietly broken
A broken connection rarely announces itself. It shows up in small details that are easy to explain away. A portal has sent no booking for four days, although it usually sends several each week. A price change you entered on Monday still does not appear in the portal on Wednesday. The minimum stay in the extranet matches the rule from last season. Or a booking arrives as an email from the portal but does not appear in the occupancy plan.
Each of these is a reason to open the connection status in the channel manager and view the log of recent transfers. That log usually shows when the last successful transfer took place and what message the portal returned. Decide who in the property knows this log and reviews it once a week. It takes two minutes and replaces the gut feeling that business is simply quiet.
What you have to take care of yourself
Three things stay in the house. First, the discipline of working in only one system. That is a habit, not a setting, and it takes two to three weeks. Second, the pricing logic: which rate applies when, which surcharge applies to short stays, and when to block dates. No service provider can decide that for you.
Third, a monthly check: a test booking through your own site, a look at two portals, and a comparison of the next 14 days. Twenty minutes that find the silent error before it becomes expensive.
When it is not worth it
Anyone who rents out a unit through a single portal does not need a channel manager. Even with two holiday apartments and few bookings a year, the monthly fee is out of proportion to the time saved; here iCal and a tidy calendar are enough.
From three to four units, or from two portals, the ratio changes, and not because of the time saved but because of the case avoided. If you want to check whether your current set-up really avoids double maintenance, go through every channel once and note where a person can change availability. Use this list to plan the connection of your channel manager, and for Smoobu properties in particular the Smoobu connection to your own site, which first gives a direct booking website its inventory. Book a call.
Sources and further reading
Häufige Fragen
Do I need a PMS in addition to a channel manager?
Not necessarily. Smaller properties do well with a channel manager that holds occupancy, prices and guest data. A PMS becomes worthwhile once invoicing, cash register links, registration reporting and housekeeping come in. The decisive question then is which of the two systems leads on availability: two systems with the same role create exactly the double maintenance you want to avoid.
Can I show different prices on my own website than on the portals?
Technically yes, the channel manager allows separate rates per channel. Whether and to what extent you may do so depends on your contracts with the portals and on the law in force. That is a legal question which should be checked by a specialist before implementation, not one to try out in the extranet.
How long does it take to set up a connection?
The technical connection is often in place within a day. Preparation takes longer: standardising categories, tidying rates, checking portal mappings. Plan two to three weeks in total, as each step is observed before the next one follows. Anyone who switches all channels over on the same day cannot tell the errors apart afterwards.
What happens to bookings made before the switch-over?
They must be carried over into the new inventory, otherwise the system opens occupied nights. A common approach is a cut-off date: all confirmed bookings from that date are imported or entered by hand and then checked against the portal lists. Schedule this reconciliation before the first live opening, not after.
Talk to us
Direct booking, without the commission
We build the booking site, connect it to your channel manager and keep it running.
Book a first call