Salons, spas, and barbershops sell two very different things through one till: timed services delivered by a specific person, and retail products off the shelf. Out of the box, Odoo POS treats every line as an anonymous product sale. There is no concept of which stylist performed a colour treatment, no link between the walk-in at the register and the appointment on the calendar, and no way to compute what each therapist earned from their bookings. Owners end up reconciling commissions in a spreadsheet at month-end, front-desk staff double-key appointments into POS, and there is no clean report of chair or room utilisation. Odoo Appointments and the Enterprise Field Service / Planning apps get partway there, but none of them push staff, service duration, and commission logic into the POS ticket itself.

This module is built to close that gap inside your database. We extend pos.order.line with a service-provider field so every service line carries the stylist or therapist who delivered it, and we add a service.commission.rule model (models.Model) that resolves the correct rate per employee, per service category, or per individual service — flat amount or percentage, computed on a @api.depends-driven field so totals recalculate live as the ticket changes. Bookings from the calendar surface in a POS-side panel (OWL component in the POS UI) so a front-desk agent can pull an appointment straight onto the active order, which stamps the assigned staff and expected duration automatically. Chair/room availability is modelled as a schedulable resource so double-booking is blocked at the ORM level, and a nightly ir.cron automated action rolls confirmed tickets into commission lines that feed a QWeb payout report per employee. Access is governed by ir.model.access.csv plus record rules so a stylist sees only their own commission figures while a manager sees the full store.

Everything is delivered as a proper Odoo addon with a clean __manifest__.py, migrations where schema changes touch existing data, and no core-file edits — it installs alongside standard point_of_sale and inherits rather than overwrites. Where you already run Appointments or HR, we wire into those models instead of duplicating them; commission payouts can flow to hr.payslip inputs on Enterprise or export via the JSON-RPC/XML-RPC API to your payroll of choice on Community. We build to your exact service menu, commission scheme, and receipt layout rather than shipping a rigid one-size template.

Because this is build-to-order, nothing is a pre-packaged download. After a short scoping call we confirm the exact commission rules, booking flow, and reporting you need, then build against your target version — Odoo 17.0, 18.0, or 19.0, Community or Enterprise. Typical delivery is one working week from confirmed scope. You get the module validated on a staging copy of your database first (UAT), then a supervised go-live with a rollback plan, the full source in a git repository you own, and a post-go-live support window.