Many OwnerRez users who connect to Airbnb via API are experiencing a significant operational issue: Airbnb is sending guest-selected arrival times (often earlier than the property rule), and OwnerRez automatically applies those times to the booking without host approval.
This is not an approved early check-in — it is simply the guest’s chosen arrival time during booking or modification. But when Airbnb sends that “arrival_time” field through the API, OwnerRez treats it as an actual check-in time and overwrites the default (e.g. 4 PM).
For hosts with multiple properties, automated workflows, and PMS-level operations, this creates serious problems:
Cleaners and caretakers see incorrect check-in times
Turnover schedules break
Door codes and access automations may trigger too early
Messaging sequences become inconsistent
Guests believe their early arrival time is approved when it isn’t
Staff gets confused and may show up at wrong times
The host loses control over one of the most important rules: check-in time
OwnerRez already has several discussions and feature requests around early/late check-in (tags, ribbon indicators, upsell triggers, flexible editing), but none of them address the underlying issue: channel-submitted check-in/out times need host approval before they override OR defaults.
Feature Request: Channel-Override Protection for Check-In/Out Times
I am requesting a new OwnerRez setting that would prevent Airbnb (or any channel) from overriding property-level check-in/out times, unless explicitly approved by the host.
Suggested options:
Option A — Global or per-property toggle:
“Always enforce OwnerRez property check-in/check-out times; ignore arrival/departure times from channels.”
When enabled:
OR uses property default times (ex: 4 PM / 11 AM)
Channel-submitted arrival times never override those defaults
The guest’s selected arrival time is stored as a note but does not change the check-in time unless the host accepts it
Option B — Arrival-Time Approval Mode:
If a channel sends a non-default check-in/out time:
OR flags the booking
OR does NOT apply the new time
Host receives an “Accept / Reject / Reset to Default” action option
Messaging, locks, and cleaning continue to use the default time until the host approves the change
Option C — Triggers & Alerts:
Trigger conditions when:
A booking imports with a non-standard check-in time
A channel modifies arrival/departure times
Allow actions like:
Email/SMS alert
Add a tag
Prevent lock-code generation until confirmed
Why This Is Needed
This protects OR users from unintentional operational disruptions caused by Airbnb’s behavior. Airbnb allows guests to select arrival times freely, and Airbnb sends them via API as if they were confirmed. Without protection, this breaks workflows for:
Automated lock scheduling
Automated messaging
Cleaning teams
Inspector timing
Guest expectations
Multi-property turnover management
OwnerRez is intended to be the “system of record” and the single source of truth. But currently, channel-submitted check-in/out times can silently override crucial booking fields.
What Success Looks Like
No channel can overwrite check-in/out times unless the host explicitly approves
Turnover, messaging, locks, and cleaners always follow OR defaults
Guest-selected arrival time becomes what it should be: a request, not an authoritative booking change
Hosts maintain full control over check-in/out rules
Multi-property operators regain reliability in their operations
Thank you for considering this. I encourage other hosts who want tighter control over check-in/out times to comment and vote.
