✓ US hosts with one to five rental units
✓ Readers comparing booking systems and direct-booking routes
✓ Operators who can verify requirements before connecting live accounts
— Guaranteed occupancy or revenue forecasts
— Property investment or rental-law advice
— Enterprise hotel procurement
Do not erase the evidence
Capture the relevant reservation references, property, dates and the systems involved in an appropriate private record. Distinguish an actual accepted reservation from a stale display, inquiry or blocked period. Avoid deleting one record just to remove the visible overlap. That can hide the problem without resolving the guest commitment, payment or channel obligation behind it.
Escalate through supported channels
Contact the relevant provider or channel using its official support route and describe the exact discrepancy. Follow the account’s applicable policies. This article does not determine which guest should be moved, what compensation is owed or what legal obligations apply. Those decisions require the real contract and circumstances, not a generic software comparison.
Limit further confusion
Assign one person to coordinate changes and another responsible contact for guest communication if available. Record actions already taken so a teammate does not repeat a cancellation or refund. Do not promise a resolution before the facts are established. If an action times out, reconcile its result rather than assuming it failed and submitting it again blindly.
Review the cause afterwards
Once the immediate situation is handled, inspect mapping, connection status, manual changes and the timing of updates with the provider. An integration can reduce coordination work without making failure impossible. Lodgify’s synchronization explanation acknowledges potential exceptions. Do not turn one incident into a universal product verdict, but do update your own verification and recovery checklist from supported evidence.
Avoid duplicate recovery actions and reduce risk
Keep a single incident note with the original references, confirmed facts, actions already attempted and the person coordinating the next step. An action marked unknown stays unknown until reconciled. This protects against two teammates independently repeating a cancellation or payment request. It does not establish which contractual remedy is appropriate; obtain that answer from the relevant provider and applicable agreement.
Where the safety evidence stops
This guide draws on Lodgify two-way calendar sync: exceptions remain possible. Merchant-controlled records describe the provider’s own capabilities, terms or standards; they do not independently validate those claims. These records do not establish independent confirmation of the product claims.
Verify any current price, plan limit, label direction, compatibility rule, or commercial term that would materially change the decision. The dated source ledger shows the underlying records so this conclusion can be checked and updated.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Lodgify two-way calendar sync: exceptions remain possible — Merchant documentation · encyclopedia.lodgify.com · Merchant-controlled · checked 2026-09-19