The SIM form factor is decided early, usually by whoever is designing the board, and usually as a hardware question. Two years later it turns out to have been a connectivity strategy question, and by then several thousand units are in the field.
The three options do not differ much in what they do on day one. They differ enormously in what you are able to do in year four.
The plastic card in its various sizes: 2FF, 3FF and 4FF. The subscriber identity lives on a chip you swap by hand. Familiar, cheap, and supported by every module on the market.
The same chip in a solderable package, mounted directly on the board. Industrial temperature range, vibration resistant, sealed against humidity and corrosion. This is the standard choice for anything mounted outdoors or inside machinery, and it is what most people mean when they say a device has "an embedded SIM" in the physical sense.
Here the terminology causes real confusion. eSIM describes a capability, not a shape. An eUICC is a SIM whose operator profile is downloaded and replaced over the air. It comes in every form factor above, including the removable card. A soldered MFF2 chip without eUICC is permanently tied to the profile it shipped with. A removable 4FF card with eUICC is remotely reprogrammable.
Ask a supplier for "an eSIM" and you learn nothing about whether the profile is changeable. Ask whether it is eUICC capable, and under which GSMA specification, and you learn everything.
The SIM function moves inside the cellular modem's system on chip as a secure enclave. No separate component, no board space, no solder joint to fail. Power draw drops, bill of materials drops, and the physical attack surface of a removable credential disappears. iSIM is eUICC capable by design.
The constraint is hardware. iSIM support is a property of the chipset, so it is available to teams designing new hardware and unavailable to teams shipping an existing board.
An industrial device has a service life of eight to fifteen years. Your connectivity contract runs for two or three. Something has to give, and without eUICC the thing that gives is a field engineer with a van.
Remote provisioning changes four situations from hardware problems into software ones.
A market's roaming rules change. Regulators in Brazil, Turkey, India and China, among others, restrict how long a foreign SIM stays attached to a domestic network. With eUICC you push a local profile to the affected units. Without it you ship replacement SIMs to installed assets.
Your provider stops fitting. Coverage in a new market, a commercial disagreement, a service level that keeps slipping. Portability is what turns that into a decision rather than a trapped position.
Devices ship before the destination is known. Manufacturers selling through distribution rarely know which country a unit ends in. A bootstrap profile gets the device online, then the operational profile arrives once it reports where it woke up.
An operator retires a network. 2G and 3G shutdowns continue across Europe. A profile change moves the fleet to a network with a future.
GSMA published SGP.22 for consumer devices. It assumes a user with a screen who taps to confirm a profile change. A water meter in a basement has neither a screen nor a user.
SGP.32 was written for IoT. Profile management is driven remotely by the fleet operator through an eSIM IoT remote manager, with no user interaction and no requirement for the device to hold a full consumer client stack. It also works over LTE-M and NB-IoT, where the earlier specification struggled. If you are specifying eUICC hardware for a fleet, SGP.32 is the version to ask about by name.
Match the form factor to the deployment reality rather than to the datasheet.
Three questions settle most cases. Does a person reach the device after installation? Does it cross a border, ever? Is the hardware design still open?
This is where deployments go wrong.The SIM decision is a hardware and portability decision. It is not a security decision and it is not a compliance decision.
A profile determines which network your device attaches to. It says nothing about where that traffic then travels, what the device is permitted to reach, or who else is on the same network path. IXT SecureNet keeps device traffic off the public internet on a private APN with private addressing and direct cloud connections. IXT Zero Trust checks every session before it opens and maps traffic across the fleet in real time.
Keep the layers distinct. The SIM identifies the device. SecureNet controls where the traffic goes. Zero Trust decides what each session is allowed to do. Blending them into one story produces a purchase that disappoints on all three counts.
IXT supplies all three form factors on a dedicated mobile core built for IoT from the ground up rather than virtualised on shared infrastructure. One SIM covers 600+ mobile networks across 190+ countries, and IXT supports local IMSI options in key markets to reduce permanent roaming risk.
No, and the overlap in language causes expensive mistakes. Soldered describes the package, MFF2. eSIM describes eUICC, the ability to change the operator profile remotely. A chip is one, the other, both, or neither.
Ask before you buy. Profile portability and the technical route for handing management to another party are contractual and platform questions, not properties of the hardware. A provider comfortable answering it in writing is telling you something useful.
The credential sits in a certified secure enclave inside the chipset. Removing the physical card removes a tamper path rather than adding one.
Yes, and SGP.32 was specified with those bearers in mind, which is one of the practical improvements over the consumer specification. Confirm regional availability of the bearer itself before you commit.
eUICC helps, because it lets you move an affected fleet to a local profile without touching the hardware. Multi IMSI addresses the same problem from a different angle by holding several identities on one SIM. Most cross border fleets end up using both.
A removable eUICC card retrofits into existing hardware where the SIM slot is reachable. Where it is not, multi IMSI on the installed base handles network flexibility, and the form factor decision moves to the next hardware revision.
Take your bill of materials to the connectivity conversation, not after it. The form factor, the eUICC specification and the roaming strategy are one decision made three times, and the cost of getting them out of order is measured in site visits.
Ask us how it works for your deployment. Book a demo at ixt.io.