These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Spa & Wellness Management
- Implementation and migration
How a Spa & Wellness Management rollout works
Start with your menu, rooms and therapists, then run a week of bookings.
Agree the operating boundary
The system holds treatments, sessions, bookings, check-ins, therapist allocations, rooms, members, packages and payments. Card processing, online booking and accounting stay in connected systems. The spa decides its menu, package rules and refund policy.
Map the source data
Agree service names, room names, member numbers and current package enrolments.
Configure a bounded pilot
Run one week of sessions live: booking, confirmation, allocation, check-in, room turnaround and payment confirmation.
Rehearse the exceptions
A full session takes no more places, a repeated check-in uses no extra session, a paused member gets a charge and a room in maintenance is moved around.
Reconcile and release
Compare members, packages and the day's takings with the old system, get sign-off from the spa manager and agree the rollback window before cut-over.
What the customer provides
- Treatment menu with durations, capacities and prices.
- Rooms with treatment type and capacity, and the therapist list.
- Members with status and current packages.
- The coming weeks’ sessions and the people who will use the system.
Changing it afterwards
Use Proto to prepare changes on a branch. Review changed fields, permissions and reports with the spa manager and replay the pilot’s exception cases before release. Past payments and enrolments keep the prices that applied at the time.
Set up Spa & Wellness Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.