SGP.32 is ready. Here is what IoT buyers should ask before they switch

  • October 21, 2026
  • imc
  • Com4

For more than a decade, the SIM card has been the one part of an IoT device you could not change once it left the factory. SGP.32 is the GSMA’s answer to that, and in 2026 it has moved from pilots into commercial products. But the standard alone doesn’t give buyers freedom. How it is implemented does.

By Amina Kristensen, CMO, Com4 (part of Wireless Logic)

Why the old model held IoT back

Anyone who has rolled out a fleet of connected meters, chargers or cameras knows the problem. You pick a connectivity provider, you put their SIM in the device, and from then on the device is tied to that contract for its whole life. Ten or fifteen years, in many cases.

eSIM was supposed to fix that. The earlier machine-to-machine standard, SGP.02, did allow profiles to be swapped over the air, but every swap depended on bilateral integrations between operators and platform vendors. In practice it was expensive and slow, so eSIM in IoT stayed mostly in automotive and utilities, where the volumes justified the effort. For everyone else, the plastic SIM and the long contract remained the default.

The SGP.02 model: every profile swap runs through operator-specific SM-DP and SM-DR integrations

What SGP.32 actually changes

SGP.32 was written specifically for IoT devices. These are devices with no screen, often no user nearby, limited power and sometimes very little bandwidth. The standard introduces two new building blocks:

  • The eIM (eSIM IoT Remote Manager), a server-side component that tells devices which profile to download, enable or delete. It can do this for one device or for a whole fleet at once.
  • The IPA (IoT Profile Assistant), which sits in the device or the module and carries out those instructions without anyone touching the device.

Because SGP.32 reuses the same profile servers that consumer eSIM already runs on, operators don’t need to build a separate infrastructure for IoT. That is a big reason why adoption is now moving faster than it did with SGP.02.

The SGP.32 model: the eIM manages profiles remotely, and the IPA in the device carries out the changes

For a buyer, three practical changes follow:

  1. One product, any market. You can build and ship a single hardware version with a bootstrap profile, then download the right local profile once the device arrives in its country. Fewer SKUs, simpler logistics.
  2. Easier compliance. Some countries restrict permanent roaming or require data to stay local. With SGP.32 you can add a local profile in the field instead of recalling hardware.
  3. A real exit option. If a network performs poorly or commercial terms change, you can move devices to another profile remotely. That changes your negotiating position for the life of the deployment.
With SGP.32, connectivity changes happen over the air, even at the most remote sites

Where the market stands in 2026

The analysts broadly agree that this is the year SGP.32 goes from talk to volume. ABI Research expects SGP.32 profile downloads to overtake SGP.02 in 2027. Kaleido Intelligence sees commercial ramp-up through 2026 and a tipping point in 2027 or 2028. Juniper Research expects the total number of eSIM devices to pass 1.5 billion this year, with connected logistics, oil and gas and smart street lighting among the biggest drivers on the IoT side.

Two things are worth keeping in mind, though. SGP.02 is not going away soon, and many devices in the field today will keep running on it for years. And SGP.32 only works end to end if the module, the SIM, the eIM and the operator profiles all support it. Plenty of devices shipping today still don’t.

The part buyers tend to overlook: who controls the eIM

This is where we see the most confusion in conversations with customers.

SGP.32 gives you the ability to switch profiles. Whether you can actually use it depends on who runs the eIM that manages your devices, and on what your contract says about it. If the eIM belongs to your connectivity provider and only accepts that provider’s profiles, the lock-in hasn’t disappeared. It has just moved from the SIM card to the management platform.

So before you sign, look past the headline “SGP.32-ready” and ask how open the setup really is.

Six questions to ask any provider

  1. Is the SIM and eUICC certified for SGP.32, and are you shipping it today? Not on the roadmap. Available to order.
  2. Which modules have you tested it with? The IPA often lives in the module, so check that your chosen hardware has firmware support.
  3. Who operates the eIM, and can I bring my own or use a third party’s? This decides how portable your fleet really is.
  4. Can I load profiles from other operators, including local ones, on the same eUICC? And what does it cost to do so?
  5. How do you handle my existing SGP.02 and plastic SIM estate? Most fleets will run mixed for years, so you need one place to manage all of it, including your multi-IMSI SIMs.
  6. What happens to my devices if we part ways? A good answer is specific about profile handover, notice periods and data. A vague answer tells you something too.

Don’t wait for the perfect moment

The most common mistake we see is waiting. Teams hold off on new designs until SGP.32 feels fully mature, and then ship another generation of hardware that is locked in for the next decade. If you are designing a device that will launch in the next 12 to 18 months, SGP.32 support belongs in the requirements now, even if you start out using a single profile.

At the same time, there is no need to rip out what works. A sensible plan for most companies looks like this: keep the current estate running, specify SGP.32 for all new hardware, test with a small batch in your most demanding market, and make sure the connectivity management platform you manage everything from can see old and new SIMs side by side.

A standard is only as open as its implementation

SGP.32 is the most meaningful change to IoT connectivity in years. It gives device makers and operators of large fleets something they have never really had: the ability to change their mind after the device has shipped. But the standard is a toolbox, not a guarantee. The value lands with buyers who ask the right questions and choose partners willing to give honest answers.

At Com4, our SGP.32 SIMs are now available to order, and we’re happy to talk through any of the questions above, whether or not you end up buying from us.

About Com4

Com4, part of Wireless Logic, is a Nordic provider of global IoT connectivity, founded in Oslo in 2011. Com4 runs its own core network and connectivity management platform and gives more than 1,000 customers access to 750+ networks worldwide, with over 20 million connections managed across the Wireless Logic group. Learn more at www.com4.no/en.