Loading...

eSIM and iSIM Change How Connected Devices Reach Global Networks

Logistics & Transportation

Published by IOT San Jose Research & Editorial Team

eSIM and iSIM Change How Connected Devices Reach Global Networks

A SIM card is a small piece of plastic that has caused large problems for IoT makers. A device built in one country and shipped to another needs a SIM that works on a local network. Swapping that card in a sealed sensor mounted on a pole is expensive or impossible. Manufacturers have historically dealt with this by stocking multiple variants of the same product or by locking devices to a single carrier. Both choices cost money, and both age badly. eSIM and iSIM are the technologies replacing that arrangement, and a new GSMA specification called SGP.32 is making them practical for the kind of unattended devices IoT depends on.

Omdia forecast in 2024 that the installed base of eSIM-equipped IoT devices would grow from just over 1 billion in 2023 to more than 3.6 billion by 2030. In the same research, a survey of over 700 enterprises found that 90 percent planned to adopt eSIM or iSIM technology within two years. Survey intentions overstate behavior, but the direction is clear.

Three Ways to Hold a Subscription

FormWhat it isChange carrier remotely?Typical fit
Removable SIM cardPlastic card in a slotNo, requires a physical swapDevices that are easy to reach and one-market
eSIM (eUICC)A separate soldered chip that holds rewritable profilesYes, over the airGlobal products, hard-to-reach devices
iSIMSIM function built into the main chipset or modemYes, over the airTiny, low-cost, power-constrained devices

An eSIM is a separate component that stores one or more carrier profiles, which can be downloaded and switched remotely. An iSIM puts the same capability inside the processor or modem, so it needs no separate chip. Both follow GSMA standards for remote provisioning. The gains from iSIM are physical and financial: one vendor guide claims up to 98 percent smaller footprint than eSIM setups and up to 50 percent lower production and logistics costs, but those are supplier claims that depend heavily on design. The practical point is that removing a component helps most in devices where board space and bill of materials dominate, such as asset tags, wearables, and low-cost sensors.

Why SGP.32 Is the Quiet Breakthrough

Consumer eSIM, defined in an earlier specification called SGP.22, assumes a person with a screen who scans a QR code and approves a profile. Many IoT devices have no screen, no person, and sometimes no reliable connection. The older machine-to-machine eSIM specification, SGP.02, solved part of this but relied on SMS to manage profiles, which is a practical obstacle for NB-IoT class devices.

SGP.32 was written for headless, long-lived devices. Two roles matter. The eIM, short for eSIM IoT Manager, is a standardized remote manager that coordinates profile downloads and switches across one device or a whole fleet. The IPA, or IoT Profile Assistant, is the device-side component that performs the secure work, and it can run on the device or inside the eUICC itself. The result is that a manufacturer or service provider can push profile changes without a user and without SMS. SGP.32 also supports eIM portability, so a company can change providers of its management backend without being locked in.

What It Changes for a Product Team

  • One stock-keeping unit. A single hardware variant can ship worldwide, with the right local profile loaded after the device reaches its market.
  • Carrier flexibility. Deployments are no longer permanently tied to one operator, which improves negotiating position and resilience when a carrier's coverage or price changes.
  • Logistics savings. Fewer variants, fewer SIM kits, and no physical handling reduce cost and error.
  • Longer product life. A sealed device built to last ten years can adapt to carrier changes, including network sunsets, without a field visit.

The relationship to chips is direct. iSIM-capable modems are most common in low-power LTE-M and NB-IoT parts, and certified iSIM chipsets are not yet widely available, so availability should be checked per product. Thales and Qualcomm announced the first GSMA-certified commercial iSIM in 2023 on a Snapdragon mobile platform, and Kaleido Intelligence projected the iSIM market could reach 300 million units by 2027, about 19 percent of eSIM shipments. Our article on cellular IoT and 5G RedCap covers the modem side, and our guide to IoT chipsets explains how these parts fit among other radios.

A Worked Example: A Fleet Tracker Built in San Jose

Consider a company designing an asset tracker in the South Bay for shipment to customers in North America, Europe, and Asia. This is an illustrative scenario. With removable SIMs, the company would need to select carriers by region, stock cards, and coordinate with customers who might switch carriers. With an SGP.32 eSIM, it ships one hardware version. At activation, the eIM downloads a profile suited to the country, and later swaps profiles if the customer moves assets across borders or if a carrier agreement changes.

The savings are not only financial. If the tracker is attached to a shipping container that crosses several countries, the device can switch to a local profile to avoid roaming charges, as long as the carriers and management platform support it. That is one reason connectivity platforms are now competing on SGP.32 readiness. KORE and Kigen announced in April 2026 that they would roll out SGP.32 connectivity with multi-network resilience, and Eseye has described SGP.32 eSIM orchestration for global resilience. Both reflect a shift from selling SIM cards to selling managed connectivity.

Security and Compliance Implications

Credentials sit in a tamper-resistant secure element, and profile management follows GSMA security requirements. For companies selling into Europe, the Cyber Resilience Act adds legal weight to secure lifecycle management, and some providers recommend using a GSMA SAS-accredited subscription management environment. Hardware-based credentials also support the broader move toward secure-by-design devices, which we discussed in our article on chiplets and RISC-V. The risk to manage is concentration. The eIM is a powerful control point, and a compromised one could disrupt an entire fleet, so access controls and audit logs matter as much as the technology.

A Worked Example: A Cold-Chain Sensor That Crosses Borders

Consider a medical logistics company in the Bay Area shipping temperature-sensitive samples to labs in several countries. This is an illustrative scenario. Each shipment carries a small logger that reports location and temperature over LTE-M. Under the old approach, the company bought SIMs from a global roaming provider and paid premium rates in every country. With an SGP.32 eSIM, the logger can download a local profile when it lands, reporting at local rates, and the company can change suppliers for a region by pushing a new profile instead of replacing hardware.

The design choices that follow are practical. The logger needs enough battery for the profile download, which uses more energy than a routine report. The platform needs rules for when to switch profiles and when to stay on the current one, since switching in the middle of a flight or sea crossing may be pointless. And the company must keep a record of which profile each device used and when, because billing and compliance both depend on it.

Teams that think through these rules early find the technology straightforward. Teams that treat eSIM as a drop-in replacement for a plastic card tend to discover the missing rules in production, usually when a batch of devices lands in a market whose carrier does not yet support the chosen profile.

Implementation Advice

  1. Decide early between eSIM and iSIM. Choose iSIM only if you are building on a certified chipset and board space or cost is critical. Otherwise eSIM is more widely available.
  2. Check true SGP.32 support. Confirm that your mobile network operators and connectivity platform support real remote provisioning, not just preloaded profile options.
  3. Plan the bootstrap connection. Devices need initial connectivity to download a first profile. Keep bootstrap separate from long-term operator choice.
  4. Migrate in parallel. Run SGP.02 and SGP.32 devices side by side instead of switching everything at once.
  5. Connect the eIM to your management platform. Lifecycle visibility belongs in the same place as your device management.

Common Challenges

ChallengeDescription
Operator readinessNot every carrier supports full SGP.32 provisioning yet, and policies differ by country
Chipset availabilityCertified iSIM parts are not yet widespread and are concentrated in low-power cellular chips
Local regulationSome countries require local profiles or restrict permanent roaming
Migration complexityExisting fleets on older specifications need a gradual transition plan
Management concentrationA central eIM is a high-value target and needs strong security

What Comes Next

Expect eSIM to become the default for new cellular IoT products and iSIM to follow as chipsets mature, with further GSMA specifications intended to streamline iSIM deployment. The competitive ground will shift to connectivity management, where providers differentiate on coverage, pricing across countries, and tools to orchestrate profiles. For product teams, the message is practical. Treat the SIM as software-managed infrastructure, plan for carrier change from the start, and choose partners who can show working SGP.32 deployments. See also our article on satellite IoT connectivity, where remote provisioning matters even more.

Frequently asked questions

An eSIM is a separate chip on the circuit board that stores rewritable carrier profiles. An iSIM puts the same function inside the main processor or modem, removing the separate component. Both support over-the-air provisioning under GSMA standards.

SGP.32 is the GSMA specification for eSIM for IoT, built for headless, long-life devices with no user interface. It uses an eIM remote manager and a device-side IoT Profile Assistant to push profile changes without SMS or user action.

Consumer eSIM, defined in SGP.22, relies on a person scanning a code and approving a profile on a screen. IoT eSIM under SGP.32 lets a manufacturer or provider manage profiles remotely, which suits unattended sensors and trackers.

Omdia forecast that eSIM-equipped IoT devices would grow from just over 1 billion in 2023 to more than 3.6 billion by 2030. A survey in the same research found 90 percent of over 700 enterprises planned to adopt eSIM or iSIM within two years.

Not fully. Certified iSIM chipsets are still limited and most common in low-power LTE-M and NB-IoT parts. Thales and Qualcomm announced the first GSMA-certified commercial iSIM in 2023, and Kaleido Intelligence projected up to 300 million iSIM units by 2027.

Confirm your carriers and connectivity platform support true SGP.32 remote provisioning, plan a bootstrap connection, check local regulations on profiles and roaming, migrate older fleets gradually, and secure the eIM since it controls the whole fleet.

Related articles

Top