What changes in appliance repair operations
Appliance repair networks coordinate dispatch branches, maintenance programs, warranty-related work, and recurring service plans. Corporate teams need branch-level quantities that are easy to compare without blending one-time calls with recurring units. A focused record shows the rule, cycle, price source, owner, and next action so an incomplete report can be resolved before the period is closed.
Watch for these gaps
- Counting dispatched calls when the rule counts completed visits
- Combining warranty work with customer-paid service units
- Allowing a branch to submit a stale count after another edit
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 appliance repair businesses, use branch roster with service area and operating status; maintenance-plan or recurring-call quantities by period; branch corrections and supporting service-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 whether the unit counts dispatched, completed, or recurring work, and keep warranty activity separate when the rule requires it. Review branch status and period owner, then inspect blank, zero, and overridden rows. Preview changes before saving, and reload any stale row instead of applying a correction to an outdated version.
Download the appliance repair review worksheet →A situation to work through
An appliance repair operator can filter to a branch, compare its completed service quantity with the configured rule and effective amount, and see whether the row is open or ready. A warranty exception stays visible without changing the rule for every branch. Before saving a revised count, the operator checks the row version and reviews the proposed result.
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.