Bug Report — Orphan nights auto-blocked instead of showing as unavailable

Availability and inventory control
Post Reply
living-essaouira
Posts: 1
Joined: Tue Jun 16, 2026 6:47 pm

When a 1-night gap exists between two reservations (orphan night), Beds24 automatically sends a hard block to Airbnb for that night instead of letting Airbnb handle it naturally as "unavailable due to minimum stay setting."

This causes several problems:

> The blocked night appears in Airbnb's calendar as "Blocked" instead of "Unavailable based on minimum stay setting"

> The block exports via Airbnb's iCal feed as a fake reservation event, polluting any external calendar that imports the feed

> Guests with existing reservations immediately before or after the orphan night cannot request to extend their stay, the night shows as blocked, not just restricted

> The host cannot manually extend an existing reservation to cover the orphan night, Beds24 prevents modification because it has auto-blocked the date

> The night is available in inventory but inaccessible to both guests and host

Please investigate and fix this behaviour for Per Occupancy Pricing, or provide an official setting to control how orphan nights are handled when pushed to Airbnb.
Post Reply