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.
- Tanning Salon Management
- Implementation and migration
How a Tanning Salon Management rollout works
Start with your services, members and exposure plans, then run a month of sessions.
Agree the operating boundary
The system holds services, sessions, bookings, attendance, exposure plans and sessions, members, membership plans and payments. Card processing and accounting stay in connected systems. The salon decides its exposure policy, prices and refund rules.
Map the source data
Agree service names, member numbers, current plans and enrolments. Authorize an exposure plan for every active member before go-live.
Configure a bounded pilot
Run one month of sessions live: booking, confirmation, check-in, exposure logging and payment confirmation.
Rehearse the exceptions
A paused member is not confirmed, a full session takes no more places, a session beyond the plan's maximum or inside its interval is refused, and a repeated check-in writes no second attendance.
Reconcile and release
Compare members, plans and the day's takings with the old system, get sign-off from the salon manager and agree the rollback window before cut-over.
What the customer provides
- Service list with durations, capacities and prices.
- Member list with status and current membership plans.
- Each active member’s exposure limits and the instructor who set them.
- 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 salon manager and replay the pilot’s exception cases before release. Past payments and enrolments keep the prices that applied at the time.
Set up Tanning Salon Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.