One calendar for every channel
Channel managers keep availability identical across platforms. The own website is often missing from that chain. We attach it as a full channel: what is booked there is gone everywhere, and vice versa.
What is synchronised
Availability
Per room type or unit, including blocked days.
Rates and restrictions
Nightly rates, minimum stay, arrival and departure days, extra-guest charges.
Bookings
Every direct booking is written to your system with its payment status.
Cancellations and changes
Applied in both directions.
Events
New bookings can trigger pre-arrival messages or upsell offers.
Safeguards
Short caching, a live check before every booking, an enquiry form if the API is down, and automatic alerts.
How a booking travels through the systems
A guest picks dates on your website. Before the form even appears, we ask your system for the current availability rather than trusting a cached copy, so nobody fills in a form for a room that went yesterday. The moment payment is authorised, the booking is written back to your channel manager or PMS, which closes those nights on Booking.com, Airbnb and every other channel within its usual sync window.
The guest gets the confirmation from your system, in your wording, and the reservation appears in the same list your team already works from. Nobody copies anything by hand, and the front desk does not have to learn a second tool.
What goes wrong without it
Double bookings
Two guests hold the same room because the website calendar lagged behind the platforms. Someone has to be moved or compensated.
Rate drift
Prices are raised on the platforms and forgotten on the website, so the channel you want to grow is the one selling too cheaply.
Manual entry
Direct bookings typed into the PMS by hand: minutes per booking, mistakes at the worst moments, and no reliable numbers at the end of the month.
Invisible errors
A token expires, the sync stops, and nobody notices until a guest calls. We alert on the failure instead of on the complaint.
How the connection is built
We start with a test account or a sandbox of your system, map room types and rate plans, and compare what the website shows with what your system holds over several days. Only when the numbers match for every unit does the booking path go live.
Some systems limit how often availability may be requested. We work within those limits with short caching and a final live check at the booking step, so the calendar stays fast without ever selling a night twice.
If a system offers no open interface, we say so before a contract, rather than building a workaround that breaks with the next update.
Frequently asked questions
Is the integration included?
Yes, one system is included in both packages. Additional systems are quoted by effort.
Are you an official partner of these vendors?
We use the publicly documented APIs. We only claim a partnership where one exists.
Can we switch channel manager later?
Yes. The website stays; only the integration is replaced. Plan a few days for mapping and testing, and keep both systems running until the numbers match.
How long does the integration take?
For a documented system with a clean room and rate structure, usually one to two weeks including testing. Houses with many rate plans, packages or seasonal rules take longer, because every combination has to be checked against the live system.
What happens if the channel manager is unavailable?
The website keeps working. The booking path switches to an enquiry form, the guest gets an immediate confirmation of receipt, and your team receives the request by email. We are alerted at the same time, so the fix does not depend on a guest complaining.
Do we still need the platforms at all?
Usually yes, and that is fine. Platforms bring guests who do not know your house. The point of the integration is that those guests can come back through your own channel later, without the commission, while the calendar stays correct everywhere.