Blog

Home > eSIM, iSIM and SGP.32: The 2026 Guide to Global IoT Connectivity

eSIM, iSIM and SGP.32: The 2026 Guide to Global IoT Connectivity

Every SIM card in your warehouse is a bet. You are betting on which country the device will ship to, which operator covers that country, and what roaming rules will look like two years after launch. Lose that bet and you are not swapping a card. You are recalling hardware.

The market is done with that gamble. Juniper Research counted 1.2 billion devices using eSIMs in 2025 and projects 1.5 billion in 2026, a 30 percent jump in a single year, with 4.9 billion cellular connections on eSIM expected by 2030. The growth is not coming from phones. It is coming from connected logistics, oil and gas, smart street lighting, utility meters and asset trackers, the products that ship in bulk and stay in the field for a decade.

This article covers the three things you need before you buy: the difference between eSIM and iSIM, why SGP.32 changes procurement, and what to check on the module itself. The decisions are not quick ones. Modules get designed in for five to ten years, and the provisioning standard you pick now decides whether a contract change later means a software update or a recall.

What eSIM, iSIM and a plastic SIM each buy you

A plastic SIM is cheap and familiar. It is also a supply chain problem. One SKU per operator, per region, sometimes per contract, and someone has to touch every device to swap cards.

An eSIM, more precisely an eUICC, is a chip soldered to the board in MFF2 form, or a removable card, that holds several operator profiles and downloads new ones over the air. One module SKU can ship worldwide and register on the local network when it arrives. That has been true on paper for years. The friction was in the provisioning standards, and that is where SGP.32 comes in.

An iSIM goes further and moves the SIM function inside the modem’s system-on-chip. No separate chip, no dedicated secure element, less space and less power for battery devices. Qualcomm started shipping iSIM-capable modems with the Snapdragon 8 Gen 2 in 2023. For IoT, Qualcomm’s E41 4G Modem-RF with IDEMIA’s iSIM adds an EAL5+ pre-certified enclave and the first GSMA SAS-UP compliant chip provisioning environment, announced in early 2025. Counterpoint expects iSIM-capable device shipments to grow at a 160 percent CAGR from 2024 to 2030.

For a module buyer in 2026 the honest read is simple: eSIM is the practical purchase, iSIM is the design criterion for the next product cycle. iSIM modules are real, but production firmware, certification and operator support are still maturing. For a high-volume product, though, removing the eUICC chip and its supply chain from the BOM is exactly the kind of saving that shows up in margin.

Why SGP.32 is the change that matters

eSIM hardware existed for years before the ecosystem worked. The bottleneck was always remote SIM provisioning, the standard that defines how a profile reaches the chip and who gets to manage it.

The old M2M standard, SGP.02, was built for automotive and gave operators control through heavy SM-SR infrastructure. Enterprises could manage profiles in theory, inside a walled garden. The consumer standard, SGP.22, moved control toward the device owner but assumed a screen and a QR code, which an unlit sensor in a cabinet does not have.

SGP.32, published by the GSMA in May 2023 with v1.2 as the current stable version, was designed for exactly those headless devices. It adds an eSIM IoT Remote Manager (eIM) on the server side and an IoT Profile Assistant (IPA) on the device, and it reuses the SM-DP+ infrastructure operators already run. Profile management runs over CoAP over UDP instead of HTTPS, which matters when the device lives on NB-IoT with a kilobyte data budget; our LPWAN guide covers when NB-IoT beats LTE-M, but the short version is that SGP.32 was built around those constraints. Operations are asynchronous, so a meter that wakes twice a day gets its instructions when it wakes. Provisioning is server initiated: the eIM pushes to a whole fleet instead of waiting for each device to pull.

The result is what procurement teams care about: the buyer controls the profiles, not the carrier. You can add, disable or switch operators over the air, from a console or an API, with no truck roll. The GSMA estimates 195 million SGP.32 profile downloads by 2029, about 70 percent of all IoT eSIM activity.

The 2026 receipts

SGP.32 moved from spec to shipping this year, and the timeline is worth keeping because it shows who is serious.

IDEMIA delivered the first fully GSMA-certified end-to-end SGP.32 solution in August 2025. At MWC in March 2026, IDEMIA, Tele2 IoT and Cisco unveiled a commercial end-to-end deployment. Telenor IoT started commercial delivery of SGP.32 SIM cards in April 2026. In July, Soracom moved its SGP.32 eSIMs from pre-order to general availability, with an orchestration layer that manages multiple operator profiles from a single API.

On the hardware side, SIMCom completed SGP.32 IPA.d integration with G+D on its A7672X Cat 1 module in March 2026 and is expanding support across the SIM7672X family; if Cat 1 bis is your lane, our Cat-1 bis vs RedCap comparison walks through the alternatives. In April, the IoT Stars community ran the first independent, public, multi-vendor SGP.32 test, moving live devices between connectivity providers using Kigen’s GSMA SAS-certified eIM. That test used commercial tools and support paths, not a one-off lab setup.

Juniper expects connected logistics, oil and gas, and smart street lighting to add a combined 75 million new eSIM connections in 2026. Those are the verticals with the most to gain from switching profiles without touching hardware. Behind these launches is a simple forecast: IoT Analytics puts cellular IoT connections at 9.1 billion by 2030, and most of those devices will never have a human nearby to swap a card.

What to check before you design one in

Not every module labeled “eSIM” is SGP.32 ready, and the difference shows up in firmware, not marketing. Put these questions to your supplier:

  • Where does the eUICC live? Inside the module as an MFF2 chip, or as an external chip you add to the board?
  • Who runs the local profile assistant? Some modules run it on-module: Quectel’s EG912U and EG915U expose it through AT commands, and SIMCom’s A7672X has G+D’s IPA.d integrated. Others expect the host processor to handle profile management.
  • Which standard does the firmware actually implement: SGP.32, SGP.22 or SGP.02? Ask for the GSMA certification document, not the datasheet claim.
  • What is the bootstrap profile? The device has to connect to something on day one. Know which eIM and SM-DP+ it talks to, and who holds the keys.
  • Does the module support in-factory profile provisioning (SGP.41/42)? It lets you ship connectivity-ready devices without preloading a single operator contract, which is how the SKU problem dies at the source.
  • Is the connectivity partner certified? The eIM platform needs GSMA SAS certification, and the profile provider matters as much as the module.
  • Is iSIM shipping in production firmware, or is it a roadmap item? Treat roadmap iSIM as a reason to design for upgradeability, not as a reason to change this year’s BOM.

Two real examples of why the label is not the whole story: Quectel’s EG25-G has no eUICC on board at all, so you supply the eSIM chip. The BG95-M9 supports SGP.32 only with a custom firmware version. Both are capable modules; neither is plug-and-play for SGP.32. u-blox’s SARA-R10001DE, by contrast, ships with an embedded eSIM and multi-IMSI profiles from Wireless Logic, a sign that connectivity bundling is becoming a module feature.

The short version

eSIM is the 2026 default for global IoT. SGP.32 is the standard that makes it practical, and iSIM is the cost saving that arrives next. Buyers who move now get one SKU instead of twelve, remote profile control instead of carrier lock-in, and hardware that does not need to be touched when contracts change. The window is open because the ecosystem just closed the loop: certified eUICCs, certified eIMs, commercial operator delivery, and modules with SGP.32 firmware.

Send us your BOM, or just the module line you are evaluating. We track the SIMCOM, Quectel and u-blox parts with eSIM and eUICC options, and we will tell you what ships with SGP.32 firmware today versus what is still a firmware promise.

Send us your BOM

Sources

Tags: , , , , ,