Running a beauty parlor on generic Odoo means fighting the software daily. Front-desk staff double-book stylists because the calendar has no concept of resource-specific skills or chair capacity; service durations aren't modeled, so a 90-minute keratin treatment looks identical to a 15-minute threading slot on the schedule. Retail products, consumable back-bar stock (colour tubes, developer, disposables), and service-linked packages all live in different places, and there is no clean way to say "this service consumes 30ml of product X" so inventory silently drifts. Odoo's native Appointments, Calendar, POS, and Sales apps each solve part of the problem, but none of them was designed for a salon where a walk-in, a membership redemption, a stylist commission, and a back-bar deduction all happen in one two-minute checkout.

This is where the standard building blocks run out of road, and where a typical off-the-shelf apps.odoo.com module usually stops at a thin appointment calendar without touching commissions, packages, or consumption. We build a proper industry template on top of Odoo. Concretely, we extend the resource and calendar models so each stylist is a bookable resource with a skill matrix and working-hours calendar, add a service.duration and buffer-time concept to appointment products, and introduce salon-specific models (for example a package/membership model with a compute field for remaining sessions using @api.depends, and a back-bar consumption line that deducts stock via stock.move when a service is delivered). Security is done right: dedicated groups (receptionist, stylist, branch manager, owner) defined in ir.model.access.csv plus record rules that scope stylists to their own appointments and managers to their branch. The front desk gets a purpose-built OWL/XML view and a POS screen extension so a receptionist can book, check out, redeem a package, and take payment in one flow, while QWeb reports cover the daily takings sheet, stylist commission statement, and per-service profitability.

Everything is wired into Odoo's automation and integration layer so the salon runs itself between visits: automated actions and scheduled crons send appointment reminders and re-book nudges, membership expiry alerts fire on ir.cron, and the XML-RPC/JSON-RPC API is available if you want your website booking widget, a WhatsApp reminder gateway, or a marketing tool to read and write appointments. We build against your Odoo edition and note the Community vs Enterprise differences up front — full Appointments, Studio-style customization, and some accounting features are Enterprise-only, so on Community we implement equivalent capability in code rather than pretending a menu exists. The template is delivered as a clean, installable module with a proper __manifest__.py, versioned for Odoo 17.0, 18.0, or 19.0 to match your deployment.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call, confirm your service catalogue, branch structure, commission rules, and any integrations, then build on a staging instance you can review. Typical delivery is one working week from confirmed scope, after which we install on your server or Odoo.sh, run UAT with your team, and hand over the source and git repository. Pricing starts from $999 (indicative, single-company base scope); multi-branch record rules, deeper localization, payroll/commission complexity, external integrations (website booking, WhatsApp, payment terminals), and historical data migration volume increase the quoted scope. You get a fixed quote after the scoping call — never a surprise invoice.