Master Licensee's Guide to HB 353: Managing Compliance Across Multiple Locations

Single-location operators have it relatively simple: choose a payout provider, install the equipment, train the staff, and go live. Master licensees face an entirely different challenge. You need to roll out compliant payout systems across dozens or hundreds of locations, each with different staffing situations, floor layouts, player demographics, and technology infrastructure.

This guide addresses the specific concerns of master licensees managing fleet-scale HB 353 compliance.

The Scale Challenge

Managing compliance across a portfolio of COAM locations introduces complexity that single-location guides do not address:

• Varied location types – Your locations may include convenience stores, gas stations, restaurants, bars, laundromats, and other venue types, each with different operational realities
• Inconsistent staffing – Some locations have dedicated attendants; others have minimal staff who are already handling multiple responsibilities
• Geographic spread – Locations across the state mean you cannot physically be at every site during rollout
• Different technology levels – Some locations have modern POS systems; others are still largely manual
• Relationship management – Each location owner has different expectations and concerns about the transition

Centralized Payout Management

The foundation of a successful multi-location rollout is centralization. Rather than managing separate payout setups at each location, you need a single platform that provides:

• Unified dashboard – See payout activity, transaction volumes, error rates, and compliance status across all locations from one interface
• Remote monitoring – Receive alerts when a location's payout system goes offline, encounters errors, or shows unusual patterns
• Centralized configuration – Update payout rules, limits, and settings across multiple locations without visiting each site
• Role-based access – Give location managers visibility into their own location's data while maintaining portfolio-wide oversight

API Integration

For master licensees with existing COAM management systems (CMS), API integration is critical. Your payout provider should offer a well-documented API that allows:

• Machine-to-payout connectivity – Winnings from your CMS trigger payout transactions automatically, reducing manual steps and errors
• Real-time data sync – Payout data flows back into your CMS for unified reporting
• Automated reconciliation – Match machine payouts to card loads programmatically rather than manually
• Custom webhooks – Receive real-time notifications for specific events (large payouts, system errors, compliance alerts)

If your CMS does not support API integration, look for a payout provider that offers a standalone management portal with bulk operations capabilities.

White-Labeling and Branding

As a master licensee, you may want the payout experience to reflect your brand rather than the technology provider's. Look for solutions that offer:

• Custom branding on kiosk interfaces and player-facing screens
• Branded receipt printing with your company information
• Co-branded gift cards featuring your logo alongside the Visa/Mastercard mark
• Custom signage templates you can deploy across all locations

Consistent branding across your fleet reinforces your identity with players and location owners alike.

Multi-Location Reporting

Georgia Lottery Commission reporting requirements apply to every location individually, but as a master licensee, you also need aggregate views. Your reporting system should support:

• Location-level reports – Detailed transaction data for each individual site
• Portfolio-level dashboards – Aggregate metrics across all locations (total payouts, average payout size, transaction volumes)
• Regional grouping – Group locations by city, county, or custom regions for performance comparison
• Automated compliance reports – Schedule reports to generate and deliver automatically on the cadence required by regulators
• Export capabilities – Download data in formats compatible with your accounting and tax systems

Phased Rollout Strategy

Attempting to deploy payout systems at all locations simultaneously is a recipe for problems. A phased rollout allows you to learn and adjust as you go:

Phase 1: Pilot (2–3 Locations, 4–6 Weeks)

• Select locations that represent your range of venue types
• Deploy the full payout system and run live transactions
• Document every issue, question, and piece of player feedback
• Refine your processes, training materials, and signage based on pilot results

Phase 2: Expansion (25% of Locations, 4–6 Weeks)

• Roll out to approximately one quarter of your locations using lessons from the pilot
• Begin training location managers to handle routine support themselves
• Validate that centralized monitoring and reporting work at a larger scale

Phase 3: Broad Deployment (Remaining Locations, 6–8 Weeks)

• Deploy to all remaining locations with a well-tested playbook
• Use your trained pilot-phase staff to support onboarding at new locations
• Monitor closely during the first two weeks at each new location

Phase 4: Optimization (Ongoing)

• Analyze performance data across all locations
• Identify and address underperforming sites
• Continuously improve training, signage, and player communication

Training at Scale

Training one location's staff is manageable. Training staff across 50+ locations requires a scalable approach:

• Train-the-trainer model – Identify a champion at each location who receives in-depth training and then trains their team
• Video training library – Create short, focused training videos that staff can watch on their own schedule and refer back to
• Quick reference cards – Laminated step-by-step guides that can be kept at the counter or near the kiosk
• Remote support line – A phone number or chat support system that location staff can reach when they encounter issues in real time
• Periodic assessments – Simple check-ins to verify that staff at each location remain proficient

Cost Modeling for Fleet Deployment

Master licensees need to model costs carefully across the portfolio. Key variables to consider:

• Hardware costs – Multiply per-unit kiosk costs by the number of locations. Negotiate volume pricing with your provider
• Per-transaction fees – Model costs based on your actual payout volume across all locations. Higher aggregate volume often qualifies for lower per-transaction rates
• Installation and setup – Factor in the labor and logistics of deploying hardware across geographically dispersed sites
• Training costs – Budget for initial training across all locations, including travel for in-person sessions if needed
• Ongoing support – Technical support, hardware maintenance, and software updates at scale
• Savings offsets – Reduced cash handling, lower shrinkage risk, automated reporting, and operational efficiency gains

For large portfolios, the per-location cost often decreases significantly as volume-based pricing and shared infrastructure reduce the marginal cost of each additional site.

Managing Location Owner Relationships

Your location owners may have concerns about the transition. Proactive communication is essential:

• Explain the legal requirement clearly—this is not optional
• Emphasize that you are handling the technology and logistics
• Address their specific concerns (space for a kiosk, staff time, player reaction)
• Provide a clear timeline so they know what to expect and when
• Share positive results from your pilot locations to build confidence

The Bottom Line

Master licensees who approach HB 353 compliance strategically—with centralized management, phased rollouts, and scalable training—will not only meet the July 2026 deadline but will likely come out of the transition with a more efficient, data-driven operation.

The key is to start now, pilot early, and build the infrastructure that will support your entire portfolio. The operators who treat this as a one-location-at-a-time problem will struggle. Those who treat it as a fleet management challenge will thrive.