Calendar sync (iCal) or a channel manager? Why linked calendars still double-sell
iCal sync copies dates but not prices or restrictions, leading to double bookings. Learn the limits of calendar links and when to move to a channel manager or hotel system.
Contents
Key takeaways
- An iCal link carries blocked dates and, on Booking.com, the reservations behind them; it carries no prices, no restrictions, no room type mapping and no guest details.
- Booking.com automatically imports every connected calendar every two hours, offers a manual "Import now", and states that sync is not real time, so double bookings remain possible (Booking.com for Partners, 2026-11-04).
- Booking.com opens calendar sync only to properties that are open and bookable, have 20 room types or fewer, hold at most one unit per room type, and do not use a connectivity provider (same source).
- A room type with several rooms cannot be expressed by one blocked date, and that gap is a common starting point for double sales at small properties.
- The durable fix is one inventory that feeds every channel, not more calendars talking to each other.
iCal sync is a calendar link that copies blocked dates between two booking platforms. It carries dates only: no prices, restrictions or guest details. Booking.com's partner help page (opens in a new tab) says it imports every connected calendar every two hours and that sync is not real time, so two guests can still book the same night (Booking.com for Partners, 2026-11-04).
A guest books your last room on one site at 21:10. On the other site the same night still shows as free, because the calendar link has not run yet. The second booking lands before the first one is even visible. If you run a pension, a boutique hotel or a small apart hotel and you have linked your booking-site calendars because it was free, this article explains what that link actually does, what it cannot do, and how to tell when it has stopped being enough.
What is iCal sync, in plain words?
iCal sync is a link between two online calendars that copies booked and closed dates from one platform to the other, so a night sold on one site shows as unavailable on the other.
iCal, short for iCalendar, is a plain file format for calendar entries. A sync link is a private web address that returns that file whenever a platform asks for it. Each platform gives you two things: an export link for its own calendar, and a box where you paste someone else's import link. A pair of platforms therefore needs two links, one in each direction.
A one-way link only blocks one side. If you import the booking site's calendar into your own tool but never export back, the booking site keeps selling. What the link replaces is a phone call or a manual close of dates. It is a calendar, not a booking system: it does not know rooms, rates, policies or guests.
It fits a small property with one unit behind each room type, selling on two or three sites, where someone is present most of the day to watch it.
Key pointiCal sync copies dates, not inventory
It answers one question, is this night taken, and answers it late.
What does an iCal link carry, and what does it leave out?
It carries dates that are already blocked, and on Booking.com also the reservations behind those dates. It carries nothing about price, policy or guest.
The receiving platform sees a blocked night, not a booking. It cannot tell a cancellation from a new reservation until the date changes back. Restrictions are the biggest omission: a three-night minimum, a closed-to-arrival rule or a maximum-stay limit never travels through the link.
There is no field for room type mapping, so the receiving side has no way to know which of its room types corresponds to the blocked one. No guest name, contact or payment status crosses the link, so you cannot reach the guest from the other platform, and neither can it reach yours. Rates are untouched: two channels can show different prices for the same night and the link will never notice. A blocked date is binary: it says not available, never how many are left.
| What the link carries | What the link never carries |
|---|---|
| Booked and closed dates | Prices and rate plans |
| On Booking.com, reservations and closed dates imported from the external calendar | Minimum stay, closed-to-arrival and other restrictions |
| A short summary line, often a reservation code or the word CLOSED | Room type mapping |
| Occupancy limits | |
| Guest name, contact and payment status | |
| Cancellation and modification reasons |
How often does iCal sync run, and who sets the delay?
Each platform sets its own import interval. Booking.com's partner help page says it imports every connected calendar every two hours, and that sync is not real time (Booking.com for Partners, 2026-11-04).
Two hours is an interval, not a promise. The clock runs from the platform's last import, and a manual "Import now" button exists for the moment you cannot wait. The delay is per hop: the booking lands, the exporting platform writes the file, the importing platform runs its next import, its calendar updates. Each side adds its own time.
The export side is rarely documented the same way. Assume it is not instant, and check each platform's own help page rather than a blog post, including this one. The exposure window is the gap between a booking and its arrival on the other channel. Any reservation made inside that window is invisible to the other site.
Risk concentrates at the last room, on the same night, at weekends and around holidays, when two bookings can land minutes apart. Some platforms let a host export a calendar to other sites; check each platform's own help page for its timing and limits. For a picture of how a direct channel connection behaves instead, see how a channel manager connection works.
Watch outA linked calendar is a record, not a live picture
A linked calendar records what already happened, not what is available now. Never confirm a last room on the strength of a calendar that has not run since the previous booking.
Why does iCal work for one unit but not for a room type with several rooms?
A blocked date can only say this unit is taken. When one room type holds five rooms, one booking cannot block the type, and the link has no way to show that four rooms are still free.
Booking.com's own eligibility rule makes the mechanism visible: calendar sync is open only to properties with 20 room types or fewer and at most one unit per room type, and not to properties using a connectivity provider (Booking.com for Partners, 2026-11-04). With several units behind one type you face a choice with no good answer: block the whole type after the first booking and lose sales, or leave it open and risk selling the same room twice.
Mapping is the second failure. The receiving platform has its own room type names, and a link has no field to say which name means which room. Pensions and apart hotels with several identical studios meet this first, because their inventory looks like one type with many units.
The last-room race is the third: two channels, one remaining room, both calendars still open, both guests paying. If you genuinely have one unit per room type, the link is a reasonable tool. If you do not, the risk is structural, not a matter of being more careful.
What routine keeps a linked calendar safe in the meantime?
Treat the link as a backup, not a control: close dates by hand on every channel the moment a booking lands, and check the calendars at fixed times each day.
Keep one master calendar, on paper, in a spreadsheet or in your own system, and make it the record of what is actually sold. After every booking, press the manual import on the other platform instead of waiting for the interval. Close the dates by hand on any channel you cannot import into, and write down that you did it.
Check every calendar at opening, mid-afternoon and close, and note the time of the last check. When you are down to the last unit, close the other channels first and reopen them if the room is still free at the end of the day. Log every double booking and every near miss with the time, the channel and what each calendar showed; the log tells you when the tool has stopped being adequate. For the wider picture of why this happens, see hotel double bookings across channels.
Checklist
- Master calendar updated after every booking
- Manual import pressed on the other platform after each booking
- Dates closed by hand on non-linked channels
- Three calendar checks completed, with the last check time noted
- Last unit protected: other channels closed first
- Double bookings and near misses logged with time and channel
- Guest contacted the same day after any incident
- Monthly review of the log
When should you move to a channel manager or one hotel system?
Move when more than one unit sits behind a room type, when you sell on more than two or three channels, or when your rates and restrictions change often enough that a calendar cannot keep up.
A channel manager holds availability and rates in one place and pushes changes to each channel over a direct connection the platform authorizes, so an update arrives in seconds or minutes rather than on a two-hour cycle. It does not remove the work: room types must still be mapped correctly, and anyone who edits availability by hand in the extranet can still break it.
Clear signals to move: several identical units, weekly rate changes, minimum-stay rules, seasonal closures, more than two or three channels, or no staff member who can check calendars three times a day. Before signing anything, work through how to choose a channel manager, and to place the roles correctly, read PMS vs channel manager vs booking engine.
A single hotel system goes one step further: reservations, front desk, housekeeping, billing and distribution share one inventory, so the room that is sold is the room that is blocked. The trade-off is a monthly cost against the cost of one double booking: a relocated guest, a refund and a review that stays public. Weigh it with your own numbers, not with percentages from a vendor.
AI Otel's hotel operating system is built so that one room inventory feeds the hotel's own website, OTAs, travel agencies and AI assistants at once; it is built and working, ahead of launch. Booking-site connections through our Channex integration are in pre-production testing, and no booking site is connected yet.
What to do next
Do a short inventory audit today: write down every room type you sell on every channel and how many units sit behind it. If any type holds more than one unit, plan the move off iCal before the next high season, because the link cannot express what you are selling. If every type holds exactly one unit, keep the link and run the daily routine until the property grows. If you want to see what one shared inventory looks like in practice, request a briefing.
Frequently asked questions
Does iCal sync work with Booking.com?
Yes, for eligible properties. Booking.com's partner help page says calendar sync is open to properties that are open and bookable, have 20 room types or fewer, hold at most one unit per room type, and do not use a connectivity provider. It imports every connected calendar every two hours and also offers a manual import (Booking.com for Partners, 2026-11-04).
Can I use iCal sync and a channel manager at the same time?
On Booking.com the two are mutually exclusive by its own eligibility rule: properties using a connectivity provider are outside calendar sync. Running both also creates two writers to the same calendar, and the slower one can overwrite or contradict the faster one. Choose one method per room type.
Does an iCal link send my prices and minimum-stay rules?
No. It carries blocked dates and, on Booking.com, the reservations behind them. Prices, rate plans, minimum stay, closed-to-arrival and occupancy limits stay in each platform's own extranet and must be maintained separately on every channel.
What should I do if two guests book the same night anyway?
Contact both guests the same day, before they travel, and be straight about the situation. Keep a written record of the times and what each calendar showed, because it shows whether the cause was the import interval, a mapping error or a manual mistake. Confirm your own obligations in such a case with your legal adviser.
Is iCal sync enough for an apart hotel with several identical studios?
No. Several units behind one room type is exactly the case the mechanism cannot express, and it is also outside Booking.com's one-unit-per-room-type eligibility rule. Either block the whole type after each booking and lose sales, or move to a channel manager or a single hotel system that holds the real count.
Sources
- How to synchronize your calendars across channels (Booking.com Partner Help) (opens in a new tab)Booking.com for Partners (Partner Hub)partner.booking.com