Customer experience

UXHub

Launch a branded self-service experience for plan purchase, activation, usage, billing, upgrades, and support.

YOUR BRANDPLANSSELF-SERVICESUPPORTExplore UXHub
Three hubs on one data model, one API, and one invoice.Read the API docs
Platform
Solutions
Services
Customers
Resources
Home eSIM IoT SIM Cards: Form Factors, eSIM and How to Choose

IoT SIM Cards: Form Factors, eSIM and How to Choose

What an IoT SIM card does, how form factors, eSIM and global SIMs differ, how to compare plans, and the acceptance tests to run before production.

Orange line-art illustration of a SIM card beside a small circuit board chip, a cell tower and a signal arc on a warm cream rounded panel.
Picture of SivaSai

SivaSai

Founder’s Office | Engineer → Marketer | Scaled Organic to 500K+ Impressions | SEO & AI Search | Email Campaigns & Funnels | AI-driven B2B SaaS Growth

TL;DR / At-a-Glance Summary

An IoT SIM holds the credentials a device uses to join a cellular network, but package, profile capability, coverage and plan are four separate decisions. Specify each one, compare complete lifecycle cost, and accept the SIM on real hardware before ordering production inventory.

Package is not capability

Removable or soldered says how it fits. It does not prove eUICC or remote profile support.

Name the GSMA standard

SGP.02, SGP.22 and SGP.32 are different architectures. Ask for the version and components.

Global is not universal

Test sites, bands and permanent roaming rules country by country.

Compare lifecycle cost

Price activation, idle SIMs, suspension and exit, not only the data rate.

Accept it on real hardware

Run activation, change, recovery and retirement on the actual device and keep written results.

Last verified 2 November 2026.

An IoT SIM card is the subscriber identity module that lets a cellular IoT device authenticate on a mobile network. It holds the credentials, while the modem supplies the radio and the provider supplies the network service. What you actually buy is a combination of four things: a physical package (a removable card or a soldered chip), a profile capability (a fixed profile or an eUICC that can load new ones), a service footprint (which networks and countries) and a commercial plan.

Those four decisions are separate, and most IoT SIM mistakes come from treating one as proof of another. A soldered chip does not guarantee remote profile changes. A “global” label does not guarantee coverage at your site. This guide explains the form factors, compares SIM, multi-IMSI and eSIM options, covers global SIMs and permanent roaming, sets out how to compare plans, and gives an acceptance test to run before you order production inventory. If you have not yet chosen a radio technology, start with the NB-IoT, LTE-M and 5G RedCap comparison.

What does an IoT SIM card actually do?

The SIM provides subscription identity and authentication keys. When the device powers up, the modem uses them to register on a network. Whether data then flows depends on the modem bands, antenna, firmware, the provider’s agreements and your application. Buying a SIM does not establish coverage or application availability.

What separates an IoT SIM from a phone SIM is the surrounding offer: which device types are permitted, what environmental grade the part is qualified for, what lifecycle controls exist (activate, suspend, retire), how data is pooled, and what support is included. A consumer plan may prohibit machine use or lack fleet controls. An “IoT” label alone does not tell you a temperature rating, a data retention period or a security guarantee, so ask for the part specification.

Keep three identifiers mapped in your inventory. The device serial number identifies the product. The ICCID identifies a SIM or profile. The EID identifies an eUICC (the secure chip that can hold several profiles). When a removable card moves between devices, or a downloaded profile replaces another, record it as an inventory event. One permanent identifier does not cover everything. For the older machine-to-machine vocabulary, see what M2M SIMs are.

Which SIM form factor and environmental grade fit your device?

The form factor decides how the SIM fits into the device. The environmental grade says the conditions the part is qualified for. They are different questions, and neither tells you what profiles the SIM can hold.

Removable cards come in the familiar sizes: 2FF (mini), 3FF (micro) and 4FF (nano). The removable sizes are defined in ETSI TS 102 221, the UICC-terminal interface specification. MFF2 is the machine-to-machine package: a small surface-mount chip, roughly 6 by 5 millimeters with eight contacts, that is soldered to the circuit board. It is covered by ETSI TS 102 671. Vendors sell 3-in-1 punch-out cards for prototyping and a soldered MFF2 for production.

Option Useful when Confirm before ordering
2FF, 3FF or 4FF removable card The device has a compatible holder and field replacement is practical Holder fit, vibration and contact reliability, environmental grade, and whether the card is a plain UICC or an eUICC
MFF2 soldered package The enclosure is sealed, vibration is high, or tampering and removal are concerns Assembly process, qualified temperature range, and which provisioning architecture the chip supports
Integrated SIM (iSIM) The chosen module already includes SIM functionality in its chipset Exact module, security certification, commercial availability and service compatibility

Sources for the form factors: ETSI TS 102 221 and TS 102 671; vendor documentation for MFF2 geometry and ratings. Fit and qualification remain part-specific.

Watch out: MFF2 describes a package. It does not prove the chip is an eUICC, that it is automotive-qualified, or that it will last a stated number of years. Industrial ratings such as an extended temperature range are published per part, so get the datasheet for the exact SKU rather than assuming a supplier’s best variant applies to its whole catalog.

Choose by serviceability. A sealed utility meter often favors a soldered chip because replacing a card is impractical. A serviceable gateway may favor a removable card because a technician can swap it. Neither choice settles who can supply the next subscription or whether you may change provider, which is a profile and contract question, covered next.

How do SIM, multi-IMSI and eSIM differ for IoT?

A traditional SIM stores one fixed set of credentials tied to one operator. To change operator you replace the card, which means reaching the device. An eSIM uses an eUICC that can store several operator profiles and has them downloaded and switched remotely. Multi-IMSI SIMs sit in between: one SIM carries several subscriber identities that the provider can enable.

  Traditional SIM Multi-IMSI SIM eSIM (eUICC)
Subscriber identity One fixed profile Several identities on one SIM, managed by the provider Several profiles stored; one active at a time
Changing operator Physical swap Provider enables another identity, within its agreements Remote profile download and enable, if the architecture and contract allow
Package Removable card or soldered chip Either Either (removable cards can be eUICC too)
Good fit Small, local, serviceable deployments Fleets that need cross-border service from one SKU Long-lived or hard-to-reach devices, and fleets that may change provider
Main risk Operator lock-in and truck rolls Selection policy and exit are the provider’s Needs a compatible device, reachable provisioning path and tested recovery
A paper-cut eUICC chip holds several operator profile cards while a cream ribbon carries a new profile in from a distant cell tower.
An eSIM stores several profiles on one chip, and a remote change brings a new one in without touching the device.

Cost trade-offs are real but depend on your fleet. Traditional SIMs usually cost less per unit and suit small, static deployments. The saving from eSIM comes mostly from avoided site visits and inventory, which only pays off if devices are hard to reach or likely to change provider. Treat any “eSIM is always cheaper” claim as unproven until you price your own fleet.

GSMA specifications in plain terms

The GSMA defines more than one remote provisioning architecture, and they are not interchangeable. SGP.02 covers machine-to-machine remote provisioning, the older model that relies on a subscription manager and, in practice, SMS to switch profiles. SGP.22 covers consumer devices, where the Local Profile Assistant on the phone downloads profiles from a server. SGP.32 specifies IoT remote provisioning for network- and UI-constrained devices. It splits the consumer role into an IoT Profile Assistant (IPA) and an eSIM IoT Remote Manager (eIM) that can manage one device or a whole fleet.

GSMA has published more than one revision of SGP.32 since the first release in 2023, so a supplier saying “SGP.32 compliant” should name the version, the device components that implement it and the profile and management services behind it. A standards label alone does not guarantee that a fleet can change operator unattended. Existing fleets built on SGP.02 are not converted by an SGP.32 management service, so migration needs a compatibility check on the deployed eUICC, module and firmware. For the architecture side by side, read SGP.22 vs SGP.32, and for the delivery sequence see remote SIM provisioning explained.

For procurement, ask who owns the profile relationship, which alternative providers may supply profiles, what bootstrap connectivity the first connection uses, and what an exit requires. Those answers are worth more than a general promise to eliminate lock-in.

What does a global IoT SIM include?

A global IoT SIM gives a device access to multiple countries or networks under one commercial arrangement. Depending on the provider, it works through roaming agreements, multiple IMSIs or downloaded eSIM profiles. Its benefit is logistical: one SKU to stock and ship instead of separate subscriptions per market. It is not universal hardware compatibility. The module still needs the right bands and regional approvals, and the service needs eligible access where you deploy.

Ask for a coverage list that names the technology (LTE-M, NB-IoT, LTE Cat 1 and so on) and the service scope per country, then test representative sites. A long country count says nothing about indoor coverage, permitted long-term use or application performance. Multiple available networks also do not mean the strongest signal is chosen at every moment: selection depends on device behavior and provider policy.

Permanent roaming and local profiles

Permanent roaming means a device from a foreign subscription stays on a visited network for the long term. Some countries restrict or condition it for IoT, and the rules differ by market and change over time. A global SIM therefore does not automatically settle compliance. Depending on the country, a deployment may need a local IMSI or a locally provisioned eSIM profile. Even then, a local subscriber identity does not by itself prove local data routing. Assess the rules country by country with your provider, and keep the answers in writing. The eSIM orchestration guide and the global IoT connectivity overview go further on multi-country operations, and single-carrier risk explains why one network is a fragile design.

Can a cellular SIM add satellite access?

Not by itself. Satellite service needs a supported device, radio and network as well as an eligible subscription. 3GPP Release 17 introduced NB-IoT and eMTC support for non-terrestrial networks, but that does not make existing terrestrial modems satellite-ready. See 3GPP’s non-terrestrial networks overview for the standard’s scope.

How should you compare IoT SIM plans and contracts?

Compare the complete cost of the same fleet over the same period, not the headline data rate. Include the SIM or profile, activation, recurring access, usage, platform services and retirement. A cheap per-megabyte rate can sit inside an expensive operating arrangement. The table lists the questions to put to each quote and the evidence to keep. It contains no quoted rates.

Cost component Question for the quote Evidence to retain
SIM and setup Are manufacturing, shipping, profile and activation charges separate? Itemized quote and the activation trigger
Recurring service Which subscription states incur access or platform fees? State definitions and minimum commitments
Data and messaging How are sessions rounded, pooled and charged above the allowance? Metering rules and representative usage
Changes and exit Do suspension, profile changes or termination create fees? Change schedule, notice period and final invoice rules

Separate steady telemetry from installation, diagnostics and firmware-update traffic. A fleet average can hide a small group of devices that use most of the allowance, so compare the real distribution, including idle units, against each pool’s countries, plans and eligible subscription states. One customer account does not necessarily mean one global pool.

A prepaid allowance can suit a predictable low-usage device if its validity and replenishment terms fit. A recurring pool can suit variable usage across eligible lines. Neither is always cheaper. Check what suspension really stops, since access or minimum-commitment fees may continue. The IoT connectivity cost guide gives the wider cost framework, and the connectivity comparison helps when you are weighing providers.

How do you accept a SIM before fleet deployment?

Follow the subscription from inventory through activation, change and retirement on representative hardware, and define success at the application and billing layers, not just in the provider portal. Record requested actions, confirmed states, timestamps and failures, so the rollout rests on demonstrated behavior rather than a good demo.

A SIM card travels a cream road from an inventory box past a test tube and an active cell tower to a pause sign and a locked padlock, showing the IoT SIM lifecycle states.
Each lifecycle stage needs its own written acceptance result.
  1. Fix the configuration. Record SIM part, profile, module, firmware, bands, antenna and intended service, so a manufacturing substitution triggers a deliberate review.
  2. Prove the first connection. Activate and confirm the expected application message. If registration succeeds but data does not arrive, check credentials, APN settings and support ownership.
  3. Exercise supported changes. Test suspension, reactivation and any profile change. Note which actions need a reachable device and how failed or partial requests are recovered.
  4. Check the actual footprint. Test representative sites and movement patterns, and keep network and application observations instead of relying on signal bars.
  5. Retire and reconcile. Confirm service removal and the final charge, and keep the mapping needed to explain a later invoice or a returned device.

The same process serves different products, but the test changes. A moving tracker needs route and recovery tests. A sealed sensor needs installation and power checks. A payment terminal needs the transaction path checked. Pick the test from the cost of failure. For eSIM, also test a device that loses connectivity during a profile operation, and do not remove the last known working profile before the recovery route is proven.

Buyer checklist: confirm the part, the supported provisioning architecture, the service footprint, the complete charges, the recovery owner and the exit process. Keep a written acceptance result for each lifecycle action you require.

Where does a connectivity platform fit?

A SIM only authenticates the device. Day-to-day, a fleet also needs someone to coordinate carrier services, subscription state and billing across providers. Spenza is an MVNE platform that supports enterprise IoT connectivity operations of that kind. Its Butlr case study reports that Butlr cut regional launch time for sensors from 60 days to 7. That result describes one documented rollout. For businesses developing connected IoT products, professional Embedded Engineering Services can help with hardware design, firmware development, and system integration. It does not prove a universal SIM activation time, a particular radio’s coverage or the savings of any plan, and a new fleet still needs its own part qualification and tests.

The control layer is covered in the guide to connectivity management platforms and the single-pane-of-glass overview. Subscription operations stay separate from device firmware management and application health, so name an owner for each layer before you buy.

Conclusion: specify the SIM as part of the whole device

Choose an IoT SIM as part of a supported device and service design. Keep packaging, profile capability and service footprint as separate decisions, check environmental claims against the exact part, and validate every market your product must serve. Compare lifecycle cost, including idle inventory and retirement, before selecting a plan. The practical next step is a small acceptance exercise on real hardware, with written conditions for activation, recovery and billing, run before the order grows to production quantities.

IoT SIM card FAQs

What is an IoT SIM card?

An IoT SIM card holds the subscriber credentials a cellular IoT device uses to authenticate on a mobile network. It comes as a removable card or a soldered chip, and it is sold with an IoT plan covering permitted devices, data, lifecycle controls and support. The modem and the provider’s network still determine whether the device connects.

What is the difference between a SIM and an eSIM for IoT?

A traditional SIM stores one fixed profile tied to one operator, so changing operator means replacing the card. An eSIM uses an eUICC that can store several profiles and be managed remotely. The benefit depends on a compatible device, a reachable provisioning path and a contract that allows the change.

Can a removable SIM support eUICC?

Yes, when the particular product includes that capability. Removable describes the physical package, and eUICC describes profile functionality. Confirm the supported provisioning architecture, compatible device software and available profile services. A plastic card proves neither remote provisioning nor its absence.

Does a soldered SIM last longer than every removable card?

Not automatically. Lifetime depends on the qualified component, operating conditions and use. Soldering changes mechanical integration and serviceability, but temperature limits and data retention remain part-specific. Ask for the qualification record for the exact part and assess the whole assembly in its intended environment.

What are SGP.02, SGP.22 and SGP.32?

They are GSMA remote SIM provisioning specifications. SGP.02 covers machine-to-machine provisioning, SGP.22 covers consumer devices through the Local Profile Assistant, and SGP.32 covers IoT devices with an IoT Profile Assistant and an eSIM IoT Remote Manager. They are not interchangeable, so ask a supplier which one and which version its product implements.

Do global IoT SIM cards avoid permanent roaming restrictions?

Not automatically. Some countries restrict or condition long-term foreign roaming for IoT devices, so depending on the market you may need a local IMSI or a locally provisioned eSIM profile. Evaluate the rules country by country with your provider rather than assuming one roaming setup works everywhere.

Does suspending a SIM stop all charges?

Only to the extent the service terms say. Access, platform or minimum-commitment fees may continue while a SIM is suspended. Ask which subscription states change billing and when, then verify the result on a representative invoice before relying on suspension for cost control.

Can a profile change upgrade the radio technology?

No. A profile change cannot add capabilities the device lacks. The modem, firmware, bands and antenna still determine which radio services are usable. A new subscription may authorize different access, but engineering must confirm the device supports it before you plan a fleet transition.

Contact Us Today

 

Related Articles

Discover insights on telecom trends, IoT, eSIM technology, and connectivity solutions with guides.

Orange line drawings of a SIM card, a globe, a signpost with two opposing arrows, a cell tower and a contract sheet with a check mark, on a pale panel beside the post title.

Permanent Roaming Rules by Country for IoT Devices

Explore IoT permanent roaming rules by country, including restrictions, time limits, and local eSIM requirements. Compare rules and plan global
Smartwatch surrounded by shipping, SIM, replacement, renewal and support icons for the IoT subscription lifecycle.

IoT Device Subscription Lifecycle: Activation to Cancellation

Manage IoT device subscriptions from activation and replacement to failed payments, renewals, cancellation and final supplier-bill reconciliation.
Authentication shield, signaling nodes, handset and headset illustrating STIR/SHAKEN call delivery testing.

Does STIR/SHAKEN A-Attestation Prove Call Delivery?

A-attestation does not prove a call reached a person. Learn six tests for SIP signaling, handset alerting, answer type, two-way

Subscribe for Smarter Connectivity Insights

Join thousands of professionals receiving expert perspectives, industry trends, and practical strategies shaping the future of telecom and connected devices.