Salon & Spa Management

ECOSIRE builds a dedicated Frappe app — its own module, DocTypes, and REST endpoints — installed on your ERPNext bench so appointments and money live in one system. At the center is an Appointment DocType (customer, service, assigned stylist/therapist, start and computed end time, chair/room, status) rendered on a color-coded Calendar view, with statuses driven by workflow: Booked -> Confirmed -> In Progress -> Completed -> No Show. A Service DocType extends Item with duration, required skill, and default commission rule; a Service Package bundles services and retail products with a prepaid balance the front desk draws down at checkout. Availability and double-booking are enforced in hooks.py validate doc events plus server-side frappe.db overlap queries, so two clients can't be booked into the same therapist or room, and buffer minutes are reserved automatically.

Booking flows in from two directions. Front-desk staff use the Desk calendar; the public books through a whitelisted REST method (@frappe.whitelist(allow_guest=True)) that returns real-time open slots and creates the Appointment under a scoped Role Profile — never exposing the full Frappe API. Client Scripts on the appointment form live-check stylist availability and auto-fill service duration and price as the user types. At checkout, one action rolls the completed services and any retail items the client bought into a single Sales Invoice, so a haircut, a treatment, and a bottle of product ring up on one bill with correct tax and payment. A scheduler event (scheduler_events in hooks.py) runs nightly to compute stylist commissions from completed appointments, post them as Additional Salary or a commission report, and send appointment reminders.

Because this is build-to-order, ECOSIRE builds it around your actual chairs, service menu, commission math, and branch structure — not a fixed template you bend to fit. After a short scoping call we confirm the DocType model, permission roles, and booking rules in writing, build on a staging bench, run UAT with your real service catalog, and hand over the installed app plus its git repository. Typical delivery is 2–4 weeks from confirmed scope. The result is a native ERPNext extension that upgrades cleanly with your site and speaks the same Item, Customer, and GL language as the rest of your accounting.