For an IoT team, changing a SIM card is rarely as simple as changing a SIM card.

The device may be installed inside a payment terminal, utility meter, industrial controller or vehicle operating hundreds of kilometres from the nearest engineer. Multiply that problem across countries and thousands of endpoints, and physical SIM logistics quickly become an expensive operational habit.

iONLINE is tackling that problem with eSIM for IoT, a new capability added to its FlexiSIM connectivity solution. The service uses standards-based remote profile management aligned with the GSMA’s SGP.32 architecture, allowing enterprises to provision connectivity, change operator profiles and manage distributed fleets without physically accessing every device.

Switching beyond the standard

SGP.32 was created for connected devices that may have limited power, bandwidth or user interfaces. Unlike the consumer eSIM experience, it does not assume somebody is standing beside a screen waiting to scan a QR code. The GSMA published version 1.3 of the technical specification in May 2026, confirming that the standard is moving from industry promise towards a more mature commercial ecosystem.

iONLINE’s main differentiator sits above that basic provisioning layer. FlexiSIM can be programmed with a mapping table that tells the SIM which installed profile it should prefer in a particular country or on a particular network. Crucially, iONLINE says the selection can still happen when the currently active profile has lost connectivity.

READ MORE: Enterprise Connectivity Needs More Than eSIM

That matters because remotely downloading profiles is only part of the problem. A device must also know what to do when its preferred network becomes unavailable, commercially unattractive or unsuitable for local data routing.

“With our eSIM for IoT FlexiSIM, customers can provision and manage connectivity remotely at fleet scale, so deployments move faster and devices stay online where the business actually needs them,” says Edwin Watson, iONLINE Chief of Staff. “Teams can programme SIM fleets to switch intelligently based on pre-defined logic. This helps devices use the best available connection for their use case.”

Depending on the deployment, that logic could prioritise signal quality, cost, local breakout or a preferred operator relationship. The company says profiles can be loaded directly from operator platforms, while activation, policy changes and fleet monitoring can be handled through CentralFlex, its connectivity management platform.

Resilience without a truck roll

The promise is straightforward: install an appropriate FlexiSIM once, then make future connectivity decisions remotely.

iONLINE points to a major US network outage as an example. Devices dependent on one operator lost service, while customers using an iONLINE profile were able to move automatically to another available network. The company combines profile switching with prioritised network-access lists configured by country.

“Success in IoT is keeping thousands of devices connected for years with minimal touch,” Watson says. “By enabling customers to switch profiles intelligently, eSIM for IoT protects uptime when networks fail. This makes connection resilience a controllable part of the deployment, rather than a risk which grows as fleets scale.”

For utilities, logistics operators, security systems and industrial deployments, avoiding even a small number of site visits can materially change the economics of a rollout. It also makes connectivity easier to govern: administrators can provision profiles centrally, apply policies and retain a clearer record of changes.

Not every fleet needs it

This will be less compelling for a small, stationary deployment operating reliably on one domestic network. It is also not an instant upgrade for every existing IoT estate. SGP.32 generally requires compatible eUICC hardware, device software and supporting profiles, so older deployments may need to wait for a hardware refresh rather than expecting a simple over-the-air migration. Eseye similarly warns that SGP.32 is not backward-compatible with earlier remote-provisioning models.

iONLINE could also make evaluation easier by publishing more detail on supported hardware, available operator profiles, switching rules, service-level commitments and how its implementation maps to the latest SGP.32 version. Standards alignment is important, but enterprise buyers still need proof that the complete chain—from module and firmware to profile availability and fallback behaviour—has been tested for their use case.

The real contest is orchestration

iONLINE is entering an increasingly active field. floLIVE and Kigen launched operational SGP.32 support in February 2026, combining remote provisioning with multi-IMSI connectivity and factory provisioning. KORE and Kigen announced their own portfolio in April, while Eseye is positioning SGP.32 inside a broader platform supporting several generations of remote SIM provisioning.

That competition reveals the bigger trend. SGP.32 is becoming the common foundation, not the finished product. The providers most likely to stand out will be those that make profile choice, fallback, local compliance, billing and fleet control feel like one coherent system.

FlexiSIM’s mapping-based, on-device switching gives iONLINE a credible angle in that race. Its real test will not be whether profiles can be downloaded remotely, but whether customers can trust thousands of unattended devices to make the right connectivity decision when conditions change.