> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kitospace.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Booking Links & Channels

> Share direct booking links, connect sales channels, import iCal calendars, and resolve booking conflicts.

## What is a booking link?

A **booking link** is a shareable web address that lets guests book specific units of yours directly. Each link covers the units you choose and, optionally, a date range — one link for a single apartment in June, another for the whole property.

Find them under **Marketing → Booking Links** in the sidebar. Every link has its own page with the booking address, a downloadable QR code, a copy-to-clipboard shortcut and a share button. If your plan includes embedding, the same page gives you an embed block for your own website.

Creating a link takes a name, one or more units, and the dates it should be bookable for. Everything can be edited afterwards by clicking the field.

<Tip>
  Print the QR code for on-site use — reception, flyers, a sticker in the room — and use the copyable address for email and social posts. Both point at the same booking page.
</Tip>

## How do sales channels work?

**Channels & Distribution** is the other way inventory reaches guests: publishing your rooms and rates to external booking sites. The hub page covers **channel connections** (connect and disconnect the sites you sell on), connection health, and **inventory pools** (which units are sold together as one room type).

Rates, availability, minimum stays, descriptions, photos and amenities are published *from* Kitospace *to* every connected channel. Edits made in a channel's own extranet are not read back and get replaced the next time we publish. Bookings, changes and cancellations travel the other way — they always reach you here.

Each unit has its own **Channel sync** switch. Turning it off tells connected channels the unit is sold out.

## What is calendar sync?

**Calendar sync** is per-unit iCal syncing, on the unit's distribution page. It works in both directions:

| Direction         | What it does                                                                                            |
| ----------------- | ------------------------------------------------------------------------------------------------------- |
| **Calendar sync** | Import blocked dates from a personal or team calendar (Google, Outlook, Apple) onto the unit's timeline |
| **Inbound feeds** | Import availability from booking platforms your channels do not manage; polled every 15 minutes         |
| **Outbound feed** | A read-only address other systems subscribe to for this unit's availability                             |

Imported dates are never re-exported in the outbound feed, so no loop can form. Calendar apps refresh subscriptions on their own schedule, typically every 8–24 hours.

<Warning>
  Do not add an inbound feed for a platform that is already connected as a channel. Pointing both at one platform makes them overwrite each other, and the usual result is a double booking.
</Warning>

## What is a booking conflict?

A **booking conflict** is a collision: an external booking arrived for dates a unit is already committed to. The **Conflicts** page lists them, and the sidebar carries a badge with the number still unresolved.

Opening a conflict shows the two bookings side by side — the external booking and your own reservation. You then choose one of:

| Resolution                  | What happens                                                                                                                 |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **Reassign guest**          | Move the external guest to a unit that is free for those dates. Everyone keeps their booking.                                |
| **Keep my reservation**     | Your reservation keeps the unit. You cancel the booking on the channel yourself, then confirm here to close the conflict.    |
| **Honour external booking** | The external booking keeps the unit and your reservation loses its allocation for those dates. The guest has to be informed. |

Most resolutions can be undone afterwards; the page says plainly when one cannot. Resolved conflicts stay readable as a record of the decision.

<Warning>
  Conflict resolution is time-sensitive. Until you resolve it, two guests believe they have the same room for the same nights — and the longer it sits, the fewer free units are left to move anyone into. Treat the conflicts badge as work for today.
</Warning>

## Who can see these pages?

Booking links and channel connections need the permission to manage sales channels, plus a plan that includes reservations. Conflicts are visible to anyone who can read reservations — an overbooking has to be fixable by the person on shift, not just an administrator.

## Common use cases

* **Direct bookings** — send a link to a returning guest so they book with you instead of through a booking site.
* **Seasonal promotion** — create a link limited to a date range and share it for that season.
* **Owner-blocked dates** — import an owner's calendar so their stays block the unit automatically.
* **Overbooking triage** — work the conflicts queue each morning, while units are still free to move guests into.

## Related

* [Reservations](/docs/reservations/overview)
* [Calendar](/docs/reservations/calendar)
* [Inventory pools](/docs/units/inventory-pools)