Setting it up
- In the Booking.com extranet: Rates & Availability → Sync calendars → Export calendar. Copy the
.icslink (it must end in.ics). - In Lemon: Properties → the property → add iCal feed → paste. Lemon detects Booking.com from the link.
- First sync immediately, then every 5 minutes.
What to expect from Booking.com's calendar
Booking.com's calendar link carries very little. Every guest booking, and every date you close yourself, shows as "CLOSED - Not available". There is no guest name, no reservation number and no status. Booking.com also changes bookings in its calendar more than Airbnb does. It can give a booking a new reference, shorten a stay that is in progress, or show two back-to-back stays as one.
What Lemon does for you
- Every booking gets a clean. Each entry is treated as a guest stay and a checkout cleaning job is created.
- Long closures are skipped. An entry longer than 30 nights is treated as you closing the property. No job, no message to your cleaner.
- Very long stays wait for you. A stay longer than 90 nights, even one with a guest name, is held for you to review.
- Changed references do not cancel anything. If Booking.com relists a booking under a new reference with the same checkout, your cleaner keeps the job.
- Shifting arrival dates are ignored. If a stay in progress looks like it starts a day later each day, the clean stays on the checkout day.
- Merged stays are handled. If a booking suddenly grows over a stay Lemon already knows, Lemon does not stretch the job. It tells you about any nights it cannot account for. If the entry later splits into real stays, the job moves onto the real booking.
- Disappearing bookings are checked, not cancelled. Lemon flags the booking and waits 24 hours (2 hours near checkout) before cancelling. It never cancels inside 24 hours of checkout on calendar evidence alone.
When to go beyond iCal
If you run back-to-back Booking.com stays or monthly stays, connect a PMS (Hospitable, Guesty, Hostaway) so reservations arrive as objects with names and statuses. Lemon deactivates the property's iCal feeds automatically when you do.
Technical details
What the feed carries. One summary for everything: CLOSED - Not available. No guest name, no reservation number, no status. A UID that changes when the surrounding availability changes shape. An in-progress stay re-exported daily with its elapsed nights removed. Two back-to-back stays sometimes exported as one block.
How each behaviour is handled, and the decision Lemon logs:
| Behaviour | Lemon's handling | Decision logged |
|---|---|---|
| Nameless block | Treated as a reservation; job created | — |
| Block > 30 nights | Owner closure; skipped | skip_owner_block |
| Stay > 90 nights even with a name | Held for host review | — |
| UID changes, same checkout | Re-linked to the existing booking | rekey_adopted |
| Check-in walks forward during the stay | Original check-in pinned | elapsed_checkin_pinned |
| Block widens over a tracked stay | Widen refused; unexplained nights surfaced | uncovered_surfaced |
| Block later splits into real stays | Placeholder promoted onto the real event | synthetic_promoted |
| Stay vanishes | Flagged; window 24h / 2h / never within 24h of checkout | auto_cancelled or imminent_protected |
Numbers. In the 30 days to 2026-09-10 across 9 Booking.com and 9 Airbnb feeds: 78 re-keys, 1,240 forward-trim pins, 10 auto-cancellations. Lifetime, Booking.com feeds withdrew 2.4× as many calendar events as Airbnb feeds. Source: feed integrity report.