The two platforms differ
- Airbnb exports guest stays as
Reservedand your own blocks asAirbnb (Not available). Lemon reads the label and files blocks asblocked— no cleaning job, no cleaner notification. - Booking.com exports everything as
CLOSED - Not available. There is nothing to read.
So the same real-world action — you close the 1st to the 7th on both platforms for maintenance — produces a blocked row from the Airbnb feed and a confirmed reservation from the Booking.com feed. Lemon's cross-feed de-duplication catches this when the dates match exactly; a one-day difference on either side is enough to defeat it. This is documented as a fundamental ambiguity, not a bug to be "fixed" into a regression.
What Lemon does with a Booking.com block
- Treat it as a reservation by default. Missing a real checkout costs far more than one unnecessary visit.
- Skip it as an owner closure if it is longer than 30 nights with no guest name.
- Hold it for review, never auto-confirm, if it is longer than 90 nights even with a name.
- Skip a short tail (up to 3 nights) that sits directly against an owner closure.
- If a block looks like a merge of stays Lemon already tracks, protect those stays and surface any unexplained nights as a question.
What a host can do
- If you block dates on Booking.com for yourself, dismiss the resulting job on the dashboard. Dismissing cancels the cleaning job and tells the cleaner; it does not touch the platform.
- Better: block the dates on Airbnb too, with the same dates, so Lemon can pair them.
- Best: connect Hospitable, Guesty or Hostaway directly. The PMS knows the difference and says so.