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 billing readiness review workflow
- 01
Open the organization billing readiness view before starting invoice processing.
- 02
Read each surfaced blocker and identify the setup path that owns its resolution.
- 03
Resolve the applicable configuration, assignment, destination, or data issue.
- 04
Return to readiness and confirm the run is ready for the next approval step.
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
A readiness check identifies a missing prerequisite.
Assign the blocker to the team that owns the linked configuration or source record.
The readiness result contains mixed severity states.
Separate a warning that can be accepted from a blocker that prevents the run.
All surfaced blockers have a disposition.
Confirm the organization, franchise, period, and destination scope before declaring the run ready.
Configuration or source data has changed.
Recheck readiness after each resolution and record the final result before approval.
A common mistake to avoid
Treating an empty or failed readiness response as proof that a billing run is ready.
Before you mark the work complete
A pre-run blocker register listing scope, blocker owner, linked resolution path, decision, and final readiness time.
- Every surfaced blocker has an owner and next action.
- The linked setup path resolves the relevant prerequisite.
- Readiness is rechecked before a run is approved.
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 billing readiness review 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.
How can teams check billing readiness?
Open billing readiness before processing, review each surfaced blocker, follow its linked setup path, resolve the applicable issue, and recheck the page. This creates a clear handoff from configuration work to an approved billing run.
Put the workflow into practice
Granite's billing readiness view links each surfaced blocker to the setup path that owns its resolution.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.