BookUser1 / 5
Salon Appointment Booking
Booking that respects who can do what and how long it really takes, with the colour formula still there next time. A marketplace takes a cut of the client you already had.
- From
- $849
- Function
- 23
- User types
- 2
- Platform
- iOS & Android
React Native · TypeScript · PostgreSQL · Expo
Inside the app
What it does out of the box
23 connected functions on one schema across 2 user types. Everything below is in the template before a line of customisation.
Book by stylist
Clients book a person. A system that assigns “anyone available” to somebody who asked for Rhea is a system that loses Rhea’s clients.
Real durations
Enforced per treatment, so a full head of colour cannot land in a 45-minute gap and wreck the afternoon.
Skills enforced
A stylist who is not colour-qualified cannot be booked for colour. The rule lives in the system rather than in somebody’s head.
Deposits
Where you require them, with the rule shown before the client agrees rather than argued about after a no-show.
Colour history
Formula, developer and timing kept against the client, which is what makes the next visit good.
Gaps
Unsold chair time shown as unsold rather than as white space, because that is what it costs you.
User types
Two apps, one chair.
The client is booking a person as much as a time, and the salon is selling a finite number of chair hours. Both facts shape the screens more than a generic booking tool allows for.
User, the client
Books the stylist they want for a treatment that fits, sees the deposit rule before agreeing to it, and rebooks from history in two taps.
- Book by stylist, not just by time
- Durations that match the treatment
- Deposits where you require them
- Rebook the same thing in two taps
- Colour and formula history kept with them
Owner, the salon
Sets services, stylists, rotas and rules, and works the diary through a busy Saturday without losing a slot.
- The day, workable mid-shift
- Stylist skills enforced at booking
- Deposit and cancellation rules that hold
- Gaps shown as unsold time
- No-show pattern per client
The limits
What this is not.
The same list we give for every app in the catalogue, because the fastest way to a bad project is a promise made in a meeting that nobody wrote down.
It will not bring you clients
It replaces the booking layer, not the marketing. Marketplace commission partly buys discovery.
We do not process payments
Deposits and payments run through your own provider account.
It is not a retail or stock system
Product sales can be added in a fitted build, but a salon that sells seriously needs stock handled properly rather than bolted on.
Patch-test rules are yours to set
The app enforces the interval you configure. What that interval must be is a matter for your insurer and local regulation.
Questions
Questions, answered plainly.
If yours is not here, ask it on the call rather than guessing from a pricing page.
How is this different from Appointment Booking?
Appointment Booking is the generic booking layer for any service business. This adds the things a salon actually needs: stylist skills, colour formulas, patch-test intervals and chair utilisation. Start here if you run a salon.
Can clients book a specific stylist?
Yes, and it matters more than most booking tools allow for. Being given anyone available after asking for a named stylist is the fastest way to lose a regular.
Does it stop no-shows?
Nothing stops them entirely. Deposits, reminders and a cancellation window reduce them, and the pattern per client is recorded so a policy decision is based on evidence.
Does it keep colour formulas?
Yes, against the client with the date and the stylist. It is the single most useful thing a salon system holds and the thing most generic tools omit.
Do I get the source code?
Yes. Both apps, API, schema, migrations and deployment configuration transfer on delivery.
Related
More on-demand builds.
Click through it before you spend anything.
The preview is the real app with sample data. Open it and judge the software rather than the pitch.