Vending business insurance checklist

General liability is the baseline. Some locations require higher limits, workers’ compensation, or additional insured certificates.

Keep certificates updated and stored digitally so you can provide proof quickly during onboarding or audits.

• Keep COIs (certificates of insurance) for each location.
• Maintain policy declarations and coverage limits.
• Track renewal dates and endorsements.

• Many sites require “additional insured” status.
• Some require umbrella coverage or higher limits.
• Update COIs when adding new locations.

• Review coverage annually with your broker.
• Increase limits as route size grows.
• Store digital copies for quick access.

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

• Skipping a controlled test leads to false positives.
• Updating hardware without documenting configuration changes.
• Forgetting to verify payout, refund, or reconciliation data after changes.

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

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

• Test with known-good inputs and controlled conditions.
• Validate telemetry, alerts, and payment logs where applicable.
• Confirm location expectations and update the site contact.

• Configuration drift after firmware or component swaps.
• Inconsistent power or network conditions at the location.
• Gaps in preventive maintenance routines.

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

• Keep permits and insurance certificates current.
• Store contracts in a single shared repository.

• Review incident logs and update policies quarterly.