Ghost Booking Guide
Airbnb Ghost Bookings in PMS Workflows
Ghost bookings usually mean the imported state no longer matches the source truth. This guide is for phantom blocks, duplicate-looking reservations, and stale availability that keeps reappearing.
What counts as a ghost booking
A ghost booking is any imported block or reservation that cannot be reconciled with the current Airbnb source state.
The goal is to isolate whether you are seeing stale imports, duplicate interpretation, or a cleanup problem in the PMS.
Ghost booking patterns
Blocked nights remain after the Airbnb stay changed or disappeared.
A duplicate-looking event keeps reappearing after sync.
Support cannot reproduce the issue consistently from OTA dashboards alone.
Why ghost bookings appear
Stale upstream exports, duplicate event interpretation, and weak cleanup logic can all produce phantom availability states.
Without a controlled import and timeline comparison, it is hard to tell whether the ghost booking is coming from Airbnb or your PMS.
Ghost booking isolation workflow
-
Step 1
Import the Airbnb source in isolation
Use a dedicated test calendar for the Airbnb feed so the source state is easy to inspect.
-
Step 2
Force a sync and review history
Compare current imported state against what support reports in the PMS.
-
Step 3
Check for repeated or stale patterns
Look for duplicate windows, stale blocks, or changes that were not cleared.
-
Step 4
Validate downstream cleanup
If Airbnb looks clean in iCal Tester, move to the PMS logic that persists or clears imported events.
Ghost booking diagnosis
| Observed issue | Likely cause | Where to inspect |
|---|---|---|
| Block persists after source removal | Cleanup failure | PMS persistence logic |
| Same stay appears twice | Duplicate import interpretation | Source UID handling and dedupe rules |
| Issue appears only sometimes | Stale export timing | Forced sync timing versus upstream changes |
Ghost booking checklist
- Use a dedicated Airbnb test calendar.
- Compare current source state with imported state.
- Check whether stale records are being cleared.
- Validate deduplication assumptions after each import.
Run it live
Need to reproduce the mismatch with source evidence?
Import the Airbnb feed in isolation and confirm whether the ghost booking is already present before debugging the PMS.
Reproduce My Airbnb MismatchFAQ
What is a ghost booking?
It is a blocked period or reservation that appears downstream but does not match the current source truth in Airbnb.
Can stale exports create ghost bookings?
Yes. If an upstream export lags behind source changes, downstream systems can continue showing outdated availability.
How do I know whether the issue is deduplication?
Compare the imported events and visible timeline state after a fresh sync. If the source looks clean but duplicates remain downstream, inspect UID and dedupe handling.
Related guides
View the full guide libraryAirbnb Guide
Airbnb iCal Not Syncing? How to Debug It
Debug Airbnb iCal sync by importing the live export, forcing a sync, and comparing blocked dates before stale availability causes an overbooking.
Validation Hub
Ultimate Guide to iCal RFC 5545 Validation for Property Management
Comprehensive hub for OTA and PMS teams: RFC-aware validation workflow, behavior checks, and linked cluster guides for sync troubleshooting.
Workflow Guide
PMS OTA Sync Workflow for Reliable iCal Imports
Build a repeatable OTA and PMS sync workflow with source isolation, observability, and blocked-date verification.