Salons and spas run on the calendar, but ERPNext out of the box has no concept of a bookable stylist, a chair that can only take one client at a time, or a checkout that mixes a 45-minute haircut with a bottle of retail shampoo and a stylist's commission on both. Teams end up juggling a third-party booking app for appointments and ERPNext only for invoicing, so no-shows, walk-ins, package redemptions and staff payouts never reconcile. ERPNext's native POS Profile and Sales Invoice are built for retail and restaurant flows, not for time-and-resource-based services, and this is exactly where a generic install runs out of road.

ECOSIRE builds a purpose-designed Frappe application that installs cleanly onto your ERPNext v15 or v16 bench. It introduces first-class DocTypes for the salon domain — an Appointment linked to Customer, Service (Item), and a Staff Resource (stylist/therapist), plus Service Package, Membership, and Commission Rule — instead of bending Project/Task or Healthcare into a shape they were never meant for. A resource-aware calendar view enforces double-booking rules and staff working hours through validate hooks in hooks.py doc events, so a therapist can never be booked in two rooms at once. Online booking is exposed through whitelisted REST endpoints (@frappe.whitelist(allow_guest=True)) that your website or a WhatsApp/Instagram funnel can call, with rate limiting and slot-availability checks server-side.

At the counter, the POS screen (a Frappe page backed by client scripts) lets front desk staff pull an existing appointment, add retail products to the same cart, apply a membership or package redemption, and split the resulting Sales Invoice into per-line commission entries. Commission and tip logic lives in server scripts and scheduled jobs: a hooks.py on_submit event on Sales Invoice writes commission ledger rows against each staff member per service line, and a nightly scheduler event (scheduler_events) aggregates them into a payout report that ties back to ERPNext Payroll or a Journal Entry. Role profiles and permission rules keep receptionists, stylists and owners scoped to what they should see — a stylist sees only their own calendar and commissions, the owner sees the whole floor.

Because this is build-to-order, we start from your actual services, staff structure, package rules and branch layout rather than shipping a one-size-fits-all download. After a short scoping call we confirm the exact DocTypes, fields, commission formulas and booking rules in writing, build the app in a Git repository, and validate it on a staging bench with your data before go-live. Typical delivery is one working week from confirmed scope. There is no instant download — you receive tested source code, a documented install, and a supported handover, all built specifically for your salon or spa.