How to calculate stylist pay so that nobody argues

If you ask salon owners which routine costs them the most nerves, payroll is almost always in the top three. Yet the arithmetic itself is elementary: percentages, salaries, sometimes a combination. The difficulty is not in the maths. The difficulty is that at the end of the month two people calculate the same thing from different data and get different results.

Where the discrepancies come from

• The stylist remembers a visit that in the system is recorded under a different stylist, or not recorded at all.
• The appointment lists one service but a different one was actually done, and nobody corrected the record.
• The manager gave a discount, but the stylist's percentage was calculated on the pre-discount amount — or the other way round, with no agreement about it.
• A card payment went through with an acquiring fee, and it is unclear whose share it comes out of.
• Some visits were paid with bonus points, and it is unclear whether that counts as revenue for the calculation.

The pay scheme has to be chosen explicitly

The first thing worth doing is fixing the scheme in words, and then in settings. homade supports three options: a percentage of services delivered, a fixed salary, and a mixed scheme with a base plus a percentage. What matters is not which scheme is better — there is no universally better one — but that it is set in the system and understood the same way by both sides. The full list of the product's capabilities is on homade.

The stylist has to see their own calculation

This is probably the single change that removes most of the conflicts. When a stylist can see their own calculation — which visits it is made up of, which services were counted — the discussion stops being emotional. Instead of "it feels like less than usual" you get something concrete: this appointment was closed under someone else. At the same time a stylist sees only their own calculation and has no access to anyone else's figures, which matters both for privacy and for the atmosphere in the team.

Why the calculation should come from the visit card

Pay calculated from a separate spreadsheet will always diverge from reality, because the spreadsheet is filled in separately from the work. If instead the calculation is built on visit cards with their set of services and payment, the data goes into it at the moment the client is served, not at the end of the month from memory. There is a pleasant side effect: the manager does not need to keep a separate "payroll log".

Discounts, bonuses and acquiring: agree in advance

These three things create almost all the disputed situations, and they are resolved not by technology but by an agreement that the technology then simply enforces. Decide in advance: is the percentage calculated on the discounted amount or not; do redeemed bonus points reduce the basis for the calculation or not; is the acquiring fee a salon expense or is it shared. After that a system with separate tills and automatic fee deduction just applies the rule the same way to every visit. You can see how it looks at homade.ru.

Roles and access: who can edit records at all

Another quiet cause of disputes is records changed after the fact. If anyone at all can adjust the set of services in a closed visit, trust in the calculation falls even when everyone is honest. Role-based access rights limit who changes what, and the "stylist sees only their own appointments" mode removes the very possibility of accidentally editing someone else's visit. Our general approach to data security is described on cybersecurity.

What to do if your salon's scheme is non-standard

There are more complicated arrangements: different percentages by service category, tiers depending on output, separate terms for chair renters. Some of that maps onto the mixed scheme, some does not. If your case does not fit an off-the-shelf product, we build systems around specific processes: CRM and ERP development. And the easiest way to start testing is the free Solo plan for one stylist — the plans are listed on homade, and questions can go through technical support.