Quick Answer
A vending machine connectivity plan should define the countries and venues served, cellular bands and modem, SIM or eSIM ownership, APN, roaming policy, data allowance, expected traffic, security, offline machine behavior, monitoring, support, replacement and provider-exit process. Buyers should test real machines on local networks and reconcile online status, payment, remote commands and data cost before approving fleet rollout.
Connectivity is easy to treat as a small line item because the SIM itself is cheap. Then a machine goes into an airport basement, crosses a border on the wrong roaming profile, or downloads a large update over an expensive plan. The cost was never the plastic card. It was every business process depending on a link nobody fully owned.

Start With the Machine Journeys That Need a Connection
List payment authorization, status, inventory, prices, content, temperature, alerts, remote support, software updates, loyalty, receipts and service tickets. Mark which are real time, which tolerate delay and which remain local.
This defines the connection requirement better than choosing a monthly data package first. A payment-only machine and a video-heavy advertising terminal do not have the same traffic or outage risk.

Map Countries, Venues, and Physical Conditions
Record launch countries, likely expansion, operator coverage, venue construction, basement or elevator location, antenna constraints, temperature, metal enclosure and available WiFi or Ethernet. Coverage maps are useful and incomplete.
Test signal and transaction behavior at the intended placement, not just outside the building. A machine moved five meters behind a concrete wall can become a different network project.

Select Modem Bands and Network Generations Carefully
Confirm supported bands, carrier certification, LTE categories, fallback, antenna connectors and expected network sunset dates by market. Cheap region-specific hardware can become expensive when the rollout changes country.
Avoid assuming older generations will remain available for the machine’s commercial life. Document upgrade or modem-replacement options before a network shutdown becomes urgent.

Decide Who Owns the SIM Relationship
The operator, OEM, distributor, venue or connectivity provider may own accounts. Ownership affects activation, billing, usage visibility, support, number portability, suspension, country changes and what happens when the commercial relationship ends.
The buyer should retain enough control to identify every SIM and export its status. A supplier invoice with one fleet total is not operational visibility.

Choose Physical SIM, eSIM, or Multi-Profile Design
Physical SIMs are familiar and replaceable but require custody and site access. eSIM can simplify remote profile changes when hardware, providers and countries support it. Multi-profile designs may improve resilience but add management and certification work.
Base the choice on rollout and service reality. A clever remote profile is less useful if the modem, local carrier or platform cannot execute the switch reliably.

Set APN and Network Security Deliberately
Decide whether public internet, private APN, VPN or another controlled path is needed. Record DNS, firewall, allowed destinations, inbound access, remote support and provider responsibilities.
A private APN does not replace application authentication and encryption. It changes the network boundary; machines still need trusted device identity, secure updates and limited services.
Understand Roaming Before Crossing a Border
Confirm permanent-roaming rules, local restrictions, supported networks, steering behavior, latency, payment-terminal requirements and commercial rates. A global SIM claim needs country-level validation.
Use local or regional profiles where reliability, regulation or cost demands it. Keep a record of which profile and network each machine actually uses, not only what the contract allows.
Estimate Data From Real Workloads
Measure routine telemetry, payment, logs, images, content, remote sessions and retries. Add software releases, reconnect backlog and diagnostic uploads. These peaks often dominate monthly averages.
Set budgets and alerts by machine type. A frozen-food unit sending small temperature packets should not quietly consume gigabytes because a log loop or failed content download repeats.
Test Normal, Weak, and Missing Connectivity
Run payment, dispense, inventory, alerts, remote command, content and update on strong and weak signal. Interrupt the connection mid-transaction, restart the router and reconnect after an extended outage.
Observe queues, duplicate prevention, time stamps and customer messages. The important result is not that data eventually returned; it is whether payment and machine state remained correct meanwhile.
Define Offline Behavior by Function
Specify cached prices, product selection, payment, dispense, receipts, loyalty, age control, temperature protection, logs and remote locks. Some functions may continue safely while others stop.
Tell customers what is unavailable without exposing technical details. Repeated tapping during a payment outage creates more confusion and possible pending authorizations.
Monitor More Than Online or Offline
Track signal quality, operator, network generation, reconnects, latency, packet use, data volume, SIM state, modem resets, last valid business event and machines switching network unusually.
A device can be technically online while payment or telemetry is stale. Combine connectivity signals with business-flow monitoring.
Control Activation and Inventory
Link ICCID, IMSI or eSIM identifier, modem IMEI, machine ID, serial, location, account, plan, activation date and status. Keep spare and test SIMs controlled.
Activate close to installation to avoid paying for inventory in a warehouse. Deactivate removed or lost devices promptly, but preserve the records needed for final billing and investigation.
Prepare Field Replacement
Give technicians approved modem and SIM handling, antenna checks, APN setup, activation, test and evidence steps. Protect PIN, profile and account credentials.
After replacement, verify machine identity, payment, cloud status, inventory, alerts and remote command. A green modem light is not commissioning.
Manage Cost Without Damaging Reliability
Review fixed fees, usage, overage, roaming, platform, static address, private APN, support, activation and suspension. Compare cost per active machine and business transaction.
A cheaper plan can cost more when it causes outages or prevents diagnostics. Optimize unused SIMs and abnormal traffic before cutting the data allowance needed for recovery.
Plan for Provider Outage and Change
Keep escalation contacts, affected markets, alternative profiles or local providers, manual instructions and recovery tests. Decide whether connectivity diversity is justified for critical locations.
For migration, pilot new profiles, preserve old access, reconcile data and billing, then remove old credentials. Avoid switching an entire fleet on contract expiry day.
Close Connectivity Cleanly at Asset Exit
When a machine is sold, stored, relocated or scrapped, suspend or transfer the SIM, remove profiles, reset routers, revoke credentials and update location records. Check recurring charges.
A decommissioned machine with an active connection is both a cost leak and an access path. Confirm closure rather than assuming loss of power ended the account.
Put Connectivity Into the RFQ
Specify countries, bands, modem, antenna, SIM format, account ownership, APN, security, monitoring, offline behavior, update traffic, support and migration rights.
Acceptance should test the intended networks, weak signal, outage, reconnect, data reporting and field replacement. Connectivity should be a designed subsystem, not an accessory added before shipping.
Buyer Control Table
| Gate | Evidence | Decision |
|---|---|---|
| Design | Markets, hardware, services and ownership | Configuration approved |
| Pilot | Real network and failure tests | Rollout approved |
| Operation | Status, cost, expiry and incidents | Continue or correct |
| Exit | Revocation, transfer and disposal | Record closed |
Related Buyer Resources
- Device identity provisioning checklist
- Business continuity plan
- Installation site requirements
- API monitoring checklist
- Custom vending machine RFQ template
- Custom vending machine prototype cost guide
- Custom vending machine dispensing methods guide
- Custom vending machine factory acceptance test checklist
- Custom vending machine engineering change control guide
- Custom vending machine pilot data and scale guide
- Vending machine payment API integration guide
- Vending machine dashboard specifications buyer guide
- Vending machine shipping import planning guide
- Vending machine testing checklist before mass production
Use WiFi or Ethernet as a Designed Alternative
Some venues offer reliable Ethernet or managed WiFi, while others provide a guest network that changes passwords or requires a browser login. Document authentication, firewall, proxy, bandwidth, venue ownership and who receives outage notices. Do not assume a visible signal means an unattended machine can stay connected.
If the machine can switch between cellular, WiFi and Ethernet, define priority, health checks, switching delay and transaction behavior during the change. Test failover in both directions. An interface that never returns to the preferred network can quietly create roaming cost for months.
Review Connectivity at Every Location Change
Relocation can change carrier, APN rules, venue WiFi, antenna position, roaming status and support ownership. Repeat signal, payment, telemetry, alert and update tests after the move. Update the SIM-to-machine-to-location record immediately; otherwise the next outage begins with the team calling the wrong venue.
Venue Environment and Outdoor Design Resources
- Indoor vending machine noise, heat and ventilation checklist
- Outdoor vending machine weatherproof design checklist
Physical Security and Service Safety Resources
- Vending machine anti-tip and physical security checklist
- Vending machine technician hazardous-energy safety checklist
FAQ
How much mobile data does a vending machine use?
It depends on telemetry, payment, images, content, logs, remote support and software updates; measure real workloads and peaks by machine type.
Is a global roaming SIM enough for every country?
No. Coverage, permanent-roaming rules, local networks, certification, latency and cost must be validated by country.
Should vending machines work offline?
Only approved functions should continue, based on payment, safety, product and compliance risk.
Who should own the SIM account?
The model varies, but the operator needs machine-level visibility, support and a workable transfer or exit route.
How can OBO help?
OBO can support modem selection, machine integration, offline behavior, diagnostics, APN requirements, testing and rollout documentation.