Skip to main content
GullySystem
Wellness

Commission and Incentives for Yoga 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.

Teachers are paid per class taught, with one rate for small batches and another for workshops. Studio rental by guest teachers is split. Membership sales earn the front desk a share.

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.
Yoga studios

How the business operates.

Most studios start with a printed timetable and a notebook. That works for one room and one teacher. It fails once passes expire in different weeks and three teachers cover seven batches, because nobody can say who is owed classes or what each teacher has earned.

Class schedule and batches

Lay out the weekly timetable by room, teacher and style, with batch size, a substitute teacher and a cancelled session recorded on the same grid. A change reaches the students booked.

Booking and waitlist

Students reserve a mat for a batch. A full class opens a queue, and the first name in it is offered a freed place by message. The rest wait their turn.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Class schedule and batches. Set the weekly timetable by style, hall, teacher and batch time. Changes show at once. Substitutions and public holidays reach every student the moment the desk saves them.
  • Student records. Keep contact details, goals, injury and pregnancy notes, plan history and attendance for every student. The teacher reads the notes before class and adapts the poses for a sore knee or a stiff back.
  • Booking and waitlist. Students reserve a mat in a class, and a full batch holds a waitlist. Cancellation closes before the class starts, and the freed mat passes to the next name in line without a call from the desk.
  • Attendance and check-in. Mark who came from the teacher’s phone, a desk list or a scanned QR code. The session is counted against the pass or the membership. The dated register stays on record for every class, so an absent student is never charged.

Operational bottlenecks to check

Pass balances are not written against the student

A student claims four classes left, the desk thinks two. Without a count that falls at each check-in, the argument is settled by whoever is more polite on the day.

A full room has no waiting list

Eight mats are booked, a ninth student arrives, and cancellations come in too late to use. Nobody is called from a queue, so the freed mat stays empty.

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. Enquiry and trial

    An enquiry arrives by phone, WhatsApp or the website. Front-desk staff book a trial class and note the student’s goals, any back or knee injury and any pregnancy, so the teacher is prepared.

  2. 2. Joining

    The student picks a monthly membership, a ten-class pass or a drop-in. The payment is recorded, and the plan starts on the date chosen, not the day it was paid. Then the first class is booked.

  3. 3. Booking

    The student reserves a mat in a batch. A full class opens a waitlist. A cancelled mat goes to the next name.

  4. 4. Class

    The teacher opens the class on a phone and marks who is on a mat. One session comes off the pass, or the day counts against the membership, before savasana ends. The register is dated and timed.

  5. 5. Month end

    Classes taught by each teacher meet the rate agreed for them. Substitutions and covered batches are counted to whoever took the room, and the month’s payout is ready for the owner to approve.

  6. 6. Renewal

    Students whose plan is ending are listed a week ahead. A reminder goes through WhatsApp, text message or email. The renewal is recorded when payment is taken, so the plan carries on without a gap.

Industry reports to connect with

  • Attendance by class, batch, hall and teacher
  • Active memberships and ten-class passes with sessions left
  • Renewals due, frozen plans and lapsed students
  • Collections by plan, intensive, teacher training and retail

Questions before implementation.

When should yoga 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