← Back to Help Center
Location Issues
What to do when a location underperforms
Improve product mix, adjust pricing, and collaborate with site contacts.
Updated Feb 9, 2026
Overview
Review sales by SKU and identify the bottom 20 percent. Replace slow movers with proven sellers and test new items in small quantities.
Compare pricing to nearby convenience retail. Small price increases can work in high-traffic sites; price reductions may be needed in price-sensitive locations.
Meet with the site contact to confirm traffic patterns and consider relocating the machine to a higher visibility area.
Data to review
- 4–8 week sales trend by SKU and daypart.
- Stockout frequency and missed sales events.
- Commission terms and service cadence.
Recommended response
- Refresh the planogram and test new items for 2–4 weeks.
- Adjust pricing based on local benchmarks.
- Document a performance improvement plan with the location.
Prevention
- Set service level expectations in writing.
- Track sales per visit and optimize refill timing.
- Use signage or product mix changes for seasonal demand.
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.
Location management notes
Relationship hygiene
- Confirm service frequency expectations in writing.
- Provide clear escalation contacts for urgent issues.
Performance review
- Track sales per location and adjust product mix.
salespricingproduct mix