Dutch 
English 
German 
Spanish The procurement manager orders 500 SIM cards from a consumer mobile operator for a new fleet tracking rollout. The cards arrive, the devices go live, and within 90 days, 40% of the SIMs have been deactivated. The carrier’s fair-use policy flags permanent roaming. The SIMs were designed for phones that travel temporarily, not for devices installed in trucks that cross borders every day. The team spends three months replacing 200 SIMs mid-deployment, paying twice for connectivity and absorbing the delay.
This is the most common and most avoidable mistake in IoT deployments: using consumer SIM cards for machine connectivity. Consumer SIMs and IoT SIMs look almost identical. The difference is entirely in how they behave at scale, under continuous operation, across borders, and in environments no smartphone was designed for.
This guide explains what makes a SIM card suitable for IoT and M2M deployments, how to choose between form factors, what roaming architecture determines whether your devices stay connected across borders, what security features matter at enterprise scale, and what questions to ask when evaluating suppliers. It covers everything from a 10-device pilot to a 50,000-unit global rollout.
Wat is een IoT-simkaart?
An IoT SIM card is a subscriber identity module designed specifically for machine-to-machine (M2M) communication and connected device deployments. The hardware may be physically similar to a consumer SIM, but the underlying specifications, software, and commercial terms are built for a different operating model.
Three differences define the distinction.
Permanente roaming zonder beperkingen
A consumer SIM is sold on the assumption that the user lives in one country and travels occasionally. Most consumer contracts permit roaming for 30 to 90 days before the carrier applies penalties, throttles the connection, or deactivates the SIM. An IoT SIM is designed for devices that may be permanently installed in another country, or that cross borders continuously as part of their function. Permanent roaming without rate shock or deactivation thresholds is a commercial standard for IoT SIMs, not an optional feature.
Industrial durability
Consumer SIMs are rated for the environments smartphones encounter. IoT SIMs designed for industrial use, specifically the MFF2 (Machine Form Factor 2) chip format, are rated for operating temperatures of -40 degrees Celsius to +105 degrees Celsius, continuous vibration, high humidity, and exposure to dust, salt, and chemicals. A standard plastic SIM card installed in outdoor infrastructure, agricultural equipment, or a maritime vessel will fail in conditions that an industrial-grade SIM handles without issue.
Designed for remote, unattended operation
A smartphone has a user who can reset it, change carriers, or call for support. An IoT device may be installed in a remote location for five years without physical access. IoT SIMs are designed for zero-touch operation: automatic network selection, remote management via a cloud platform, and remote provisioning without SIM swaps. Everything that a human user does manually on a consumer device needs to happen programmatically and remotely on an IoT deployment.
IoT SIM form factors: physical SIM, eSIM, and MFF2 ChipSIM
The form factor determines how the SIM is physically installed, what environments it can operate in, and how it is managed over its lifetime. The right choice depends on the device type, the operating environment, and whether profiles need to change after deployment.
Physical SIM (3-in-1)
The standard removable plastic SIM card, available in full-size (1FF), mini (2FF), micro (3FF), and nano (4FF) form factors, sold as a 3-in-1 that can be broken to size. Suitable for devices with a SIM slot, accessible for manual swaps, and compatible with any device that accepts a standard SIM. The limitation is that physical removal and replacement is required to change carrier or profile, which is impractical for devices deployed at scale or in inaccessible locations.
eSIM (eUICC)
An embedded SIM with a removable or fixed profile that can be updated over-the-air. The eUICC (embedded Universal Integrated Circuit Card) standard enables remote SIM provisioning: a carrier profile can be downloaded and activated on the device without physical access. This is the practical solution for managing carrier profiles at scale, for complying with local regulations that require a native carrier profile rather than a roaming SIM, and for deployments where devices cannot be physically reached after installation. Activation in 60 seconds via QR code is available for devices that support it.
MFF2 ChipSIM (soldered industrial)
The MFF2 format is a chip soldered directly onto the device’s circuit board during manufacturing. It cannot be removed, which is both its limitation and its primary advantage. Soldering eliminates the mechanical failure mode of a SIM slot: no loose contact, no ingress of dust or moisture around the card, no possibility of vibration unseating the connection. MFF2 SIMs are rated for extreme environments that would destroy a removable SIM. Operating temperature range of -40 degrees Celsius to +105 degrees Celsius is standard. For devices in agriculture, heavy industry, maritime, energy infrastructure, and outdoor asset tracking, MFF2 is the correct choice from the start of the hardware design process.
Weconnect provides all three form factors under a single contract, managed through the same platform. Deployments that mix device types, some with SIM slots, some with soldered chips, some with eSIM capability, are managed from one portal rather than three separate supplier relationships.
Roaming architecture: the decision that determines whether your devices stay connected
For IoT deployments crossing borders or operating in countries other than the supplier’s home market, roaming architecture is the most important technical decision in SIM selection. It determines whether devices connect reliably, what happens at territorial borders, and whether costs scale predictably.
Steered roaming
A steered SIM has a preferred network list programmed into it. The SIM is directed toward specific carrier partners, typically the partner that has the most favourable commercial relationship with the SIM provider. In practice, this means the device may reject a stronger signal from a non-preferred carrier and hold onto a weaker preferred carrier connection. For high-volume IoT deployments crossing multiple countries, steered roaming creates systematic coverage gaps at transitions and unpredictable performance based on the SIM provider’s commercial agreements rather than actual network conditions.
Non-steered multi-network access
A non-steered SIM has no preferred network list. The device connects to whichever network provides the strongest signal at its current location, across all available carriers in the region. For an IoT device crossing from the Netherlands into Germany, the SIM detects the German carriers as soon as their signal is available and switches automatically, without holding onto the Dutch network past the point of usable signal. This is not a luxury feature. It is the operational baseline for any deployment that crosses borders or operates at the edge of single-carrier coverage.
Weconnect provides non-steered multi-network access as the default architecture across its IoT SIM oplossingen, with 700+ carrier partnerships in 195 countries and automatic connection to the strongest available network at every location.
Permanent roaming vs local breakout
Permanent roaming means a SIM registered on a foreign carrier on a continuous basis, which consumer carriers prohibit but IoT carriers explicitly permit. The alternative, local breakout, involves eSIM provisioning with a native carrier profile for each country of operation. Local breakout eliminates some roaming costs and satisfies regulatory requirements in markets that mandate local carrier registration (notably some Asian and Latin American markets). For European IoT deployments, permanent roaming on a non-steered multi-network SIM is typically simpler and equally cost-effective.
IoT SIM security: what enterprise deployments require
Consumer SIM security is designed for individual users. IoT SIM security is designed for networks of devices transmitting operational and sometimes safety-critical data, often running unattended and connected to backend infrastructure. The security requirements are different in kind, not just in scale.
Particuliere APN
A Private APN (Access Point Name) creates a closed network path from device to corporate infrastructure. Traffic from devices on a private APN never touches the public internet. It flows directly from the SIM through an encrypted tunnel to the organisation’s data centre firewall. This eliminates a class of attack vectors: a device compromised on the public internet cannot be reached from outside the private APN, and data in transit cannot be intercepted on public routing infrastructure. Private APN is the standard security architecture for deployments handling sensitive operational data, SCADA connectivity, medical telemetry, or financial transactions.
IPsec VPN
An IPsec VPN adds end-to-end encryption on top of the private APN architecture. Even within the closed network path, data is encrypted between endpoint and destination. For deployments where data sensitivity requires encryption in transit regardless of network path, IPsec VPN provides that guarantee.
IMEI locking
IMEI locking binds a SIM card to a specific device IMEI. If the SIM is removed from the device and inserted into a different device, it will not register on the network. This prevents SIM card theft and unauthorised device swapping, which are relevant risks in field deployments where devices are physically accessible. An alert can be configured to notify the operations team if an IMEI mismatch is detected.
Fixed IP addressing
A fixed IP SIM retains the same IP address regardless of network transitions or device reboots. This enables consistent firewall rules at the corporate end: the firewall can whitelist specific device IP addresses rather than managing dynamic IP ranges. For SCADA systems, remote diagnostics, and any two-way communication where the central server needs to initiate a connection to the device, fixed IP is a functional requirement, not a security option.
Data plans for IoT: pay-per-GB, unlimited, and shared pools
IoT data consumption varies enormously across deployment types. A temperature sensor transmitting a daily reading uses kilobytes per month. A connected camera transmitting continuous video uses gigabytes per day. Matching the data plan to the consumption profile is the difference between a cost-effective deployment and one that is chronically over or underprovisioned.
Pay-per-GB
Pay-per-GB plans charge for actual data consumed with no minimum commitment per SIM. This is the correct model for deployments with variable or seasonal consumption, for devices that are idle for extended periods, and for pilots where actual consumption is unknown. The risk is overage charges if a device behaves unexpectedly. Usage alerts and hard caps configured in the management platform mitigate this.
Unlimited plans
Unlimited plans provide a set monthly allowance per SIM with no overage charges above a soft cap. Suitable for high-throughput devices with predictable continuous consumption. The economics make sense when the per-GB rate on a pay-per-GB plan would exceed the unlimited monthly fee for that device’s typical usage.
Shared data pools
A shared data pool aggregates the allowances of all SIMs in a deployment into a single allocation. A device that consumes more in one month draws from the pool, a device that consumes less contributes back. The fleet manager sees one total consumption figure, not 500 individual SIM balances. Shared pools are the practical choice for large deployments where individual device consumption varies but total fleet consumption is predictable. They eliminate the administrative overhead of adjusting individual SIM plans and reduce the cost of provisioning peak headroom per device.
Managing IoT SIMs at scale: the connectivity management platform
A deployment of 50 SIMs can be managed manually. A deployment of 5,000 cannot. The connectivity management platform (CMP) is the operational infrastructure that makes large IoT deployments administrable, and it should be evaluated alongside the SIM itself when selecting a provider.
What a CMP needs to do
At minimum, a CMP provides SIM activation, suspension, and deactivation, real-time data usage monitoring per SIM, usage alerts and hard data caps, and basic reporting. At enterprise level it adds cost-centre allocation (assigning data costs to specific projects, departments, or clients), API access for integration with internal systems, fleet-level and SIM-level analytics, and the ability to delegate management to sub-accounts or reseller partners.
Cost-centre management
The cost place section of a CMP allows fleet managers to separate data consumption by project, department, client, or any other organisational unit. For a logistics company running fleet tracking and cold-chain monitoring on the same SIM contract, cost-place reporting shows what each use case is actually consuming and costing. For a reseller managing IoT connectivity for multiple end clients, it allows per-client billing without separate contracts.
Weconnect’s connectivity management platform
Weconnect’s platform voor connectiviteitsbeheer provides per-SIM and fleet-level real-time monitoring, usage alerts, data caps, cost-place allocation, and API access. The platform supports independent operation: the customer can activate, suspend, and manage SIMs without involving Weconnect’s support team for routine operations. This matters at scale. A deployment of 10,000 SIMs spread across multiple countries should not require a support ticket to change the data cap on a single device.
IoT SIM buyer checklist: 8 questions before you commit
Before selecting an IoT SIM provider, these eight questions identify the dimensions where providers differ most and where misalignment creates the most operational problems.
1. Does the SIM support permanent roaming in your deployment countries?
Confirm that the provider explicitly permits permanent roaming in the countries where your devices will operate. Get this in writing. Consumer-grade terms that permit roaming for a limited period will result in deactivated SIMs mid-deployment.
2. Is roaming steered or non-steered?
Non-steered is the correct answer for any deployment where network performance matters more than the SIM provider’s carrier economics. Ask specifically whether the SIM has a preferred network list and whether that list can be cleared.
3. Which form factor matches your hardware and environment?
Physical removable SIM for devices with accessible SIM slots and stable environments. eSIM with eUICC for devices requiring remote profile changes or carrier switching. MFF2 ChipSIM for devices in harsh environments where a removable SIM would fail.
4. What network technologies does the SIM support?
Confirm support for the radio access technologies your devices use: 4G LTE, LTE-M (for low-power wide-area IoT), NB-IoT (for sensor networks requiring deep building penetration), 5G, and 2G/3G for legacy devices. Not all IoT SIMs support all technologies on all networks.
5. What security features are included or available?
Private APN, IPsec VPN, IMEI locking, and fixed IP should be available. Confirm which are standard and which are add-ons. If your deployment handles sensitive data or connects to corporate infrastructure, private APN and IMEI locking are non-negotiable.
6. What data plan model matches your consumption profile?
Pay-per-GB for variable or unknown consumption. Unlimited for high-throughput continuous devices. Shared pools for large deployments with variable per-device consumption but predictable fleet totals. Confirm whether there are minimum commitments per SIM and what the overage charges are.
7. Can the management platform scale to your fleet size?
Test the CMP with your expected SIM count before committing. Confirm that bulk operations (activate 500 SIMs, set a data cap on all devices in a cost place) are supported and what the API looks like if you need to integrate management into your own systems.
8. What does the pilot process look like?
A serious IoT SIM provider offers a pilot programme where you can test SIMs in your actual deployment environment before committing to volume. Weconnect provides pilot programmes for IoT SIM validation, allowing you to verify network coverage, test private APN configuration, and confirm performance in your hardware before full deployment.
Veelgestelde vragen
What is the difference between an IoT SIM and a regular SIM card?
A regular SIM card is designed for a device with a human user who manages it directly. It assumes temporary roaming, regular physical access, and consumer-grade environments. An IoT SIM is designed for machines: permanent roaming without deactivation, remote management without physical access, industrial durability for harsh environments, and security features suited to unattended devices handling operational data. The hardware may look identical, but the commercial terms, software, and specifications are built for a different operating model.
What is the difference between an M2M SIM and an IoT SIM?
M2M (machine-to-machine) is the traditional term for connectivity between two devices without human involvement, typically used in industrial applications like fleet management, utility metering, and remote diagnostics. M2M SIM is the broader, more modern term covering all connected devices, from industrial sensors to consumer smart home products. In practice, M2M SIMs are a subset of IoT connectivity. Providers, including Weconnect, use the terms interchangeably and offer the same technical features under both descriptions.
Can a consumer SIM be used for IoT devices?
Technically yes, but operationally problematic. Consumer SIM contracts restrict permanent roaming, typically after 60 to 90 days. They offer no private APN, no fleet management platform, and no industrial SIM form factor. For a single device in a single country with light usage, a consumer SIM may work. For any deployment crossing borders, operating in harsh environments, requiring centralised management, or scaling beyond a handful of devices, consumer SIMs create the exact problems that IoT SIMs are designed to prevent.
What is a Private APN and when do I need one?
A Private APN creates a closed network path from device to your corporate infrastructure. Data from devices on a private APN never touches the public internet. It flows through an encrypted tunnel directly to your data centre firewall. You need a private APN when your devices handle sensitive operational data (SCADA, telemetry, medical, financial), when your security policy requires keeping device traffic off public internet routing, or when you need consistent firewall rules with fixed IP addressing. For deployments with no sensitive data and no security policy requirement, a standard shared APN is sufficient.
How do shared data pools work for IoT deployments?
A shared data pool combines the data allowances of all SIMs in a deployment into a single allocation. Individual SIMs draw from the pool based on their actual consumption. A device that uses more in one month draws more from the pool, a device that is idle contributes nothing. The fleet manager monitors consumption at the pool level, with per-SIM detail available for anomaly detection. Shared pools eliminate per-SIM plan management, reduce the cost of over-provisioning headroom, and simplify budget forecasting.
What is the MFF2 SIM form factor and when should I use it?
MFF2 (Machine Form Factor 2) is an industrial-grade SIM chip soldered directly onto the device’s circuit board. It cannot be removed. It is rated for operating temperatures of -40 degrees Celsius to +105 degrees Celsius, continuous vibration, high humidity, and harsh chemical environments. Use MFF2 when the device will operate in conditions that would damage a removable SIM: outdoor infrastructure, agricultural equipment, heavy machinery, maritime vessels, and industrial automation. If the device design permits, specify MFF2 from the hardware design stage rather than retrofitting later.
Next steps
Choosing the right IoT SIM is a decision that compounds over the lifetime of a deployment. Getting form factor, roaming architecture, security, and data plan right at the start prevents the rework cost of replacing SIMs mid-deployment, renegotiating carrier terms, or rebuilding the security architecture after an incident. Weconnect provides IoT SIM oplossingen across all form factors, with non-steered multi-network access across 700+ carriers in 195 countries, private APN and IPsec VPN as standard security options, shared data pools, and a connectivity management platform built for independent operation at fleet scale. Challenge us with your deployment requirements.
Direct reactie binnen 4 werkuren.