← Back to Help Center
Operations & Inventory
Route planning for growing operators
Optimize service cadence, stocking priorities, and drive-time efficiency.
Updated Feb 9, 2026
Overview
Cluster locations by geography to reduce drive time, then layer in service urgency. Use telemetry or manual sales logs to prioritize high-volume sites and prevent stockouts.
Set minimum stock levels per category and schedule visits based on sell-through rates. Rebalance the route monthly and remove low-performing stops that consume time without revenue.
Metrics to track
- Sales per visit and stockout rate.
- Service time per stop and drive time between stops.
- Gross margin per location.
Improvement actions
- Prioritize high-velocity locations early in the route.
- Adjust visit frequency based on sell-through.
- Drop low-performing stops that consume time without margin.
Prevention
- Use route templates for consistent scheduling.
- Standardize refill quantities by location type.
- Review route performance monthly.
Expanded guidance
- Confirm all steps are documented so the next technician can reproduce the results.
- Capture before/after metrics (errors cleared, sales restored, or uptime improved).
- Review machine, reader, or route settings to ensure they match location standards.
Common pitfalls
- Skipping a controlled test leads to false positives.
- Updating hardware without documenting configuration changes.
- Forgetting to verify payout, refund, or reconciliation data after changes.
Next-step checklist
- Run a final test with known-good inputs.
- Log the outcome with date, time, and device identifiers.
- Schedule a follow-up check if the location has high traffic or seasonal demand.
<!-- expanded:v2 -->
Additional details
Operational notes
- Document changes with time, machine ID, and location name.
- Verify settings, pricing, and service modes after each fix.
- Capture before/after results to confirm resolution.
Field checklist
- Test with known-good inputs and controlled conditions.
- Validate telemetry, alerts, and payment logs where applicable.
- Confirm location expectations and update the site contact.
Common root causes
- Configuration drift after firmware or component swaps.
- Inconsistent power or network conditions at the location.
- Gaps in preventive maintenance routines.
Next steps
- Monitor for 7 days and note any repeat errors.
- Schedule follow-up if the site is high-traffic.
- Escalate with full logs and photos if issues repeat.
Operations guidance
Inventory
- Use a consistent par-level system per location.
- Reconcile spoilage weekly to protect margins.
Route efficiency
- Group stops by distance and service priority.
routesinventoryscheduling