Skip to main content
GullySystem
Wellness

Commission and Incentives for Nail studios

Calculate incentive amounts from approved sales or collection rules.

Sales and Distribution

Does this function belong in your operation?

Use when compensation depends on recorded sales, collections or other agreed outcomes.

A commission period is ready for review.

A technician’s pay is built from services done, add-ons and retail sold, at the rates set for each level. Tips are listed apart. The owner reviews the totals at pay time.

Bring the records the workflow depends on.

  • Eligible transactions
  • Commission rules and dates
  • Participant assignments

Outputs to check

  • Transaction-level incentive calculation
  • Adjustment and approval statement
  • Payout handoff record

Follow the commission and incentives workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Approve the scheme

    Record eligibility, calculation basis and effective dates.

  2. 2. Collect eligible activity

    Use the agreed sale or collection evidence.

  3. 3. Calculate earnings

    Apply attribution, slabs and exclusions without manual overwriting.

  4. 4. Review adjustments

    Resolve returns, reversals and approved exceptions.

  5. 5. Approve payout

    Send the authorised statement to payroll or accounts and retain settlement references.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Owner

Sets the rules and approves the month’s payout.

Accounts assistant

Runs the working, checks the holds, and pays from the same statement.

Sales executive or agent

Sees what has been earned so far this month, and which customer’s payment is keeping the rest back.

Branch manager

Reads the team’s earnings against targets, without opening anybody’s salary.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Sale later returned

Apply the approved reversal rule and show the affected prior earning.

Participant changes territory

Use the agreed attribution date rather than today's owner automatically.

Manual adjustment requested

Require a reason and approval separate from the formula result.

Can this work independently?

Calculation needs eligible sales or collection records and effective-dated rules. It can run from imports without payroll, but payroll or accounts performs the payment. Returns, credits and reversals must feed the calculation so a booked sale is not rewarded twice or retained after reversal.

Systems and records it connects with

  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Receipts management: Recorded customer payments and invoice allocations.
  • Collections and follow-up: Due balances, payment promises and follow-up outcomes.
  • Payroll: Approved pay inputs, deduction calculations and payment instructions.

Configure, test and introduce the workflow.

  • You describe how each role is paid, on paper or aloud. You get a written note of each rule in plain language to confirm. Plain words are enough.
  • Old and new rates are entered with the dates they apply from. You get a screen to check a past month against what was paid. Past months are good tests. Statements are produced for a few people from last month’s bills. They read them, and you hear what does not match. People check their own.
  • You decide what pulls a commission back and when. The rules are tested with returned orders and bounced cheques. Edge cases come out here. The accounts team prepares payouts from the statements and marks them. Staff are shown how to read their own statement. Questions drop quickly.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Calculations trace to qualifying transactions.
  • Returns follow the agreed reversal rule.
  • Rule changes use the correct effective date.
Nail studios

How the business operates.

Nail work is booked in blocks of time that differ by service. A polish change, a gel manicure, a full acrylic set and a soak-off with a fresh set all need a different number of minutes. When the diary treats them alike, the afternoon runs late and the next client waits at the door. Slots must reflect that.

Service menu with minutes and add-ons

Hold each service with its length, price and the add-ons that extend it, such as art, extensions and soak-off. Total minutes are read before a slot is offered.

Technician diary and chair allocation

Book clients to a technician and a chair, with breaks and the sanitising gap between visits kept clear. Walk-ins are fitted into the gaps that really exist.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Service menu and add-ons. Hold every service with its length and price, plus the add-ons that change them, such as chrome powder, French tips, extensions and gel removal. The summed minutes feed the diary directly.
  • Technician diary and chairs. Book by technician and by chair. Breaks, late starts and the sanitising gap between clients are respected, and a walk-in is placed only where a chair is free for the full length of the service.
  • Online booking and messages. On your studio’s own booking page the guest picks a service and a slot, then gets a confirmation and a reminder by email, SMS or chat. Late changes reach the front desk at once.
  • Client cards. Keep shade codes, shape, length, nail condition, allergy notes and photographs of finished sets on one card, so every technician reads the same history before the first brush stroke.

Operational bottlenecks to check

The diary ignores service length

A full set and a polish change look alike as slots, so one long set pushes three clients back. Technicians are blamed for a diary that was built wrong.

Shade and allergy notes live in memory

A client reacted to a primer last spring, and only the technician who did that set remembers. A new technician repeats the product. The note belongs on the card. That is avoidable.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Booking

    Booking starts anywhere. Requests come by message, phone, online page or walk-in. The desk picks the service and add-ons, and the system sums the minutes and holds a technician and chair for that length. Nothing double-books.

  2. 2. Arrival and card

    The card opens with the usual shade, shape, length and any allergy or lifting note, and a pack balance shows beside it if the client holds one. Nobody scrolls a chat history to find it.

  3. 3. Service

    Service is logged as it happens. The technician records the work done, the bottles opened and any change from the booking, and a soak-off added on the day extends the chair time and warns the next booking.

  4. 4. Billing

    The bill is made from the service lines, and payment is taken by the methods the studio accepts. An infill pack visit is counted off instead of cash when the client holds one. Tax and currency follow the country you trade in.

  5. 5. Rebooking

    Before the client leaves, the next infill date is suggested and a reminder message is queued for the days before it. A photograph of the finished set joins the card.

  6. 6. Month end

    Pay is totalled from billed lines. Each person’s rate is applied, the owner reads bottles used, packs sold and expired and retail sales beside them, and tips show against whoever earned them.

Industry reports to connect with

  • Chair hours booked against hours open, by day and technician
  • Services done by type, with average minutes against the menu length
  • Refill packs sold, used, expired and still open
  • Gel, polish and tip use against services billed

Questions before implementation.

When should nail studios consider commission and incentives?

Use when compensation depends on recorded sales, collections or other agreed outcomes. A commission period is ready for review.

What should we bring to the requirements discussion?

Bring anonymised examples of Eligible transactions; Commission rules and dates; Participant assignments. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Calculate incentive amounts from approved sales or collection rules. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Employment terms, tax treatment and payout approval remain with your authorised team.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Calculations trace to qualifying transactions. Use this check when reviewing the first working version.

Talk to us

Discuss commission and incentives for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements