Syncing Booking.com and Agoda calendars so a room never sells twice
HostBooking · · 7 min read
Booking.com and Agoda both support iCal, but only for room types with exactly one unit. If you sell individual homes, a direct link is enough; Booking.com re-reads outside calendars every 2 hours, Agoda does not publish its interval. With several identical rooms you need to split room types, divide rooms between channels, or use a channel manager.
Where this pair gets stuck
Booking.com and Agoda both work like hotel systems: a room type can hold several identical rooms. iCal only knows "busy" or "free" for a night, not "2 of 4 left". So both OTAs restrict iCal to single-unit room types. For an owner with four identical doubles, that is the first obstacle, before delays even come into it.
| Booking.com | Agoda | |
|---|---|---|
| Where the link lives | Extranet → Rates & Availability → Sync calendars | Partner portal (YCS) → Calendar → Calendar connections |
| Conditions | Up to 20 room types, one unit each, no connectivity provider | Eligible room types (one room); deactivated if changed to several |
| Refresh of imports | Every 2 hours, plus Import now | Not published |
| Connection status | Activating, Okay, Import only, Export only, Service error | Shown in Calendar connections |
Three options for identical rooms
- Split room types: turn a 4-room "Double" into four single-room types ("Double 101", "102"…) on both OTAs, then link each pair. Booking.com allows up to 20 types, enough for most homestays. Downside: guests see several near-identical types, and you edit prices per type.
- Divide rooms by channel: sell 101 and 102 only on Booking.com, 103 and 104 only on Agoda. No iCal link between the OTAs is needed and they can never clash. The cost: one channel may sell out while the other still has rooms.
- Channel manager: connects to both OTAs directly, sends the number of rooms left rather than busy/free, and usually rates too. Booking.com states that properties using a connectivity provider cannot use iCal sync.
Direct link or a central calendar
For single-room homes, a direct Booking.com ↔ Agoda link works. With a central calendar each OTA imports one link from your software. Software like HostBooking keeps the real room count of each type: its export marks a night busy only when the whole type is full, and it offers a link for each room when every room is its own type on the OTA. Website, phone and walk-in bookings then block both OTAs as well. HostBooking also reads booking emails from both Booking.com and Agoda, so new bookings often land before the next calendar read.
Linking directly (single-room types)
- On Agoda: Calendar → Calendar connections, find the room type, click Copy calendar link.
- On Booking.com: Rates & Availability → Sync calendars, click Add calendar connection on the right room, paste the Agoda link, name it "Agoda", click Next step.
- Continue to the export part, name the connection and click Copy link for the Booking.com link. A correct link contains "/ical/".
- Back on Agoda, paste the Booking.com link into Other website link, name it, click Import.
- On Booking.com click Done, wait for the status Okay, then click Import now.
- Compare one real stay on both sides. Repeat for each room type.
What iCal does not carry
- Rooms left: only busy or free, which is why the one-unit rule exists.
- Prices and deals: Booking.com Genius rates and Agoda deal rates do not cross over.
- Cancellation policy, breakfast, occupancy: set on each OTA separately.
- Guest names: only in the OTA booking or its confirmation email.
Checklist against double bookings
- Room type names and order match on both OTAs, so room 101’s link never goes into room 102.
- Booking.com shows Okay, not Import only or Export only.
- Never raise the room count of a linked Agoda type.
- Moving to a channel manager? Remove every old iCal connection on both sides first.
- Same-day bookings: close that night by hand on the other OTA.
If a double booking still happens
Both OTAs expect the same: if another room is free, move the guest to an equal or better one at no extra cost. If not, you find comparable or better accommodation elsewhere and pay for it. Agoda requires you to provide transport; Booking.com advises it, or you may have to reimburse travel later.
The difference is commission: Booking.com still charges it on a double-booked reservation unless the property has been live under 30 days or has had no more than four double bookings in 12 months. Contact Booking.com support to mark the reservation as a double booking or report a relocation.
On HostBooking
OTA calendar sync reads Booking.com and Agoda every 5 minutes, counts against each type’s real number of rooms, and alerts you to double-booked nights. Pair it with booking email forwarding for guest names and prices. If you want to lean less on these two, see reducing reliance on Booking and Agoda. iCal basics are in the iCal sync guide; plans are on the pricing page.
Frequently asked questions
I have 3 identical rooms. Can I link Booking.com and Agoda by iCal?
Not while they share one room type: both OTAs only link single-unit types. Split them into three types, divide rooms between channels, or use a channel manager.
How often does Booking.com read the Agoda calendar?
Every 2 hours automatically, and Import now reads it at once. Agoda does not publish how often it reads the Booking.com link.
I use a channel manager. Should I add iCal too?
No. Booking.com does not allow calendar sync alongside a connectivity provider, and two sources editing one calendar cause errors. Pick one.
Who pays when Booking.com and Agoda double-book?
The property. Both OTAs expect you to move the guest to equal or better accommodation at your cost. Booking.com may also charge commission on the double-booked reservation.