Name the intended outcome
Are you reserving personal-use dates, cancelling a guest reservation or correcting an imported event? Write that down before acting. Each can affect availability and communication differently. Do not delete a visible calendar item simply because it resembles the thing you want removed. Follow the supported workflow for the record’s actual origin and the system that owns it.
Check every affected channel
After an authorized change, verify the receiving systems that should reflect it. Pay attention to dates that should remain unavailable as well as those that should reopen. An iCal feed and an API integration can have different timing and data boundaries. Do not infer completion from one calendar screen or promise immediate synchronization without provider evidence.
Keep guest obligations separate
A calendar becoming available does not establish that a guest was notified, a refund was processed or a cancellation condition was satisfied. Track those responsibilities separately with their owners. This publication does not advise on legal cancellation rights. The goal is to avoid losing non-calendar work behind the apparent simplicity of removing a rectangle from a date grid.
Retain the original reference
Keep the reservation or event reference and a record of the action in an appropriate private location. If the outcome is unclear, reconcile through the provider instead of submitting the same action repeatedly. A cautious recovery path is especially important when an action may already have completed. Do not replace an uncertain record with a new one merely to make the interface look tidy.
A three-state check
For a changed period, record what you intend the dates to mean: unavailable for owner use, available for sale, or reserved for a guest. Then inspect the supported receiving surfaces. Do not use the absence of one colored event as the sole proof of the intended state. Keep communication and payment tasks linked but separate so calendar cleanup cannot silently close them.
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 iCal integration — Merchant documentation · lodgify.com · Merchant-controlled · checked 2026-09-19
- Lodgify channel manager: merchant description, not reliability testing — Merchant documentation · lodgify.com · Merchant-controlled · checked 2026-09-19