← back to reference index

Stays

TuluyanOS Owner & Manager provisional · D87, D88

Sell on Airbnb, Booking.com and Agoda without double bookings (D87)

STATUS: interactive demo — behavior shown here is the intended contract (nothing is saved). Demo Location: La Union Beach Villas (stays on), business date Mon, Sep 28 2026.
iCal is not real-time. Airbnb, Booking.com and Agoda fetch your calendar on their own schedule (often every 1–3 hours) and we fetch theirs every 15 minutes. Two guests can book the same dates in that gap. iCal sends dates only: no guest name, price or payment. For hotels selling many rooms on OTAs, use a channel manager (below).

Export: give these links to each channel

Import: bookings made on the channel

Channel manager (two-way, real-time) phase 2 · partner being chosen (PLAN-273)

Pushes availability, rates and restrictions per room type and rate plan within a minute, and receives OTA reservations with guest details, price and commission. Planned channels: Agoda, Booking.com, Expedia, Traveloka, Airbnb (via the partner; we don’t connect to each OTA directly). Mapping screen: your room type ↔ channel room code, your rate plan ↔ channel rate code.

Implementation notes for Cursor

Entities: ChannelConnection (provider ical/channex/siteminder/…), ChannelMapping (room type ↔ channel codes; ical_import_url_enc, ical_export_token_hash); imported stays are Reservations with source and no guest details.

Key states: Export URL carries a random token (only the hash is stored); rotating it kills the old link. Import accepts only https URLs on public hosts (no localhost, private or link-local IPs, no redirects to them: SSRF guard), max 1 MB, fetched every 15 min; a removed event cancels the imported stay; a clash is kept and flagged overbooked with a push.

Forbidden inventions: No scraping OTA extranets; no storing OTA passwords; no direct OTA APIs (phase 2 goes through one partner).

Governs: D87; modules/STAYS.md §8; PLAN-272, PLAN-274.