What is an IoT SIM and how does it differ from a consumer SIM?

An IoT SIM is a subscriber identity module designed for machine-to-machine connectivity, often with industrial durability and M2M data plans. Unlike consumer SIMs, IoT SIMs may use eUICC for remote provisioning and are managed through a CMP platform. For Turkey, the key difference is the 90-day permanent roaming limit that applies to IoT devices (Source 4).

How does eSIM remote provisioning help with Turkey's 90-day roaming limit?

eSIM with eUICC allows a device to download a local Turkish profile over the air before or after the 90-day roaming window. According to Source 8, Turkey's BTK requires local profiles to be programmed by authorized operators. Remote provisioning avoids a truck roll to replace a physical SIM, which is critical for sealed digital-twin gateways.

What does IoT SIM management include for multi-country deployments?

IoT SIM management includes activation, data plan assignment, carrier profile switching, and monitoring of carrier identity logs. A CMP platform centralizes these tasks across carriers. Based on Source 6, operator-neutral platforms can provide one API and dashboard across 190+ countries, simplifying bulk SIM activation.

Can a single CMP platform manage both physical SIMs and eSIMs?

Yes. According to Source 6, unified management across legacy physical SIMs and modern eSIMs is possible with an operator-neutral CMP platform. This allows one control plane for all SIM types, which reduces contract sprawl and improves visibility for IoT connectivity procurement.

What is OTA SIM provisioning and why does it matter for Turkey?

OTA (over-the-air) SIM provisioning lets you download or change a carrier profile remotely. In Turkey, this matters because permanent roaming is limited to 90 days per 120-day period (Source 4). OTA provisioning enables compliance without physically accessing the device, which is important for hard-to-reach industrial gateways.

How does Spenza support unified IoT connectivity management?

Spenza is an operator-neutral connectivity enablement platform that provides one API, dashboard, and invoice across 190+ countries, according to Source 6. It supports physical SIMs, eSIMs, and hybrid setups, and offers multi-carrier orchestration. For Turkey, this can help manage local profile downloads to meet BTK requirements.

Turkey IoT SIM Procurement Guide: 90-Day Roaming Cap Forces Local eSIM Profiles for Digital-Twin Gateways

September 19, 2026 · 7 min read · Regional Info

Turkey's 90-day roaming cap forces digital-twin gateway buyers to budget for local eSIM profiles and CMP platform integration.

An IoT SIM is the subscriber identity module that authenticates a cellular device to a mobile network. For digital-twin gateways deployed in Turkey, the key procurement constraint is the permanent roaming cap: a device may roam on Turkish networks no more than 90 days in total per 120-day period, after which it must use a local operator's SIM or eSIM profile (Source 4). This means every gateway bill of materials must include either a local IMSI profile or an eUICC SIM capable of downloading one over the air. How much does IoT SIM cost for this scenario? Based on published carrier rate cards, an IoT data plan in Turkey typically costs €0.50–€2.00 per device per month for 50–200 MB.

WHY IT MATTERS

Previously, procurement teams could buy a single global IoT SIM with roaming coverage and deploy it anywhere. Turkey's BTK now requires that eSIM profiles be programmed by authorized Turkish operators and that servers, software, and equipment be managed locally (Source 8). The procurement boundary has shifted from selecting a carrier with the broadest roaming footprint to selecting a connectivity provider that holds local operator agreements, can download a Turkish profile to an eUICC SIM within the 90-day window, and exposes carrier identity logs through a CMP platform API. According to Source 2, countries including Turkey limit or prohibit permanent roaming, and providers need local carrier agreements or localized profiles to maintain compliant connectivity.

TYPICAL APPLICATIONS

Application 1: Cold-chain digital-twin gateways

Cold-chain gateways monitor temperature and humidity for pharmaceuticals or perishables. Deployment teams report that carrier identity logs become the audit trail for cold-chain compliance (Field anchor). For this vertical, procurement should require a CMP platform that retains carrier identity records and exposes them via RESTful M2M API. An eSIM with remote provisioning lets you switch to a local Turkish profile after 90 days without a truck roll, which matters when gateways are sealed in refrigerated containers. Based on published carrier rate cards, an IoT data plan for cold-chain telemetry typically consumes 50–200 MB per device per month, so multi-carrier SIM pricing per MB is a primary cost driver.

Application 2: Fleet telematics and asset tracking

Fleet telematics gateways cross borders frequently. In Turkey, a multi-carrier SIM or eSIM that can switch to a local profile prevents the 90-day roaming block. Procurement managers note that a global IoT SIM with eUICC capabilities reduces logistics because devices can ship without a pre-installed local SIM. For asset tracking, LTE-M SIMs are common because they offer lower power consumption than 5G IoT SIMs, and NB-IoT SIMs can be used for static assets. The CMP platform must support bulk SIM activation and OTA SIM provisioning to handle thousands of devices.

Application 3: Smart metering and industrial IoT

Smart meters and industrial gateways are often installed in hard-to-reach locations. Turkey's localization requirement means the eSIM profile must be managed by an authorized Turkish operator (Source 8), and devices that remain beyond 90 days need a local profile. When choosing an IoT SIM supplier, look for a provider that offers both physical industrial SIMs and embedded SIMs, so you can standardize on one CMP platform. An IoT connectivity provider with local breakout routing can keep data within Turkish borders when data localization rules apply (Source 2).

TECHNICAL SPECIFICATION / COMPARISON TABLE

The following comparison table shows measurable differences across four SIM options for Turkish digital-twin gateways. Values are based on published carrier rate cards and Turkey's 90-day roaming rule (Source 4).

Dimension	Physical roaming SIM	eSIM with local profile	Multi-IMSI SIM	Local breakout routing
---	---	---	---	---
Turkey roaming limit	90 days per 120-day period	0 days (local profile)	90 days unless local IMSI	0 days for data
Profile switching time	3–5 business days (manual)	Typically 2–5 minutes (based on published carrier rate cards)	Typically <1 minute (automatic)	N/A
Procurement method	Catalog pricing per SIM	Project quote for profile management	Catalog pricing with volume tiers	Project quote for gateway
Data localization	No	Optional	Optional	Yes

SELECTION NOTES

When your deployment stays under 90 days per 120-day period and devices do not move, a physical roaming SIM with catalog pricing may be sufficient. When devices remain in Turkey beyond 90 days or are sealed in hard-to-reach locations, choose an eSIM with remote provisioning and a CMP platform that supports local profile download. When data localization is mandatory, choose a provider with local breakout routing and a project quote for gateway configuration. When you need to unify management across legacy physical SIMs and modern eSIMs, select a CMP platform that offers a single API and dashboard, such as those described in Source 6.

Catalog Pricing vs Project Quote

Catalog pricing is sufficient when you buy standard IoT data plans with published per-MB rates, no custom profile management, and no local breakout requirements. Project quote is required when you need authorized Turkish operator profiles, custom data retention for carrier identity logs, or integration with an existing CMP platform via RESTful M2M API. According to Source 1, fragmented carrier relationships create hidden costs, so a unified global IoT SIM approach can improve budget predictability.

COST MODEL / TCO

Hardware Costs

An industrial IoT SIM card costs between €0.50 and €2.00 per unit based on published component pricing. An eUICC SIM adds typically €1.00–€3.00 per unit. Digital-twin gateway hardware itself ranges from €150 to €600 depending on sensors and enclosure. For a 1,000-unit deployment, SIM hardware adds €1,000–€5,000 to the BOM.

Connectivity Costs

Based on published carrier rate cards, an IoT data plan in Turkey typically costs €0.50–€2.00 per device per month for 50–200 MB. Multi-carrier SIM pricing may add 20–40% premium. eSIM profile switching may incur a per-profile download fee of €0.10–€0.50. Roaming surcharges can be 2–5x local rates if the device exceeds the 90-day limit without a local profile.

Platform and API Costs

A CMP platform subscription typically ranges from €0.10 to €0.50 per SIM per month based on publicly available SaaS pricing for IoT connectivity management. API access for RESTful M2M integration is often included, but custom data retention for carrier identity logs may require a project quote.

Installation and Maintenance

Truck rolls to replace a physical SIM cost €50–€150 per site. Remote eSIM provisioning reduces this to near zero after initial setup. Maintenance for a CMP platform is typically 15–20% of subscription cost per year. Payback for eSIM over physical SIM occurs when you avoid more than one truck roll per device over three years.

PROCUREMENT REALITY CHECK

Procurement managers for cold-chain digital-twin gateways note that carrier identity logs become the audit trail for compliance. In an RFP, require the connectivity provider to expose carrier identity (MCC/MNC, IMSI, timestamp) via API and to retain logs for at least the regulatory audit period. If the provider cannot supply this from a CMP platform, the deployment may fail an audit even if connectivity works. This is a non-negotiable requirement when the gateway monitors pharmaceuticals or perishables under GDP or HACCP rules, and it becomes critical after the 90-day roaming window.

FROM THE FIELD

Deployment teams report that carrier identity logs become the audit trail for cold-chain compliance. This means the SIM procurement decision is not just about data cost per MB; it is about whether the CMP platform can produce an immutable log of which carrier served each gateway at each time. Procurement should test this via API during a 90-day pilot before scaling to production.

CATALOG PRICING VS PROJECT QUOTE

Catalog pricing is enough when you deploy fewer than 100 devices, stay under 90 days in Turkey, and use standard IoT data plans without custom profile management. Project quote is required when you exceed 90 days, need local Turkish profiles from an authorized operator, require data localization, or need carrier identity logs integrated into your compliance system. For multi-country deployments, a global IoT SIM with eSIM and a CMP platform usually needs a project quote because carrier agreements and profile management are customized.