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 — or connect Hospitable or Smoobu once under Features and take over the listings from there. 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.
How the booking calendar fits into the overall workflow of a vacation rental operation — cleaning task, checklist, defect, caretaker, handover protocol — is described on the industry page Vacation Rentals & Serviced Apartments; the step-by-step setup is in the Guide for the office.
Switching the module on
The panel entry "Bookings" only appears once the module is switched on for the property — accounts in the holiday-rental industry have it on from sign-up. Switch it on under Features → Per property → Bookings, also for several properties at once. You can switch it off on the panel entry via its context menu; the entry then disappears again.
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). Without pasting a link per listing: connect Hospitable under Features. |
| 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. |
| Smoobu | Listing → Calendar → "iCal export" | One link per listing. Without pasting a link per listing: connect Smoobu under Features. |
| Other calendar | iCal export of your property management software (e.g. 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.
Connecting Hospitable or Smoobu
If you use Hospitable or Smoobu as your channel manager, there is no need to paste an iCal link per listing: under Features → Connections you connect the account once and then take over the provider's listings as properties. How to set up the connection — API key and secret for Smoobu, connect button or access token for Hospitable — is described on the page Features → Connections.
Compared with an iCal link, the connection delivers more:
| iCal link | Connection via Features | |
|---|---|---|
| Setup | one link per listing, pasted on the property | once per account; listings are taken over |
| Check-in and check-out | date only | date and time, where the provider knows it |
| Guests | — | number of adults and children |
| Booking channel | the source of the link | the channel behind the channel manager (Airbnb, Booking.com, direct booking …) |
| Cancellation | the booking disappears from the calendar | a real status from the provider |
| Freshness | fetched every 30 minutes | changes arrive within seconds via webhook; additionally fetched every 30 minutes |
Both ways can be mixed: a property can have a connected listing and further iCal calendars alongside it.
Taking over listings
After connecting, the card under Features shows all listings of the provider. For each listing you choose:
- Create new property — LiteLog creates the property with the provider's name, address, coordinates and time zone; with Hospitable, the listing's default check-out time is also taken over as the due time of the cleaning task.
- Assign existing property — if the apartment already exists in LiteLog, for example with an iCal calendar.
Take over creates the properties, switches the "Bookings" module on for each of them and imports the bookings immediately.
On this tab the listing then appears as a source without an address, marked "Connected via Smoobu (Features)" or "Connected via Hospitable (Features)". It cannot be edited here — label and credentials belong to the connection.
Unlinking a listing
Unlink on the source detaches the listing from the property: its bookings are removed, tasks already created remain. The connection to the provider stays in place; under Features you can assign the listing again at any time. To remove the whole connection, see Features → State, synchronise, disconnect.
What is not taken over
Guest names, contact details, prices and messages stay with the provider. Per booking, LiteLog stores only check-in and check-out with time, number of guests, booking channel and status.
Task per check-out
In the Task per check-out card you define what the automatically created task looks like:
| Setting | Meaning |
|---|---|
| Template | Checklist or form template for the cleaner — e.g. "Cleaning checklist unit". A checklist is copied into every check-out task as items; whether all items are required there (completion only once every item is ticked and every photo item has its photo) is set by the template's All items are required switch. A form is filled in when completing. |
| 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). If the booking carries a check-out time (connected listing), that time applies; if the provider changes it, the open task is rescheduled. |
| 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}. |
Tasks are created for check-outs within the next 120 days; later bookings are stored and get their task once they enter this window. The task description carries check-in, check-out, source and the reservation link — for connected listings also the times, the number of guests and the booking channel. 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 or the connected provider reports it as cancelled, 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. Connected listings offer only Unlink instead of Edit and Delete.
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; for connected listings with the time after the date. |
| Source | Connected calendar or connected listing, for channel managers with the booking channel behind it. |
| Guests | Number of adults and children — connected listings only. |
| 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. |
Overview across all properties
If you look after several holiday rentals, you do not have to open each property: under Features → Bookings → "Open overview" there is a page covering all properties of the account. It is read-only — connecting or editing calendars and setting the task per check-out stays on this tab of the respective property.
Navigation: Features → card "Bookings" → "Open overview" (the page has no menu entry of its own)
The page shows two tables:
Connected calendars — every stored calendar with its property:
| Column | Meaning |
|---|---|
| Property | Link to the property's "Bookings" tab, where the calendar is managed. |
| Label / Source | The label you gave and the portal (Hospitable, Airbnb, Booking.com, …). |
| Status | The same states as above (Active, Never fetched, Error, Paused). If the module is switched off for the property, the row is dimmed with the hint Module off — the calendar stays stored but is not fetched. |
| Last fetch / Bookings | Time of the last fetch and number of imported bookings. |
| Fetch now | Loads the calendar immediately (at most once per minute), as on the property. |
Arrivals and departures — the bookings of all properties in the selected period (default: today until 60 days ahead). Above the table you narrow down to one property or another period; both are part of the address and can be shared as a link. The columns match the property's bookings list, plus the Property with a link.
As long as no calendar is connected, the page leads to the "Bookings" card under Features — there you switch the module on per property.
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.
The connection says "Sign-in required". The API key or access token has expired or was revoked at the provider (Hospitable access tokens are valid for one year). Under Features, click Reconnect on the card and enter new credentials — the listing assignments are kept.
The apartment already exists in LiteLog. When taking over, choose Assign existing property instead of "Create new property" — otherwise a second property with the same bookings is created.
The automatically created property has no public holidays. Taken-over properties receive name, address, coordinates and time zone, but no holiday region. Add it in the property settings if tasks or shifts depend on it.
Times are missing with Smoobu. Smoobu delivers check-in and check-out times only if they are maintained there on the booking or the listing. If they are missing, the time from the "Task per check-out" card applies, and the bookings list shows the date only.