Skip to documentation content

Channels & Calendar

Use the unified booking calendar

Read website bookings, API reservations and iCal blocks together while keeping source ownership and read-only restrictions visible.

The Pro Booking Calendar gives staff one view of stay intervals from the website, existing Booking.com or Agoda API reservations and iCal external blocks. It is a presentation of authoritative records, not a second inventory engine. Free booking availability remains the final authority for whether a new website booking can be created.

Read the calendar

  1. Open Hotel Booking → Booking Calendar.
  2. Choose the date range and room type filters needed for arrivals or occupancy.
  3. Read the source label: Website, Booking.com (API), Agoda (API) or the iCal provider and source label.
  4. Open a normal website or API booking only through its supported detail link.
  5. Treat an iCal row marked External calendar block as read-only and return to the OTA for changes.

The calendar uses check-in inclusive and check-out exclusive occupancy. It may show an iCal block without guest details because iCal supplies dates only. A successful source refresh can release a block that disappeared; an error keeps the previous block and displays health attention rather than silently clearing it.

Do not infer payment or confirmation from a calendar color. Check the source record, booking status and payment ledger separately. If the same stay appears twice, determine whether API and iCal both imported it before changing any configuration. Preserve the source IDs, dates, room and redacted health reason for support.

Next: avoid and recover from overbooking.

Was this article helpful?

Your feedback helps us improve the documentation.