What changes in car washes operations
Car wash networks track locations, membership activity, wash programs, and seasonal operating changes. Their shared workspace should make it easy to find a location, understand which quantity rule applies, and see what still needs review. A clear distinction between saved location quantities, per-cycle entries, and effective prices prevents local exceptions from becoming permanent network assumptions.
Watch for these gaps
- Treating a paused location as a zero-producing active location
- Using membership totals when the rule counts completed washes
- Losing the reason for a temporary seasonal override
A repeatable franchise quantity entry workflow
- 01
Open Unit billing and select the active rule and cycle that need quantities.
- 02
Review the assigned franchise rows and enter the changing per-cycle amounts.
- 03
Preview the batch and resolve any validation or stale-row feedback.
- 04
Finalize eligible entries and keep the resulting period state available for review.
Bring the industry records into the review
For car washes, use wash location roster with active, paused, or archived state; membership or wash-program quantities by reporting cycle; location-level price overrides and change history 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 selected rule, reporting period, or franchise set is uncertain.
Stop and select the correct rule and cycle when the workspace context does not match the intended period.
Assigned franchise rows are being reviewed for the current cycle.
Enter only the quantities that changed and preserve an unchanged value when the source confirms it.
Validation or concurrent-change feedback is present.
Resolve missing, invalid, or stale-row feedback before approving the batch.
The preview matches the source and review is complete.
Finalize only the rows shown as eligible in the preview and retain the batch result.
A common mistake to avoid
Replacing a blank or unchanged quantity with zero without confirming that zero is the intended source value.
Before you mark the work complete
A cycle quantity batch with the selected rule and period, changed rows, validation results, preview outcome, and finalization owner.
- The selected rule and period are correct.
- Validation and stale-row feedback are resolved.
- The preview is eligible before finalization.
Check location state before reviewing cycle quantities, especially after a pause or reopening. Confirm the unit label matches the source count, distinguish a saved quantity from a per-cycle entry, and review effective price after any override. Close the cycle only after overdue locations, deliberate zeros, and temporary adjustments have been addressed.
Download the car washes review worksheet →A situation to work through
A car wash operator can select a wash program, search for a location, and see the organization price, local override, effective price, and cycle quantity in one row. A paused location can remain visible for historical review without receiving new active work. When a count changes, the operator saves the row after previewing its current version and resulting amount.
Apply the franchise quantity entry 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 do teams enter recurring franchise quantities?
Open the unit billing workspace for a rule, review assigned franchises, enter per-cycle quantities, preview the batch, resolve validation or stale-row feedback, and finalize eligible entries. The preview keeps the period and rule context visible before changes are applied.
Put the workflow into practice
Granite's unit billing workspace connects franchise quantities to a preview and eligible finalization.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.