An advanced booking & operations platform built for a women's salon - designed not around a calendar, but around "how a salon actually operates" under real daily pressure.
Domain: Service Business OperationsStatus: 🟢 Soft Launch — Live Testing
RoleFull-stack Engineer
ComplexityMulti-role · Multi-constraint System
ImpactOperational chaos to Structured system
Project Gallery
11 images
+6more
💡 The Real Engineering Challenge
Most booking systems treat an appointment as a simple tuple: service + time + customer.
[Redacted]was built around a harder question:
what does it actually take for a booking to be possible?
"The problem wasn't building a booking page. The problem was modeling the operational logic of a salon itself."
Shift-Aware Scheduling No Ghost Slots
Staff availability isn't just a name in a database. [Redacted] ties every time slot to
actual shift windows, work days, and exceptions — before surfacing it to the customer.
Conflict Prevention First Zero Double-Books
The system validates against service duration, staff assignment, and concurrent bookings
before any appointment is confirmed — not after.
Payment-Linked Booking Real Intent
Bookings from the website require a deposit. Reception-created bookings require
full payment. The appointment state machine reflects both paths cleanly.
Best-Fit Recommendation Smart Allocation
Customers can pick a specific staff member — or let the system
recommend the best available match based on service, time, and shift constraints.
🏗️ System Architecture
[Redacted] operates as four interconnected layers — each solving a distinct operational concern.
Booking Request
│
▼
Availability Engine
│ ├── Is the service available?
│ ├── Does the time fit within shift hours?
│ ├── Is the staff member free? (no overlap check)
│ └── Specific pick or best-fit recommendation?
│
▼
Payment Gate
│ ├── Online booking → Deposit required
│ └── Reception entry → Full payment recorded
│
▼
Appointment State Machine
│ Pending → Awaiting Deposit → Confirmed
│ Confirmed → Completed / No-show / Rescheduled / Cancelled
│
▼
WhatsApp Notifications → Customer Confirmation + Reminders
│
▼
Financial Reports + Admin Dashboard (Manager Layer)
📋 Appointment States
Every appointment moves through a defined state machine — no ambiguity in what "confirmed" means.
The platform doesn't mix all users into one view. Each role has a dedicated,
permission-scoped experience that matches their actual daily job.
💅
Customer
Browse 200+ services, create multiple bookings, pick a specific staff member or use best-fit recommendation, pay deposit online, receive WhatsApp updates.
🗓️
Staff Member
View shift-linked personal schedule, see assigned services, track upcoming appointments, avoid surprises — no access outside their scope.
🖥️
Receptionist
Enter walk-in bookings (full payment), handle cancellations and rescheduling through the control panel, manage daily operations in real time.
📊
Site Manager
Full visibility: all bookings, all staff shifts, services and pricing, financial reports, daily pressure monitoring — a genuine operational control layer.
🧠 Why This Is Actually Hard
This isn't a CRUD app with a calendar skin. The real complexity is in the constraints.
Modeling real availability — A staff member being "in the database" doesn't mean she's bookable.
Availability is calculated from shift start/end, assigned service types, and existing confirmed appointments.
200+ services with distinct durations — Every service has its own duration, price, and potentially a required skill level or specific staff assignment.
Scheduling must account for the actual time block each service occupies.
Payment as a workflow gate — The booking-to-payment link is behavioral: online bookings trigger a deposit flow,
reception entries bypass it with full payment. The state machine must reflect this without leaking logic between paths.
Role-based access across a live system — Four roles with different views, different permissions, and different operational realities —
all sharing the same underlying data layer without colliding.
The best UX here isn't a beautiful animation. The best UX is a system that prevents chaos before it starts.
![[Redacted] Booking Engine thumbnail](/_next/image?url=https%3A%2F%2Fcdn.lous.in%2Fkhalil%2F2d158032-73c4-48e7-aa6b-e0d4f1e77e9e_updated_thumbnail.jpg%3Fformat%3Dwebp&w=3840&q=75)
