How to Build Nail Salon Management Software

A nail salon with 8 technicians runs both appointments and walk-ins at the same time. The scheduling problem isn't the calendar. It's answering one question accurately at 11am on a Saturday: how long is the wait? A wrong answer sends the walk-in to the salon across the street.

What nail salon management software does

The nail salon industry generates over $8 billion in annual revenue in the US, with roughly 56,000 locations competing on service quality and customer experience. According to a Mintel beauty services report, 48% of salon clients say speed of service and wait time accuracy are the primary factors in whether they return to a salon. That stat is what makes the scheduling engine the make-or-break component of any nail salon software platform.

The software manages six connected systems:

Online booking. Customers select a service, pick a technician or any-available, and choose a time slot. The booking engine checks technician availability and filters by service specialization. Not every tech does nail art or acrylics.

Walk-in queue management. Walk-in clients check in on a tablet at the front desk, select their service, and join a digital queue. The system shows estimated wait time per available technician in real time.

Technician scheduling and commission tracking. Each tech has a personal schedule with their working hours and service specializations. Every completed service records the tech, the service price, and the commission rate. Pay statements are generated per pay period.

Customer records. Service history, preferred technician, before/after nail photos organized by visit, and color/product preferences. Surfaces at check-in so the tech knows the client's history before touching a nail.

Retail POS. Product sales (nail polish, nail care) integrated with the booking system so all revenue flows into one report.

Multi-location management. Central view of occupancy, revenue, and technician performance across all locations.

MVP vs. full platform

An MVP includes:

• Online booking with technician-service matching

• Walk-in check-in with queue and wait time display

• Commission tracking per completed service

• Basic in-person POS (card payments via Stripe Terminal)

• Customer records with photo storage

• Simple daily/weekly revenue reports

A full platform adds:

• Retail inventory management with reorder alerts

• Loyalty points and gift card programs

• Automated rebooking reminders via SMS

• Multi-location analytics and staff comparisons

• Payroll export to ADP or Gusto

• No-show fee handling (charge on file for missed appointments)

Core architecture

Booking engine. Service menu with duration per service type. Tech availability calendar with service specialization flags. When a client books a gel manicure, the system only shows techs who have gel listed as a service they perform. Availability is calculated as open time blocks minus committed appointments minus buffer time between services.

Walk-in queue. An iPad app at the reception desk. The client enters their name and selects a service from the menu. The system enqueues them and calculates estimated wait time per tech. The receptionist or the client chooses a tech. When the previous service completes, the tech is marked available and the next queue entry is assigned.

Commission engine. Every service completion creates a commission record: tech ID, service ID, service price, commission rate (stored per tech, overridable per service), and commission amount. The payroll report aggregates these by tech and pay period. Tips are tracked separately. They're distributed 100% to the tech with no commission deduction.

Customer record. Core fields: name, phone, email, preferred tech, visit history. Photo storage: S3 bucket organized by customer ID and visit date. Signed URLs deliver photos securely to the front desk app at check-in without exposing the S3 bucket directly.

The hardest technical challenge

Walk-in and appointment interleaving is the scheduling problem that off-the-shelf tools handle poorly.

"The biggest operational failure we see in service businesses is showing customers a wait time they can't trust. It destroys loyalty faster than a bad service outcome."

Todd Krizelman, Co-CEO of MediaRadar, speaking at a 2024 field service operations panel on customer retention

RaftLabs has shipped scheduling platforms for service businesses across the beauty and wellness space. The wait time calculation engine is where almost every early build breaks. Teams underestimate the interleaving logic, ship a naive version, and spend months fixing it in production.

A technician's schedule at any given moment looks like this: currently doing a pedicure (started 20 minutes ago, 25 minutes remaining), then a 1pm gel manicure (40 minutes), then open until 3pm. A walk-in arrives at 12:45pm wanting a basic manicure (25 minutes). When can this tech take them?

The naive answer: 1pm appointment ends at 1:40pm, so take the walk-in at 1:40pm, done by 2:05pm. Wait time: 55 minutes.

But the walk-in asked at 12:45pm. The tech's current service ends at 1:00pm. If the 1pm appointment is running on time, there is a 0-minute gap. If the 1pm appointment no-shows, there is a 40-minute window. The system cannot show the walk-in a wait time of "depends on whether the 1pm shows up."

The correct model treats each tech's day as a sequence of committed time blocks and available gaps. A walk-in can fill a gap only if the gap is longer than the walk-in's service duration plus a buffer. If no gap exists before the next committed appointment, the walk-in waits until after the last committed appointment of the current run.

This calculation must update every few minutes as services complete early or run long. Build a background job that recalculates wait times every 60 seconds and pushes updates to the front desk display.

The second problem: when a 2pm appointment arrives at 2:15pm, the tech has already started a walk-in in that slot. Now the system must recalculate the appointment's new estimated start time and notify the client. Build a late-arrival detection rule (appointment start time + 10 minutes, with no check-in) that triggers an automatic SMS to the client asking if they're still coming.

Build costs and timeline

MVP: $90K-$160K. 10-14 weeks.

Covers: online booking, walk-in queue with real-time wait time, commission tracking, basic POS, customer records with photo storage.

Team: 1-2 backend engineers, 1 React developer, 1 React Native developer (iPad kiosk app), 1 designer.

Full platform: $180K-$300K. 18-24 weeks.

Adds: retail inventory, loyalty program, automated rebooking reminders, multi-location analytics, payroll export.

Running costs: $500-$2,000 per month (infrastructure, Stripe fees, Twilio SMS).

Build vs. buy

According to Capterra's 2024 salon software survey, the average independent salon using off-the-shelf software pays $150-$400/month once add-ons are factored in. Multi-location operators hit $1,500-$4,000/month. At that run rate, a custom build recovers its investment in under 3 years.

Vagaro ($25-$90/month): full-featured for a single salon, has walk-in queue and commission tracking. Good for a single location owner.

Boulevard ($175-$375/month): more polished booking experience, stronger analytics. Used by higher-end salons.

Fresha (free base, charges on marketplace bookings): works well for salons that want new client discovery, but the platform takes a cut on every Fresha-sourced booking indefinitely.

Phorest ($100-$200/month): strong marketing automation features for rebooking campaigns.

Build custom when you operate 5+ locations and need consistent reporting across all sites, or when you're building a white-label platform for a nail salon franchise. At 10 locations, Boulevard costs $1,750-$3,750/month. The build investment recovers in 2-3 years.

Tech stack

Backend: Node.js with PostgreSQL. Frontend: React for booking and POS web app. Kiosk app: React Native on iPad (walk-in check-in, service selection, queue display). Payments: Stripe Terminal for in-person card processing, Stripe for online appointment deposits. Photo storage: AWS S3 with CloudFront CDN and presigned URLs. SMS: Twilio for appointment reminders and late-arrival alerts. Push notifications: Firebase Cloud Messaging for staff alerts.

The walk-in queue recalculation job runs as a cron task every 60 seconds. Use PostgreSQL's FOR UPDATE SKIP LOCKED on queue records to prevent duplicate processing when multiple servers are running.

RaftLabs has shipped scheduling platforms, POS systems, and two-sided service marketplaces. See our SaaS platform engineering service or talk to us about your build.