Bookings (property)
On this tab you connect the booking calendars of a holiday home or apartment with LiteLog. You enter the iCal link of your booking portal or property management software, LiteLog reads the bookings regularly and automatically creates one cleaning task per check-out — with a form template, due time and assignee.
Navigation: Master data → Properties → select property → panel entry "Bookings"
What is this view for?
Cleaning teams for holiday rentals plan around departures. Instead of copying bookings from Airbnb or Booking.com by hand, LiteLog takes them from the portal's calendar export. Every departure becomes a task on the task board and in the task calendar; the cleaner fills in the assigned checklist when completing it.
The feature is a property module: you switch it on per property, like the material or documents module.
Switching the module on
The panel entry "Bookings" is greyed out while the module is off for the property. Switch it on:
- directly on the panel entry via its context menu, or
- via the banner at the top of the tab with Switch on now, or
- under Apps on the Bookings card for several properties at once.
While the module is off, connected calendars stay stored but are not fetched and create no tasks.
Connecting a calendar
Click Connect calendar and paste the iCal link. Where to find it depends on the portal:
| Source | Where the link is | Note |
|---|---|---|
| Hospitable | Properties → open property → "Copy the iCal feed" | One link per property; already merges all channels (Airbnb, Booking.com, Vrbo). Recommended if you use Hospitable. |
| Airbnb | Calendar → Availability → "Sync calendars" → "Export calendar" | One link per listing. Bookings appear as "Reserved", blocks as "Not available" and create no task. |
| Booking.com | Extranet → Rates & Availability → "Sync calendars" → export link | One link per unit. Booking.com reports bookings and manual blocks identically ("CLOSED – Not available"); LiteLog flags such entries as uncertain and still creates a task. |
| Other calendar | iCal export of your property management software (e.g. Smoobu, Guesty, Lodgify) | Every entry is read as a stay. |
You can connect several calendars per property — for example Airbnb and Booking.com for the same apartment. The link is a secret (it contains a key); after saving, LiteLog only shows it masked. Only https links are accepted.
After connecting, LiteLog fetches the calendar immediately; afterwards every 30 minutes.
Task per check-out
In the Task per check-out card you define what the automatically created task looks like:
| Setting | Meaning |
|---|---|
| Template | Form template the cleaner fills in when completing — e.g. "Cleaning checklist unit". |
| Assignee | Assigned to the task directly. Empty = the task stays open and can be assigned to the on-duty team via automation. |
| Time | Due time on the check-out day (default 11:00). |
| Priority | Default priority of the task. |
| Priority on same-day turnover | If the next guest arrives on the check-out day, the task gets this priority (default High). |
| Task title | Default "Endreinigung · property name". Placeholders: {property}, {check_in}, {check_out}, {source}. |
The task description carries check-in, check-out, source and the reservation link. Guest names or phone numbers are never copied.
Moved booking: If the check-out date changes in the calendar, LiteLog updates the due date of the open task. If the task was already completed, a new one is created.
Cancelled booking: If a booking disappears from the calendar, the open task is marked "Storniert · …" and set to low priority; it is not deleted. The default rule "Buchung storniert → Objekt-Aufsicht" can notify the property supervisors (see automation).
Feed status
Each connected calendar shows its state:
| Status | Meaning |
|---|---|
| Active | Last fetch succeeded; next to it the time and number of bookings. |
| Never fetched | No successful fetch yet — normal right after connecting. |
| Error | Several fetches in a row failed (invalid link, portal unreachable). The reason is in the tooltip; LiteLog then retries only once a day until you fix the link. |
| Paused | Fetching switched off for this calendar; bookings are kept. |
Fetch now loads the calendar immediately (at most once per minute). Edit changes label, source or link; Delete removes the calendar with its bookings — tasks already created remain.
Bookings list
The table shows the bookings of the next 60 days:
| Column | Meaning |
|---|---|
| Check-in / Check-out | Arrival and departure day from the calendar. |
| Source | Connected calendar. |
| Same-day turnover | "Yes" if the next guest arrives on the check-out day. |
| Status | Confirmed, Cancelled or Blocked (block without task). |
| Task | Link to the created task with its state. |
Frequently asked questions
The calendar is rejected. Only https links to publicly reachable calendars are accepted. Copy the export link again from the portal; on Airbnb the export must be enabled for the listing.
Bookings arrive late. Airbnb refreshes exported calendars only every few hours, so last-minute bookings may appear later. Hospitable refreshes about every 20 minutes.
A task was created for a manual block. Booking.com does not distinguish blocks from bookings. Delete the task or use the Hospitable feed, which excludes blocks.
I want to hand the task to the on-duty team. Under Automation, create a rule with the trigger Check-out (booking) and the action Assign task → on-duty team of the shift.