Pro imports a complete iCal source snapshot into source-managed inventory blocks. It does not obtain full guest or payment details and does not turn calendar events into normal website booking actions.
Configure the source
- Open the room type’s OTA/iCal tab with channel-management permission and entitled Pro.
- Enter the trusted provider calendar URL, provider/label and quantity blocked per event. The quantity must be positive and no larger than that room type’s physical inventory.
- Choose an active source and the synchronization interval, then save. The default is 30 minutes; supported settings range from 5 to 1,440 minutes.
- Inspect the first synchronization result and dates before relying on the mapping. Use the available authorized manual action when appropriate.
The quantity setting applies to each event; a feed is not a flexible per-event room-quantity API. Check whether one feed represents one physical unit or pooled occupancy. Do not import the site’s own export back into the same inventory.
Understand supported dates and failures
Check-out is exclusive. Supported date/date-time values are normalized using the defined timezone rules. Recurrence, duplicate UID, ambiguous/floating times without the required timezone and other unsupported structures can reject the entire snapshot. A parser error must not be treated as an empty successful calendar.
Source reconciliation is atomic. Current source revision, room/inventory and authorization are rechecked before commit. A failed, partial or conflicting import preserves the previous snapshot. A valid complete empty calendar releases that source’s active blocks; missing/cancelled/transparent events can release their source-owned occupancy.
UID identity is source-scoped. Reappearance of the same event can reuse its block; a different source or changed identity is not automatically the same external reservation.
Verify and maintain
Compare occupied nights and remaining website inventory with the provider’s own calendar. Review last success, next due and bounded errors after changes. Keep URLs/private tokens out of logs and public support.
Disabling new synchronization or losing Pro availability does not remove existing Core-enforced blocks. Resolve changes through the source owner rather than ordinary booking cancellation. See scheduler and health.
