SGP.32 Adoption: What It Will Take to Scale IoT eSIM

The mobile industry has stopped asking whether IoT eSIM will arrive and is now working out how to run it in the field, as the GSMA's summary of the eSIM Summit at MWC Barcelona 2026 made clear. Mid-year eSIM connection snapshot data released in October 2026 by the Trusted Connectivity Alliance (TCA) revealed a fivefold increase globally in the number of eSIM Subscription Manager platforms that enable profile downloads in accordance with the new eSIM for IoT specification – SGP.32.

Under SGP.32, the GSMA's eSIM standard for IoT, a device maker can ship one global product instead of an eSIM-based variant for every network and every market, and an enterprise can move a deployed fleet to a new network without physically swapping a device. Enterprises can deploy with standard format SIMs as well as soldered and integrated form factors all without standing up bespoke infrastructure at every product cycle. Furthermore, enterprises can retain control remotely of managing these past the first agreement cycle. Getting from that promise to a product line is where SGP.32 adoption gets hard, because remote management has to be interoperable with the eSIM hardware and the network profiles a business wants to use.

With more products available and some achieving established industry certifications, interoperability has become a central question for adoption: eSIMs, devices, platforms and networks from different vendors all have to work together before anyone commits to designing them in.

The good news is that the ecosystem is now far enough along that businesses can test real remote profile activation and management workflows today.

SGP.32 Adoption Has Moved From Theory to Practice

For most of the past few years, SGP.32 lived in standards documents and roadmap slides. But now certified eSIMs exist, certified eSIM IoT Remote Managers (eIMs) are in service, module makers support the standard, and connectivity providers are embracing digital profiles that can be activated on real devices.

In May 2026, the cellular IoT developer community IoT Stars ran an SGP.32 reality check. The test connected eSIMs on five different host devices to Kigen's eIM. It then downloaded, activated and switched profiles from various connectivity providers in a live multi-vendor environment.

The test showed profile download, activation and switching working across that mix of hardware and providers. It did so with the same commercial eSIMs, tools and profiles any business can order today, rather than a lab build.

The standard has arrived with the ease it promised: multiple networks, easy to activate and work with. Scaling it depends on the pieces around it working together, and on business success parameters such as upstream integrations, freedom to choose and visibility into total cost of ownership.

Connectivity Choice Without Designing Around One Operator

Few IoT businesses operate in a single, simple network environment. More often, a manufacturer already working with one connectivity provider needs a second to enter a new sector, or an enterprise needs more than one network for operational resilience. A device maker expanding into regulated markets faces different local rules on coverage, commercial terms and profile availability, and a global product team has to support customers in several regions without redesigning hardware or multiplying SIM supply chains.

SGP.32 lets the connectivity decision move later in a product's life. Neil Wilson of Pangea Connected put it plainly: with SGP.32 and Kigen's eIM, "an OEM can ship now and decide on the network later."

That flexibility only holds if switching is easy in practice. Without a unified route, teams end up building separate relationships with each provider, aligning activation processes, validating profile downloads and testing device behavior for every one. Choice that costs a fresh integration project each time is choice most product teams will avoid.

Interoperability Is What Makes SGP.32 Scale

Each handoff between vendors is a point where activation can break. An SGP.32 deployment stacks the eSIM, the module, the eIM, the providers' profile servers and the enterprise's own systems, often from different suppliers. An eIM proven with one vendor's eSIM may never have been tested with the next, and a fleet that finds that gap finds it in the field.

Two certified products can follow the same standard and still make different implementation choices that affect real deployments. Placing the profile assistant in the eSIM itself (IPAe) rather than in device firmware can widen hardware choices and simplify integration. Devices behind gateways or within restricted networks require indirect profile downloads, and constrained, low-power devices may require lighter transport protocols than broadband devices. And an eIM should be proven with other vendors' eSIMs, and eSIMs with other vendors' eIMs.

Cross-vendor testing is already happening. Kigen's eIM has been tested with eSIMs from other vendors and supports more than 60 IoT modules and platforms, and its eSIMs have been tested with five other eIMs.

For Operators, a Familiar Consumer eSIM Playbook

SGP.32 brings IoT eSIM closer than ever to the model that made consumer eSIM work. It uses the same SM-DP+ profile infrastructure as consumer eSIM, so providers already serving consumer eSIM start from familiar ground.

Instead of a person scanning a QR code on a phone, an eIM triggers profile operations across a fleet of headless devices. A provider that already delivers consumer eSIM profiles has most of the building blocks; the work is in validating activation on IoT eSIMs and making commercial onboarding simple.

Buyers are pushing providers to do that work. Among the connectivity partners supporting the Kigen IoT eSIM Starter Kit, KORE highlights the need for connectivity that is "simpler to deploy, more flexible to manage, and resilient over the lifetime of every device," while Soracom CTO Kenta Yasukawa notes that SGP.32 is "rapidly becoming a requirement in automotive and enterprise IoT RFPs." At launch, the Starter Kit included 13+ connectivity partners offering activation-ready profiles, with more operators and MVNOs completing their workflows.

eSIM Activation Is Only the First Step

A successful first profile download proves the pieces connect, but before committing devices to the field, teams need to test what happens after that first download:

• Profile changes. Switching a device to a new provider when a contract ends, a region changes or a better commercial deal appears.
• Recovery. What happens when a switch fails, and whether the device can fall back to a working profile without a site visit.
• Resilience. Whether a second network keeps devices online when the primary one has an outage.
• Fleet visibility. Which profile is downloaded and enabled on each device, when each operation happened and whether it completed. At fleet scale, that audit trail becomes part of security and compliance governance.
• System alignment. Whether billing, policy and connectivity systems agree on each device's active profile. When they don't, the mismatches show up as cost, support tickets and compliance risk.

These are operational questions, and paper evaluations rarely answer them. Testing profile activation and lifecycle management on real devices, with real profiles, before a large rollout is how teams find the gaps while they are still cheap to fix.

From Proof of Concept to Scalable Deployment

Many IoT projects stall between a working pilot and a production rollout. For SGP.32, manufacturers and enterprises typically need five things in place to get across that gap:

1. Certified eSIMs in the form factor the product needs, from plastic SIMs for development to solderable chips for production.
2. An eIM they can drive two ways: through a console for operations staff and through APIs that plug profile management into their own platforms, portals and billing.
3. Device-side tools, such as SDKs and reference implementations, so firmware teams are not decoding the standard on their own.
4. Activation-ready profiles from several providers, already validated on the eSIMs, so connectivity choice is real from day one.
5. A production path, including provisioning profiles at the factory, so what worked in the pilot carries into manufacturing.

Historically, each business had to assemble those pieces itself. More than 100 eIM trials over the past 18 months have surfaced the field realities that slow adoption: constrained devices, different module environments, network variation, platform-specific integration work and operational exceptions.

Digi International and Itron are already using Kigen's SGP.32 integrations in volume, and Evergy, NuvoLinQ and Robustel are among the companies that have announced they are scaling SGP.32 IoT eSIMs.

How to Start Evaluating SGP.32 Today

Businesses no longer have to build the full ecosystem before they can test it. The Kigen IoT eSIM Starter Kit is one practical example. It brings together 10 certified eSIMs, access to an eIM and the Pulse management console, device-side tools including a C-SDK and IPAd, and activation-ready profiles from 13 or more connectivity partners, with three months of evaluation access.

"Customers can now focus on outcomes without having to assemble the entire ecosystem themselves."

Jean-Louis Carrara, SVP Sales, Kigen

Three months is enough time to answer the questions that decide whether the choices in the stack work or how best can they scale. Teams can choose an eSIM activation partner, test remote profile management inside their own device environment, and run profile switches and recovery on real hardware. Along the way, they can build a working understanding of total cost of ownership and the factors that will determine scaling success, before a full rollout.

Widespread SGP.32 adoption will come from making implementation simple, interoperable and commercially practical, and the ecosystem has reached the point where that can be tested today.

To see how SGP.32 will work in your own products, request a Kigen IoT eSIM Starter Kit.