You chose a SIM format at the start of the project. Three years later that choice decides which countries you ship to, how many carrier contracts you hold, and how much engineering time goes to connectivity instead of product.
IoT SIM, eSIM, iSIM, eUICC. Vendor material treats these as one shopping list. They are not. Two describe hardware. One describes a remote provisioning standard. One describes where the SIM sits on the board. Sorting them out before hardware freeze costs less than sorting them out afterwards.
What each term means
The removable SIM
The plastic card, in 2FF, 3FF or 4FF form. A person puts it in the device and a person takes it out. Field swaps are the fallback when connectivity breaks, which is also the weakness: someone has to travel to the device.
MFF2, the soldered SIM
The same chip, soldered to the board. It survives vibration, temperature swings and humidity, which matters for meters, chargers and vehicle units. Once it is soldered, nobody swaps it. Whatever profile sits on that chip is the profile the device lives with, unless the chip accepts new profiles remotely.
eSIM and eUICC
Here is where the language breaks down. eSIM in common use means the soldered form factor. eUICC means the software layer that accepts a new operator profile over the air. A device holds one without the other. A soldered SIM with no eUICC is a permanent commitment. A removable SIM with eUICC is reprogrammable and still falls out of a socket.
The standard to ask a supplier about by name is GSMA SGP.32, written for IoT devices with no screen and no user. Earlier eSIM standards assumed a phone and a person to tap accept. SGP.32 removes that assumption.
iSIM
The SIM function moves onto the device's main processor, inside the cellular modem itself. No separate chip, no separate footprint, lower power draw. For devices where board space and battery life set the design limits, that is the argument. It also ties the SIM to the silicon you selected, so module choice narrows.
The question underneath the form factor question
Form factor decides how the SIM survives the field. It does not decide which networks the device reaches once it gets there.
That is a separate layer: how many operator identities the SIM holds, how it switches between them, and whether the switch happens without a truck roll. A device that crosses three borders in a working week touches three carrier relationships. Multi-IMSI handles that at the identity level. eUICC handles it at the subscription level. They solve different halves of the same problem and they work together.
Permanent roaming is the constraint most projects meet late
A device that sits on a foreign network indefinitely is roaming permanently, and a growing list of markets restricts it. Brazil, Turkey, India and Canada each apply rules of their own, and enforcement varies by operator. It arrives as a disconnected fleet, not as a warning letter.
The answer is local network identity rather than permanent visitor status. IXT supports local IMSI options in key markets to reduce permanent roaming risk. Your SIM strategy has to carry that, which rules out a single-identity SIM for any fleet shipping internationally.
Choosing
- Device is reachable, volumes are low, deployment is one country: a removable SIM with eUICC keeps the cost down and the options open.
- Device ships internationally and stays in the field for years: MFF2 with eUICC, plus multi-IMSI identities for the markets you sell into.
- Device is space-constrained or battery-constrained: iSIM, decided at module selection, not after it.
- Device sits in a regulated sector: the SIM is the identity anchor for every layer above it, so decide it alongside the security architecture rather than before.
Where the SIM stops
The SIM identifies the device. It does not protect the traffic. Confusing the two is how a deployment ends up with a well-chosen SIM sitting on a flat, publicly routed network.
At IXT, SecureNet keeps device traffic off the public internet and routes it to your systems directly. The Zero Trust layer checks every session in the network and cloud, so a device reaches the one application it is authorised to reach and nothing else. The SIM is where that chain starts. It is not where it ends.
Questions buyers ask
Is eSIM the same as eUICC?
No. eSIM describes the physical form. eUICC describes the software that accepts a new operator profile remotely. Ask a supplier for both by name.
Does multi-IMSI make eUICC unnecessary?
No. Multi-IMSI switches between identities already loaded on the SIM. eUICC loads a subscription that was never there. Long-lived fleets want both.
Which form factor suits a device with a ten year life?
MFF2 or iSIM. Both survive the environment. Both demand remote provisioning, because ten years outlasts most carrier contracts and some carriers.
Do we have to pick one format across the whole fleet?
No, and most fleets do not. One SIM covers 600+ mobile networks across 190+ countries, and the same subscription runs across physical SIM, eSIM and iSIM. Match the form factor to the device. Keep the connectivity layer common.
What breaks first when the SIM strategy is wrong?
Cross-border deployments. A single-identity SIM works fine in the home market and strands a fleet the moment it ships somewhere with permanent roaming rules.
What to decide before hardware freeze
Three things: the form factor your environment demands, whether the SIM accepts new profiles remotely, and which of your target markets restrict permanent roaming. The first is a hardware decision and it is permanent. The other two decide whether the first one ages well.
Ask us how it works for your deployment. Book a demo at ixt.io.
