What changes in moving and storage operations
Moving and storage networks coordinate branches, move volume, storage units, seasonal demand, and local operating changes. A central team needs to distinguish recurring storage activity from project-based moves and see which branches still need to report. Keep branch assignments, period quantities, effective prices, and document follow-up in one reviewable workspace rather than stitching together dispatch and billing spreadsheets.
Watch for these gaps
- Using move jobs to explain recurring storage-unit quantities
- Ignoring a seasonal branch whose reporting period is overdue
- Changing an assignment instead of correcting a submitted quantity
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 moving and storage businesses, use branch directory with service area and operating state; move, storage, or recurring-unit quantities by cycle; branch exceptions, correction history, 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.
Start by separating move volume from recurring storage units and confirming the branch's active status. Check the expected reporting cadence, then review blanks, zeros, overrides, and overdue rows. Use the rule's effective price when assessing the amount, and resolve stale versions before saving any correction so one branch cannot overwrite another reviewer's work.
Download the moving and storage review worksheet →A situation to work through
A moving network can review an open cycle by branch, search for a location, and see storage units or move counts beside their rule and effective amount. A branch with an overdue submission is easy to distinguish from one that intentionally reported zero. The operator can save a corrected row after preview and retain the branch's period-specific history for later questions.
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.