← Back to Help Center
Compliance & Insurance
Health permits and compliance basics
Know what permits you need and how to keep records ready for inspection.
Updated Feb 9, 2026
Overview
Check local health department requirements for food and beverage machines and apply for permits before installation. Requirements vary by county and state.
Maintain cleaning logs, product sourcing records, and temperature checks when applicable. Keep permits accessible at your office or with your route binder and renew them on time.
Documentation
- Keep permits, sanitation logs, and product invoices.
- Store temperature checks for refrigerated units.
- Maintain service records for inspections.
Site requirements
- Verify if the location needs proof of permits on-site.
- Confirm any local labeling or nutritional requirements.
- Keep a compliance binder on the route truck.
Renewal cadence
- Review permits annually and track renewal dates.
- Update documentation after any inspection findings.
- Keep digital copies for quick access.
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.
Compliance guidance
Documentation
- Keep permits and insurance certificates current.
- Store contracts in a single shared repository.
Risk control
- Review incident logs and update policies quarterly.
permitscompliancerecords