Salon & Spa Management for Business Central

Key Features

Appointment calendar page with day, week and staff-column views, drag-to-reschedule, and conflict detection across resource, room and equipment in a single availability query

Staff skill matrix on an extended `Resource` table: a service is only bookable to a resource holding the required skill code, with certification expiry dates that withdraw a stylist from availability automatically

Service master extending `Item` and `Resource` with duration, pre-buffer, post-buffer and processing-gap minutes, so a colour service releases the chair during development time

Room and equipment requirement codes per service, validated against a capacity table so treatment rooms and shared equipment cannot be over-committed

Service packages and courses of treatment held as a drawdown balance in a posted, non-editable Membership Ledger Entry table following Business Central ledger-entry conventions

Deferred-revenue handling for prepaid packages and memberships: cash recognised as a liability on sale, revenue recognised per session consumed via the standard deferral schedule

Table-driven commission rules by staff, service group, retail item category, revenue band and date-effective promotion, with separate service and retail rates per stylist

Nightly commission accrual through a `Job Queue Entry` writing Commission Ledger Entries that drill back to the originating posted sales line, plus a payroll export dataset

Gift voucher and gift card issue, part-redemption and expiry posted through the sales document, so the liability sits on the balance sheet rather than in a spreadsheet

Membership tiers that flow a discount percentage or customer price group into the sales line at booking and at POS, honouring standard price and discount priority

Retail POS and online booking integration over `API pages` on REST API v2.0 plus OData v4 endpoints for availability, booking creation and voucher balance lookup

Event subscribers on `Codeunit 80 Sales-Post` so every appointment and retail sale produces a genuine posted sales invoice with correct VAT, dimensions and customer ledger entries

Dedicated permission sets separating front desk (book, take payment), management (commission rules, pricing) and finance (posting, deferrals) roles

Dimension defaulting by location, stylist and service group, so profitability by chair, by therapist and by treatment room is reportable in standard analysis views

Power Platform and Dataverse connectivity for a front-desk canvas app, appointment reminders via Power Automate, and Power BI utilisation and commission reporting

Application Insights telemetry on booking search, availability calculation and commission runs for diagnosable performance on peak trading days

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

A salon or spa runs on two clocks at once. The first is the chair: a colour service that blocks a senior stylist for 140 minutes with a 30-minute processing gap in the middle, a therapist certified for hot stone but not for microdermabrasion, a treatment room that holds one bed. The second is the till: retail shampoo sold at the desk, a prepaid 10-session package drawn down one visit at a time, a gift voucher issued in December and redeemed in March, and a payroll run where every stylist is owed a different percentage on service versus retail. Dynamics 365 Business Central is genuinely strong at the second clock — items, sales, inventory, VAT, receivables — and has essentially nothing for the first. There is no resource-and-room calendar with skill matching, no service menu with duration and processing gaps, no commission engine that splits service and retail at different rates, and no deferred-revenue treatment for a package the customer has paid for but not yet consumed. Salons end up running a separate booking SaaS and re-keying the day's takings, which means Business Central knows the money but never the margin per stylist, per chair, per hour.

We close that gap inside Business Central rather than beside it. The extension is delivered as an AL app — a per-tenant extension for your SaaS environment, or an AppSource-format app package if you prefer that packaging. Staff are modelled on Resource with a new Staff Skill matrix and working-calendar assignment, so a colour service can only be booked against a resource holding the matching skill code and an available room. Services extend Item and Resource with duration, buffer, processing-gap and room-requirement fields; packages are composed as service lines with a drawdown balance held in a new Membership Ledger Entry table that follows Business Central's own ledger-entry conventions — posted, non-editable, reversible only through a correcting entry. Booking, drawdown and commission calculation live in codeunits, and posting is wired to the standard routines through event subscribers on Codeunit 80 Sales-Post and Codeunit 12 Gen. Jnl.-Post Line, so a salon sale is a real posted sales invoice with the right G/L, VAT and dimension postings — not a parallel set of books.

Commission rules are table-driven — rate by staff, service group, retail item category, revenue band or date-effective promotion — and a Job Queue Entry accrues commission nightly into a Commission Ledger Entry table ready for your payroll export. Front desk staff work on purpose-built list and card pages plus a day/week calendar page. The retail lane integrates with your existing POS through API pages on REST API v2.0, and OData v4 endpoints expose availability, bookings and voucher balances to an online booking site or a Power Apps canvas app over Dataverse. Everything ships with its own permission sets, so a receptionist can book and take payment without seeing the G/L, and telemetry is emitted to Application Insights so slow availability searches are diagnosable on a busy Saturday.

Because it is built for your business rather than bought off a shelf, the shape follows your operation. A single-site salon with six chairs gets a lean build: calendar, service menu, commission, vouchers. A ten-location spa group gets location-aware availability, per-site commission schemes, inter-site voucher redemption settled between location dimensions, and membership tiers that carry discount rates into the sales line. Where you already run a booking front end, you keep it and we integrate through the API layer instead of replacing it.

Delivery is build-to-order, and we are direct about what that means. Nothing is downloadable today. We start with a scoping call, agree the service catalogue, commission rules, membership mechanics and POS integration in writing, and quote against that scope. Typical delivery is two to four weeks from confirmed scope, depending on how many commission variants and integrations are in play. We build against your Business Central release wave — SaaS online or on-premises — install into a sandbox first, run user acceptance testing with your front-desk and finance staff on real service and price data, then promote to production in an agreed window with a documented rollback. You receive the AL source, the git repository, and a support window after go-live. If your requirement turns out to be a poor fit for a build — for instance you need a consumer booking marketplace rather than an ERP-side scheduler — we will say so at the scoping call rather than sell you a project.

What you get

Installable AL extension packaged for your Business Central version and deployment type — per-tenant extension for SaaS, or an app package for on-premises — with complete source code

Installation and configuration on your sandbox and production environments, including permission set assignment and job queue setup for commission accrual

Technical documentation: object ID ranges, table and page extension inventory, event subscriber map, API and OData endpoint reference with sample payloads, and upgrade notes

End-user guide plus a live training session for front-desk, management and finance staff, recorded for future hires

User acceptance testing on your staging environment against your real service catalogue, price list and staff roster, with a written rollback plan for the production promotion

Initial data load of services, packages, staff skills, commission rules and outstanding voucher and package balances from your current booking system or spreadsheets

Git repository handover with full commit history, branch model and build configuration, so your team or another Business Central partner can maintain the code

Post-go-live support window covering defect fixes, configuration questions and compatibility with the next Business Central release wave

Who this is for

Salon or spa owner-operator

Runs one to three sites and currently juggles a booking SaaS, a card terminal and Business Central. Wants bookings, the retail till and the commission run in one system so month-end stops being a reconciliation exercise, and wants margin per chair rather than just total revenue.

Operations or salon manager

Owns the rota, the service menu and the front desk. Needs skill-aware booking so a junior is never scheduled onto a service they are not certified for, needs the calendar to respect processing gaps and room capacity, and needs to change a commission rate for a promotion without raising a support ticket.

Finance manager or controller

Responsible for the numbers a prepaid package creates. Needs deferred revenue treated correctly, voucher liability visible on the balance sheet, commission accrued in the right period, and every transaction traceable back to a posted sales invoice with the correct VAT and dimensions.

IT lead or incumbent Business Central partner

Will live with this extension through the next release waves. Cares about clean AL — proper object ID ranges, event subscribers rather than base-code changes, a documented API surface, permission sets, and a git repository they can build from without depending on ECOSIRE.

How Salon & Spa Management for Business Central Compares

Criterion	ECOSIRE	Custom Build	Competitor	Dynamics 365 Business Central Native
Fit to your service menu and commission scheme	Built from your actual catalogue, rota and commission rules, agreed in writing at scoping	Same fit is reachable, but you carry the analysis and design work in-house	Configurable within the vendor's model; anything outside it becomes a change request or never happens	No salon concepts at all — services, chairs, packages and commissions have no representation
Scheduling with staff skills and room capacity	Calendar page with resource, room and equipment conflict detection and skill-matched booking	Buildable, but availability across three constraint types is where most in-house builds stall	Often strong on calendar, weaker on ERP-side posting and dimension detail	Resource capacity planning exists for jobs, not for chair-and-room retail booking
Time to a working system	Two to four weeks from confirmed scope, with a fixed quote before work starts	Typically months once hiring or upskilling an AL developer is counted	Installs in a day, then weeks of configuration and workaround discovery	Available immediately, but the salon-specific gaps stay open permanently
Financial correctness of packages and vouchers	Deferred revenue and voucher liability posted through standard sales posting and deferral schedules	Depends entirely on whether your developer knows the Business Central posting routines	Varies widely; many hold balances in their own tables and post only a daily summary	Deferral schedules exist, but nothing links them to session consumption
Code ownership and lock-in	Full AL source and git repository handed over; any partner can maintain it	You own it outright, and you also own every future fix	Vendor-owned binary; you are tied to their roadmap, pricing and support quality	Microsoft-owned platform code, not extensible for this without a build
Release-wave upgrade path	Tested against the next wave and updated within your support window	Your team retests and repairs on every wave	Vendor usually updates, but on their schedule and sometimes behind the wave	Microsoft handles upgrades; there is nothing salon-specific to break
Integration with existing POS and booking site	API pages on REST API v2.0 and OData v4, plus custom adapters where a vendor needs one	Fully open, but the integration design and testing are yours	Integrates with the partners the vendor has chosen, rarely with yours	Standard APIs exist but expose no booking, package or commission data
Cost profile over three years	One-off build cost plus an optional annual support and compatibility agreement	Developer salary or day rate, ongoing, whether or not the system is changing	Per-user or per-location subscription forever, rising as you add sites	No extra licence cost and no capability — the cost is paid in manual work

Frequently Asked Questions about Salon & Spa Management for Business Central

How long does delivery take, and can I download it today?

There is no download. This is build-to-order: we scope your service menu, commission rules, membership mechanics and integrations first, then build against that written scope. Typical delivery is two to four weeks from confirmed scope. A lean single-site build sits at the short end; a multi-location group with per-site commission schemes, an online booking integration and migration from an existing booking platform sits at the longer end. The scoping call gives you a date and a fixed quote before any work starts.

Does this work with Business Central SaaS, on-premises, or both?

Both. For Business Central online we deliver a per-tenant extension (or an AppSource-format app if you prefer that packaging) that installs into your sandbox and then production through standard extension management. For on-premises we deliver the app package for your specific version. We build against your current release wave and confirm at scoping which wave your environment is on, because that determines which platform features we can rely on.

What happens with support and Business Central release-wave updates?

Every build includes a post-go-live support window for defect fixes and configuration questions, agreed at scoping. Microsoft ships two major release waves a year; we test the extension against the next wave and supply a compatibility update within that window. Beyond it you can take an annual support and compatibility agreement, or maintain it yourself — you hold the full AL source and the git repository, so you are never locked to us.

Can it integrate with the POS terminal and online booking site we already use?

Usually yes, and that is often the better outcome. We expose availability, booking creation, package drawdown and voucher balances through API pages on REST API v2.0 and OData v4, so an existing booking site or POS can read and write against Business Central directly. If your POS only supports file or webhook exchange, we build that adapter instead. Bring the vendor's API documentation to the scoping call and we will tell you honestly whether the integration is a half-day or a two-week job.

How are stylist commissions actually calculated and paid?

Commission rules are data, not code — configured by staff member, service group, retail item category, revenue band and date-effective promotion, with separate service and retail rates. A job queue entry runs nightly and writes Commission Ledger Entries that drill back to the originating posted sales line, so a stylist can see exactly which appointments and retail sales produced their figure. The result exports as a payroll dataset in the format your payroll provider expects; we agree that format at scoping.

How do prepaid packages and gift vouchers appear in the accounts?

Correctly, which is the point of doing this inside Business Central rather than in a booking app. Cash from a prepaid package or voucher is recognised as a liability on sale, and revenue is recognised session by session as the client consumes it, using the standard deferral schedule and G/L posting. Voucher liability and unredeemed package balances are reportable at any date — which matters at year end, and matters more if the business is ever audited or sold.

What do I actually own at the end of the project?

The AL source code, the git repository with full commit history, the technical documentation, and the right to modify or extend it. We do not ship obfuscated code or hold the repository. If you later want your own developer or a different Business Central partner to take it on, they can clone, build and deploy it without us.