Availability and the calendar

Nights, not days

Every booking and every blocked range occupies the half-open interval [check-in, check-out): the check-in day is taken, the check-out day is free. A guest leaving on the 10th frees the 10th for the next arrival, and a three-night booking covers three nights.

• One service in the API answers which nights are free, from the bookings that hold nights plus the blocked ranges. The website's calendar, the reserve card, the checkout, the dashboard's calendar and the AI assistant all ask it, so they cannot disagree.
• Pending, confirmed, checked-in and completed bookings hold their nights. A cancelled booking holds nothing, so it never stands in the way of a new one.
• Every date is a calendar day in the company's time zone, the timezone setting (America/New_York), written YYYY-MM-DD, never an instant. That is what "today" means for arrivals, the calendar, the cancellation window and the holds, on both sides of a daylight-saving change.

What a stay accepts

The quote and the checkout check the same four, and the checkout checks them again when the booking is written, so two guests can never pay for the same night.

Holds

• A card or PayPal booking holds its nights from the moment it is made, before the guest is sent to the processor, for 30 minutes. If the payment has not settled by then, a sweep running every minute cancels the booking and frees the nights.
• A pay-on-arrival booking that waits for the host has no hold: it keeps its nights until the host confirms or cancels it.
• A paid booking holds its nights until it is cancelled.

The calendar on the website

The stay page shows two months and marks five states, each with its own legend swatch:

The reserve card beside it prices the chosen nights as soon as both days are picked.

The calendar in the dashboard

• /en/dashboard/calendar shows a month of nights, one row per stay. A booking's bar covers its nights and stops before the check-out day, and opens the booking's details.
• The blocked-dates dialog takes a stay's nights out of the calendar, from a first night to a check-out day, with a reason (Maintenance, Company use or Other) and an optional note. It is refused when a booking or another block already holds one of those nights, and the dialog names it: "Booking B0021 already holds some of these nights. Choose other dates.", or the same for a block such as K003.
• The date fields keep the day you pick whatever time zone the computer is set to, so a block or a filter never lands on the day before.
• Every block is listed below the calendar, soonest first, to edit or remove.
• If a stay is also listed on another site, block the nights booked there by hand: the product has no channel manager and no iCal import or export.

Who can do what

Both seeded roles, Super Admin and Manager, hold both.

The routes behind it

• GET /api/stays/:slug/availability?from=&to= answers a published stay's taken nights for at most 92 days at a time, and GET /api/stays/:slug/quote?checkIn=&checkOut=&guests= its nights, subtotal, cleaning fee and total, with available and the refusal reason.
• GET /api/calendar?month=YYYY-MM&stay= is the dashboard's month view.
• /api/availability/blocks lists, adds (stay_id, from, to, optional reason and note), changes and removes blocks. A conflict answers 409 with code: "dates_taken", details: { "held_by": "booking", "reference": "B0021" } (or "block" and a K reference) and the translated message "Booking B0021 already holds some of these nights."

• API reference