A global IoT connectivity supplier earns its keep in one way: it removes the work of running SIMs at scale. You want one SIM that works in every country your fleet touches, network changes without shipping hardware, and a single view of every connection. Anything less and you are juggling several carriers' contracts, invoices and support desks at once. This post sets out what to look for, and what each item is for.
Why coverage alone is not a feature
Coverage claims are the oldest trick in connectivity marketing, and a single network in each country proves nothing about your devices. A tracker in a delivery van crosses network boundaries hourly. A payment terminal in a shop cannot wait for a field visit. What matters is whether the SIM can register on whatever network is available where the device actually sits.
A multi-network SIM carries profiles or roaming agreements for many operators, so the device is never dependent on one carrier's footprint. If the home network has no signal where the device is, the SIM registers elsewhere. That is the entire point, and it is what separates a global SIM from a domestic one with an international roaming bolt-on.
The eSIM question: what remote provisioning buys you
eSIM, in plain terms, is a SIM whose network profile can be changed over the air instead of by swapping plastic. In IoT that matters for three reasons: you can change carrier without a technician visit, you can fix a shipment of devices tied to the wrong network before they are deployed, and you can move a fleet between tariffs as its usage changes.
The standard work sits with the GSMA, whose eSIM specifications for IoT have matured to handle fleets rather than single handsets. The practical lesson is older than any spec version: check that the SIMs you buy are remotely provisionable, and that your supplier can change profiles at fleet scale, not one device at a time.
Unsteered roaming, and why steering hurts
Some connectivity plans steer the device onto a preferred network even when another carrier has a stronger signal. Steering exists because the supplier earns more on that network, not because the device performs better there. Unsteered roaming means the device stays on the strongest available signal and moves when that signal fades.
For a camera on a remote site or a meter in a basement plant room, the difference between a steered and an unsteered SIM is often the difference between a live device and a support ticket. Ask a prospective supplier directly: does the device pick the best network, or the one you make the most margin on?
Tariffs built around the fleet, not the average device
Global fleets are uneven. One region may have thousands of low-data sensors; another, a handful of cameras streaming constantly. A per-device tariff applied uniformly across that estate wastes money in one place and throttles it in another.
The useful shape is pooled data: a shared allowance across the estate, so the quiet devices subsidise the chatty ones within the same contract. SIMs should also move between tariffs as usage shifts, without a commercial renegotiation every time.
| Tariff shape | Best for | Weakness |
|---|---|---|
| Fixed per SIM | Predictable, similar devices | Wasteful with uneven usage |
| Pooled data | Mixed fleets across regions | Needs clear visibility of consumption |
| Custom per country or network | Heavy traffic in specific markets | More administration |
Lifecycle control: the unglamorous part that saves weekends
Most of the cost of connectivity is not the data. It is the admin: activating SIMs in bulk, suspending a stolen device, working out why a unit went dark, reconciling an invoice against a spreadsheet nobody trusts. A supplier is only doing its job if activation, suspension, monitoring and billing happen in one place.
Coverage and network intelligence matter here too. If you can see which network every SIM is on, its signal strength and its roaming state, you catch a fading connection before the device drops offline. That is the difference between a proactive fix and a call from a customer who cannot pay at the terminal.
Where the platform fits in
Devices, not just SIMs, need managing, and the two should not live in separate systems. On RAAD™, the DigitalSom IoT platform, every asset a customer runs sits in one place, SIMs included, with tracking, alerts and reporting alongside. A connectivity supplier who cannot show you the SIM's state next to the device it is fitted to is selling you half a picture. Cloud-IQ sells, deploys and supports RAAD alongside the connectivity itself, which is worth knowing when you compare suppliers who offer one or the other.
APIs matter for the same reason. If your fleet management or OEM platform cannot pull SIM status automatically, someone will do it by hand, badly.
Security and breakout, briefly
Two items belong on any sensible checklist. Private routing keeps device traffic off the unprotected public internet. Local breakout means data exits to the internet through a point of presence near the device rather than a distant data centre, which cuts latency for cameras and payment terminals. Do not accept a vague promise on either; ask how traffic is routed and where.
Support that can diagnose, not just escalate
When a device goes dark, the failure is one of three things: the SIM, the network, or the device. Most support desks can only escalate. The useful kind of support reads cell-tower data, tells a SIM fault from a network fault, and routes the fix to whoever owns it. Engineers who can diagnose are worth more than engineers who are merely on call around the clock; the best suppliers offer both.
Common questions
Should I start with a pilot or deploy globally at once?
Pilot first, in a market that represents your hardest coverage case. Prove the SIMs, the provisioning process and the support chain, then scale the same configuration outward. A pilot that needs reworking to scale was not a pilot, it was a detour.
Is eSIM worth the premium over standard SIMs for IoT?
If your fleet might cross borders, change networks or outlive a single carrier relationship, yes. Reprofiling remotely removes most of the cost of fixing a connectivity mistake after deployment.
How do I compare coverage claims between suppliers?
Ask two questions: how many mobile networks can a single SIM register on, and in how many countries? Then test it. A claim of "global coverage" backed by one network per country fails the first time that network has an outage where your device sits.
How Cloud-IQ approaches this
Cloud-IQ is the DigitalSom group's global IoT connectivity business. We keep devices online across 190+ countries and 800+ mobile networks, and we sell, deploy and support RAAD, the DigitalSom IoT platform. One multi-network SIM replaces a SIM per country, with unsteered roaming keeping every device on the strongest signal, and tariffs built around the countries and data your fleet actually uses, pooled across the estate. Your SIMs and the devices they are fitted to are managed together on RAAD, and our engineers are on call 24/7 to separate a SIM fault from a network fault. If that is the shape of the fleet you are running, you can Request a quote.
