Run a group booking
A wedding party takes four apartments. That is one reservation with one guest to talk to and one price to agree, and four apartments that each check in, get cleaned and release their own door code on their own schedule.
Stay N Host models exactly that: one deal, several units under it.
Create one
Section titled “Create one”-
Start a group inquiry or open the group wizard from
/bookings. -
Add each apartment. Each is a unit of the same deal, with its own listing and its own dates if they differ.
-
Say who is staying in each apartment. The party is captured per apartment, not once for the whole booking, because that is where it actually matters: six adults across three apartments is two, two and two. The deal’s own figure is the sum.
-
Quote and confirm once. One price, one guest, one payment trail.
What the booking page shows
Section titled “What the booking page shows”One page for the stay, with one lifecycle panel per apartment, each headed by its listing code. The status in the page header is derived from the least advanced unit - so a reservation reads as “arriving” until every apartment has arrived.
What fans out, and what does not
Section titled “What fans out, and what does not”| Action | Scope |
|---|---|
| Cancel the deal | Every unit. One cancellation frees all of them. |
| Check in / check out / no-show | One apartment. Arrival is physical: a guest reaches one door at a time. |
| Door code release | One apartment, gated on that apartment’s own reservation. |
| The price, the payments, the ledger | The deal, split per unit where the books need it. |
Cleaning and turnovers
Section titled “Cleaning and turnovers”Each apartment produces its own turnover from its own checkout. A group leaving together generates four jobs on the turnover board, not one.