What changes in salons and barbershops operations
Salon and barbershop groups manage locations with different service mixes, staffing patterns, and local schedules. Corporate operators need a consistent place to review recurring units and location exceptions without flattening those differences into one total. Organize each record around the location, the specific rule, the period, and the person responsible for resolving an incomplete or unusual submission.
Watch for these gaps
- Combining membership counts with appointment counts without a rule
- Leaving a manager's access active after a location handoff
- Assuming a blank month means the same thing as zero services
A repeatable unit-based billing rule setup workflow
- 01
Open Billing Rules and choose the unit-based rule family.
- 02
Set the organization price, unit labels, cadence, quantity mode, reminders, and payment destination.
- 03
Choose the franchise assignment policy and review the next complete billing cycle.
- 04
Resolve readiness blockers before activating the rule for future cycles.
Bring the industry records into the review
For salons and barbershops, use location roster with manager, operating status, and service profile; recurring membership or service-unit counts by period; location corrections, price overrides, and document requests as the evidence packet. Keep the franchise and reporting period attached to each record so a reviewer can follow the source without reconstructing the conversation.
What to do when the review finds a problem
The rule's recurring charge is being defined.
Set the unit price, label, and cadence together so the future charge has an unambiguous basis.
The rule can use changing quantities or a fixed configured quantity.
Choose a quantity mode that reflects where the cycle's count will come from.
The pricing and quantity decisions are complete.
Confirm assignments, reminders, and payment destination before activation.
The rule is ready for a future-cycle readiness check.
Review the next complete billing cycle and resolve blockers before publishing.
A common mistake to avoid
Using a quantity override to conceal a missing franchise assignment or unclear unit definition.
Before you mark the work complete
A unit-rule specification that states price, unit label, cadence, quantity mode, assignment policy, reminders, route, and next cycle.
- The unit price, cadence, and quantity mode are intentional.
- Assignments and payment destination are ready.
- The next cycle and activation blockers are understood.
Confirm the location's service rule and manager before reviewing the count. Keep membership, appointments, and add-on services in distinct units, and make the blank-versus-zero decision explicit. Review overrides against the organization price, check for handoff-related access changes, and inspect the period history before marking the location complete.
Download the salons and barbershops review worksheet →A situation to work through
A salon group can open a cycle, search one location, and quickly see whether its submitted membership quantity is complete and how the amount was derived. The operator can keep a blank open while waiting for the manager, record an intentional zero when appropriate, and review the change history alongside the location's current access and assignment state.
Apply the unit-based billing rule setup steps above to this situation. Record the original evidence, the unresolved question, and the person who can answer it before treating the item as complete. This is a planning example, not a customer result.
What does a unit billing rule need before activation?
Set the unit price and labels, cadence, quantity mode, assignment policy, reminders, and payment destination. Review the next cycle and readiness blockers, then activate only when the rule clearly explains the future franchise charge.
Put the workflow into practice
Granite's unit-based billing rules connect quantity settings and assignments to future billing cycles.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.