← Back to Help Center
Help Center

Discounts and promos

Use discounts without killing margin.

Updated Feb 9, 2026

Overview

Pricing and commission should align with traffic, service effort, and product mix. Use discounts without killing margin.

Diagnostics

  • Assess traffic and location expectations.
  • Compare nearby retail pricing.
  • Estimate service frequency and costs.

Resolution steps

  • Set prices based on location type and margin targets.
  • Offer a commission range with performance incentives.
  • Explain how pricing supports reliable service.

Preventive maintenance

  • Review prices quarterly.
  • Avoid underpricing in high-traffic sites.
  • Communicate price changes before they occur.

When to contact support

  • Offer a limited-time promo for new placements.
  • Revisit commission if service costs increase.
  • Use a sales review after 60 days.

See packages and pricing at /pricing. Start with leads at /vending-leads or /hot-leads.

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