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