eSIM for IoT fleets: what SGP.32 changes, and what it doesn't

Every connected device has a SIM, and for most of IoT's history that SIM has been a long commitment. Choose a network, fit its SIM, ship ten thousand units, and you are tied to that network's coverage, prices and technology plans for the life of the product. If the network raises prices, switches off a technology or loses coverage where your devices sit, the fix is a site visit.

eSIMs were meant to end that, and for phones they largely have. For IoT, the earlier standard, SGP.02, worked, but switching networks under it depended on integrations between operators' systems that were slow and expensive to arrange. SGP.32 is the GSMA's standard for ordinary IoT fleets, and in 2026 it moved from slides to stock. Telenor IoT, for example, began taking orders for SGP.32 SIMs in February and delivering them from 17 April 2026 (Telenor IoT).

What actually changes

The device carries an eUICC, a SIM that can hold more than one network profile. Under SGP.32, three pieces work together (KORE). An SM-DP+ creates and delivers network profiles. An eIM, the eSIM IoT remote manager, decides which profile goes to which device. And an IPA, the IoT profile assistant on the device or the SIM, carries out the instructions. In practice, you can download a new network profile to a sealed device in the field and switch to it. There is no site visit, and no need for the current operator to integrate with the new one.

That matters most in four situations. A product sold in several countries that wants a local network in each. A long-lived device that will see at least one network change or sunset in its life. Devices that are expensive to reach, on poles, in plant rooms or in another province. And fleets whose connectivity contract will be renegotiated, because a credible ability to switch is a strong negotiating position.

What it does not change

It does not create coverage. A new profile is only as good as the new network's signal where the device sits, and the modem still has to support that network's bands.

It does not upgrade old devices. SGP.32 is not backward compatible with SGP.02, and existing fleets cannot move to it with a software update; they need new eUICC hardware (KORE). For devices already in the field, SGP.32 is a decision for the next hardware revision.

It does not make switching instant or free. Each operator has its own commercial terms, profile downloads cost money, and every new network needs testing with your device before you trust it. A promise of a new operator at the push of a button describes the mechanism and leaves out the work around it.

It does not solve the bootstrap problem. A device needs a working connection to download a new profile. If the only profile on it has lost coverage, there is nothing to download over, so choose the first profile, and the fallback, with care.

It adds a dependency. The eIM is now part of your product's lifeline. Ask who runs it, what it costs per device, and whether you can move to another eIM if that relationship ends.

And the ecosystem is young. Many products described as SGP.32-capable are still partly implemented, and fleets will run mixed standards for years (KORE).

When it is worth it

SGP.32 earns its cost on fleets that are large, long-lived, multi-country or hard to reach. It matters much less for a few hundred devices in one country with a short life, where a good single-network contract and an ordinary SIM are simpler and cheaper.

If you are designing a device that will live in the field for five years or more, settle these questions now:

• Is the eUICC certified for SGP.32, and do the modem and firmware support the IPA it needs?
• Which eIM will we use, and can we change it later?
• Which networks will the first and fallback profiles use, and have we tested them at our sites?
• What does a profile download cost, and what do the operators we might switch to charge?
• Who will own profile management after launch?

Treat connectivity as a part that will change

Connectivity belongs in the design the same way firmware does: as something that will be updated during the product's life. Pick a modem with the bands for every market you might enter. Keep the eSIM and its management in the design from the first prototype. And make sure the firmware reports which profile is active and how well it is performing. A fleet that can tell you its signal and network per device can make a switching decision on evidence. One that cannot is guessing.

If you are planning a fleet that has to outlive its first network contract, send us a brief, or write to hello@handee.co.za.