For years, choosing a mobile network for an IoT product was close to a lifetime decision. Once a device left the factory with a SIM from one provider, changing provider usually meant a costly field visit, a complex commercial negotiation, or both. For products designed to run for a decade or more, that's a long time to be locked in.
SGP.32, the GSMA's eSIM specification for IoT, changes that. It lets connected devices download, switch and manage connectivity profiles remotely, at scale, without anyone touching the device. The GSMA published the latest version, SGP.32 v1.3, in 2026, alongside its architecture specification (SGP.31) and test specifications (SGP.33). Here's why it matters, and what to think about before you adopt it.
Why the earlier approaches fell short
Remote SIM provisioning isn't new. The original machine-to-machine standard, SGP.02, made it possible, but it relied on a server-driven model, often depended on SMS, and usually required integration agreements between parties before devices could switch. In practice, that left many deployments tied to one provider. The consumer standard, SGP.22, made switching easy for smartphones, but it assumes a person with a screen who can scan a QR code. Most IoT devices have neither.
SGP.32 was designed to fill that gap. It reuses proven building blocks from the consumer world, such as the SM-DP+ profile server, and adds two IoT-specific pieces:
- The eIM (eSIM IoT remote manager): a server that tells devices which profiles to download, enable, disable or delete, so decisions can be made centrally for one device or a whole fleet.
- The IPA (IoT profile assistant): a small component on the device or on the eSIM itself that carries out those instructions, replacing the user-facing app consumer phones rely on.
Where the value comes from
1. Freedom to choose, and change, connectivity
With SGP.32, a device can move to a new connectivity profile over the air. That gives you real negotiating leverage with providers, the option to use different networks in different markets, and a way out if coverage, service or pricing stops meeting your needs. Connectivity becomes a decision you can revisit, not one you're stuck with.
2. One product, built once, for every market
Because the right profile can be downloaded after manufacture, device makers can build a single hardware variant and decide on connectivity when and where the device is deployed. That means fewer product variants, simpler supply chains and less stock tied up in region-specific SIMs.
3. Protection for long-lived devices
Smart meters, industrial sensors, vehicles and medical devices often stay in service far longer than any connectivity contract or network technology. When a network is retired, a contract ends or a business is sold, remote provisioning lets you update the connectivity of devices already in the field instead of replacing them.
4. Designed for constrained devices
SGP.32 removes the dependency on SMS and supports lightweight transport such as CoAP over UDP with DTLS security. That makes it a much better fit for low-power devices on networks like NB-IoT and LTE-M, where SMS may not be available and every byte of data and milliwatt of battery counts.
5. Managing fleets, not individual SIMs
The eIM is built for scale. Instead of handling SIMs one at a time, you can apply profile changes across thousands of devices at once, based on location, customer or contract. That turns connectivity management from a manual chore into a controllable, auditable process.
6. Meeting local requirements
Some countries restrict the permanent roaming many IoT deployments rely on, or require local connectivity. Downloading a local profile once a device reaches its destination is a far simpler way to meet those rules than managing separate hardware or SIM stock for each market.
A sign the ecosystem is maturing
Certified, production-ready components are what turn a standard into something you can build on. In October 2026, Kigen announced that its Automotive eSIM is the industry's first eSIM supporting SGP.32 v1.3 to achieve GSMA eUICC Security Assurance (eSA) certification. Built on Infineon's TEGRION automotive security controller, it's aimed at connected vehicles that need to stay secure for more than a decade, with OEM samples available from October 2026.
Milestones like this matter beyond automotive. Security certification against the latest version of the standard gives device makers and fleet operators more confidence that SGP.32 is ready for long-lived, high-value deployments, and it's a useful benchmark when you assess suppliers for your own products.
What to plan for
SGP.32 is a big step forward, but it isn't a switch you simply flip. A few questions deserve attention early:
- Ecosystem maturity. Support across eSIMs, modules, servers and certification is still developing, though it's moving quickly. Check which components you rely on are SGP.32-ready and tested before you commit to a product launch.
- Who controls the eIM. The eIM decides where your devices connect, so it's strategically important. Make sure you can change eIM provider, or run your own, so lock-in doesn't simply move from the SIM to the management layer.
- Existing fleets. SGP.32 isn't backward compatible with SGP.02, so devices already deployed on the older standard need their own plan. That might mean running both side by side for a while.
- Commercial models. The technology makes switching possible; your contracts need to make it practical. Look closely at profile fees, minimum terms and switching conditions.
- Security and ownership. Decide who is allowed to trigger profile changes and how those actions are authorised and audited, especially for devices in critical or regulated settings.
Getting started
A sensible first step is to look at your current and planned device portfolio and ask where flexible connectivity would make the biggest difference: new products still in design, markets with difficult roaming rules, or long-lived fleets most exposed to network or contract changes. From there, a focused pilot with SGP.32-ready hardware and a carefully chosen eIM approach will show the operational and commercial benefits in practice, before you roll it out more widely.
At Connectree we help IoT businesses shape connectivity strategy, business models and the platforms behind them. If you're weighing up SGP.32 for your next product or fleet, our Product and Business services are a good place to start.
Want to go deeper? Our whitepaper SGP.32 in practice: a planning guide to eSIM for IoT covers the architecture, the key decisions, commercial terms and a phased adoption roadmap.
Talk to Connectree
Working on something in telecom, IoT or AI? We'd be glad to hear about it.
Get in touch