Runs package occupancy: rooms, therapists and kitchen together.
For a wellness resort that books packages. The resort enters its rooms, its packages (the nights, the base price, and what each needs every day per guest — so many treatments of a kind, so many meals) and its therapists, and rosters each therapist on the days they work; a therapist with no roster for a day is not counted for it. A guest is booked on a package with check-in and the number of guests; a room is given at booking or later and the calendar refuses a room already held on any of those nights. The next two weeks show, day by day, the rooms held, the guests, the treatment sessions to give, the meals to cook and the therapists rostered. The numbers it is compared with — the meals the kitchen can serve, the sessions one therapist gives in a day — are the resort’s own, entered with their source; none ships, and until they are set the day’s load is counted and nothing is flagged.
/resortresort.readWhat it does not do, by design. A listing with only benefits is an advertisement.
Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.