Sabee for wellness retreats.

A retreat booking is not a room booking

Most PMS software treats a reservation as a room, a rate, and a set of dates. That model breaks the moment a retreat centre tries to use it. A guest arriving for a seven-night detox programme is not buying seven nights of accommodation with breakfast included — they are buying a programme that happens to include a room, three meals a day built around a specific protocol, a schedule of treatments and classes, and often a cohort of other guests moving through the same programme together.

Sabee's wellness configuration starts from the programme, not the room. A programme is defined with its own duration, its own inclusions, its own price, and its own capacity — and the room becomes one component inside it rather than the primary object. That reordering is what lets a retreat operator sell "12-night Ayurveda Immersion, arrivals every second Sunday, 14 spaces" as a real inventory item with its own booking page, rather than jury-rigging it out of a room type and a spreadsheet of add-ons.

Treatment scheduling that does not double-book your therapists

Every retreat runs a limited number of treatment rooms and a limited number of therapists, and both are shared resources across every guest on-site, not just the ones on a specific programme. Sabee's scheduling module treats therapists and treatment rooms as their own bookable resource pools, separate from guest rooms, with their own working hours, break rules, and specialisations (a shiatsu therapist is not interchangeable with a physiotherapist, and the system will not let a guest book across that boundary by mistake).

When a guest checks in on a 12-night programme that includes six massage sessions, four consultations and a daily yoga class, Sabee proposes a schedule across their stay that respects the therapist roster, the room availability, and the guest's own preferences — and lets the wellness coordinator adjust it by drag-and-drop rather than rebuilding it from scratch. Overbooking a therapist, or leaving a treatment room empty for three hours in the middle of a fully booked afternoon, are the two failure modes the scheduler is built to prevent.

Package pricing that survives real-world exceptions

Retreat pricing is rarely a simple night rate. It is a package price for a fixed programme length, often with single-supplement rules, add-on treatments priced individually, early-booking discounts, and a different price entirely for a guest who wants to extend their stay by a few nights outside the programme structure. Sabee's package-pricing engine handles all of that as configuration rather than manual override: define the base package, the supplement rules, the add-on catalogue, and the extension rate, and the booking engine prices every combination correctly without a staff member re-keying totals by hand.

This matters more than it sounds. Retreat centres lose real margin when front-desk staff manually calculate a package-plus-extension-plus-two-extra-treatments total under time pressure at check-in, because manual pricing under pressure trends toward under-charging. Sabee removes that risk entirely — the quoted total is the correct total, every time, and it is what actually gets billed.

Allergies, dietary protocols and guest preferences

A retreat's guest profile carries more operationally critical information than almost any other hospitality format. Food allergies are not a nice-to-have note — many retreat programmes are built around a specific dietary protocol (elimination diets, fasting windows, specific macronutrient ratios) that the kitchen must follow exactly, and a missed allergy note is a genuine safety issue, not an inconvenience.

Sabee's guest CRM surfaces allergy and dietary flags at every relevant touchpoint: the kitchen's daily meal-prep list, the treatment-booking screen (a therapist needs to know about a skin allergy before selecting massage oils), and the front-desk arrival brief. These flags persist across visits, so a returning guest who disclosed a shellfish allergy on their first stay two years ago does not have to disclose it again at every subsequent booking — and the kitchen sees it automatically on every stay.

Longer average stay changes the operational rhythm

Where a boutique hotel's average stay might be 1.8 nights, a wellness retreat's average stay commonly runs 5 to 14 nights, and some signature programmes run a full month. That longer horizon changes almost every operational rhythm: housekeeping shifts from a daily full clean to a lighter mid-stay service with a deeper clean on a fixed cadence, F&B planning has to account for guests who will eat every meal on-site for two weeks without repeating a dish, and the guest relationship itself has more time to develop — which is exactly why guest-preference data matters more here than in a one-night stay.

Sabee's housekeeping module supports this directly with stay-length-aware service rules: define the mid-stay service cadence for programme guests (say, light service on days 2, 4, 6, deep clean and linen change on day 7), and Sabee generates the right task list automatically instead of defaulting to a daily full turnover that neither the guest nor the housekeeping team actually wants.

Cohort bookings for retreat-programme groups

Fixed-date retreat programmes sell as cohorts — a group of unrelated guests who all arrive on the same date and depart on the same date, moving through the same schedule together. That is structurally closer to a group booking than an individual reservation, and Sabee's cohort-booking tools reflect that: a programme opens with a defined capacity, individual guests book into the cohort independently (no need for one lead booker holding the whole group), and the programme coordinator gets a single roster view showing every guest in that cohort, their dietary flags, their treatment schedule, and their payment status in one screen.

This is also where package-based revenue management pays off. A 14-space cohort with 9 booked three weeks out is a very different pricing decision than the same cohort with 3 booked — Sabee's pace reporting is scoped per programme cohort, not just per date range, so a retreat director sees exactly which upcoming programme needs a promotional push and which is already close to selling out.

Meal-plan CRM notes that follow the guest

Beyond hard allergy flags, wellness guests tend to arrive with soft preferences that meaningfully affect their experience — a guest who prefers earlier dinner seatings, one who is doing a specific elimination protocol only for the first week, one who has asked twice not to be seated near the yoga studio's morning class group. Sabee's CRM notes are structured so these observations accumulate over a guest's history and surface automatically to the relevant team (F&B, front desk, wellness coordination) without anyone needing to remember to check a separate document.

Retreat operators who have run on spreadsheets before consistently describe this as the single biggest quality-of-life change after switching — not a headline feature, but the accumulation of dozens of small correct decisions that used to depend on one staff member's memory.

Reporting built for programme-based revenue

Because the sellable unit is a programme rather than a room-night, standard PMS reporting (ADR, RevPAR) tells only part of the story. Sabee's wellness reporting adds programme-level metrics — occupancy per cohort, average package value, add-on attach rate, and repeat-programme rate — so a retreat director can see whether the 12-night Ayurveda programme is actually more profitable per available bed-night than the shorter weekend detox, rather than guessing from gut feel.