What are the hardware specifications of Onomondo eSIMs (MFF2)?

Onomondo's public pricing page (source [6]) lists IoT data plans and SIM pricing but does not detail specific hardware specs beyond the MFF2 form factor. For exact technical specifications, request a project quote.

Can I transfer SIMs to a new operator post-deployment?

With eSIM and SGP.32, you can switch profiles remotely via the eIM, as described in source [1]. Physical SIMs require replacement. M2M eSIM used a push model, while SGP.32 enables a pull model for remote switching.

Do I pay for activated SIMs when they are not in use?

Based on published carrier rate cards, most IoT data plans charge per active SIM per month, but some offer suspend or archive modes with reduced fees. Check your CMP platform's billing policies; for example, Spenza's CMP unifies connectivity orchestration and cost control (source [8]).

Do you offer a public API and webhooks?

Many CMP platforms offer RESTful M2M APIs and webhooks for provisioning and monitoring. According to source [8], Spenza's CMP provides APIs and automation. Onomondo's pricing page (source [6]) does not list API details; request a project quote for API documentation.

Do I have real-time insights in every country?

Real-time insights depend on carrier network visibility and CMP platform capabilities. Source [3] notes that interoperability issues have hindered eSIM adoption. For multi-country deployments, ensure your CMP platform supports real-time data usage across all target countries. This often requires a project quote for custom reporting.

oneM2M IoT SIM Procurement: $1.8B eSIM Market by 2029, Certification Bottleneck

September 20, 2026 · 5 min read · Technical Whitepapers

oneM2M standardizes IoT service layer, but eSIM IoT SGP.32 changes SIM/CMP procurement. $1.8B market by 2029; eSIM certification is the timeline bottleneck.

oneM2M is a global standard for an M2M/IoT service layer, providing a common architecture for interoperability across devices and platforms. For a 10,000-device multi-country deployment, the eSIM IoT specification (SGP.32) market is projected to reach $1.8 billion by 2029 (source [4]), yet procurement managers note that eSIM profile certification—not hardware—is the timeline bottleneck.

WHY IT MATTERS

The procurement constraint shifted in 2023 when GSMA published SGP.32, the eSIM IoT specification, replacing the 2013 M2M specification (SGP.02) that failed to enable widescale adoption (source [4]). SGP.32 introduces a pull model with an eSIM Remote Manager (eIM) and IoT Profile Assistant (IPA), moving away from the push model of M2M (source [1]). This changes contract types: instead of locking into a single carrier's M2M eSIM platform, procurement can now specify an eIM that manages profiles from multiple carriers, enabling eSIM profile switching for IoT without physical SIM swaps.

TYPICAL APPLICATIONS

Fleet Telematics

For a 5,000-vehicle fleet tracking deployment, eSIM with SGP.32 allows remote profile switching across borders. Use a global IoT SIM with multi-carrier profiles and a CMP platform that supports eIM integration. Catalog pricing works if you use pre-certified profiles from a single provider; otherwise request a project quote.

Smart Metering

Smart meter cellular connectivity for 100,000 units often uses NB-IoT SIM or LTE-M SIM. oneM2M service layer standardizes data models, but SIM procurement must decide between eSIM (embedded SIM) and physical industrial SIM. eUICC SIM with SGP.32 enables remote provisioning, reducing truck rolls. API integration with CMP is essential for bulk activation.

Asset Tracking

eSIM for asset tracking across 20+ countries benefits from SGP.32's expanded application layer protocols beyond SMS and HTTPS (source [2]). A RESTful M2M API from your CMP platform lets you automate eSIM profile switching. Catalog pricing for IoT data plans is viable for standard 50 MB/month per device; custom multi-IMSI configuration requires a project quote.

TECHNICAL SPECIFICATION / COMPARISON TABLE

Specification	Year Published	Architecture	Remote Manager	Profile Delivery Protocols
M2M (SGP.02)	2013	Push model	SM-SR	SMS, HTTPS
Consumer (SGP.22)	2016	Pull model	SM-DP+	HTTPS
IoT (SGP.31/32)	2023	Pull model with eIM	eIM + IPA (IPAd/IPAe)	Expanded beyond SMS/HTTPS
oneM2M	Ongoing	Service layer	N/A (not RSP)	N/A

Sources: [1][2][3][4]

SELECTION NOTES

When deploying in a single country with standard data plans and pre-certified eSIM profiles, catalog pricing is sufficient. For example, Onomondo publishes IoT data plans and SIM pricing (source [6]). When your deployment spans 3+ countries with multi-carrier requirements, or you need custom eIM integration and bulk SIM activation for enterprise IoT, a project quote is required. If you require an API for real-time provisioning, choose a CMP platform that offers RESTful M2M endpoints without extra licensing fees.

COST MODEL / TCO

Hardware Costs

eUICC SIM hardware typically ranges from $2 to $5 per unit based on published carrier rate cards. Industrial SIM form factors (MFF2) may cost $1 to $2 more. For 10,000 devices, hardware totals $20,000 to $50,000.

Connectivity Costs

IoT data plans typically range from $1 to $3 per device per month for 50 MB, based on published carrier rate cards. Multi-carrier eSIM profiles may add 10-20% to base connectivity. Over 3 years, connectivity for 10,000 devices is $360,000 to $1,080,000.

Platform and Integration

CMP platform fees are typically $0.50 to $2 per device per month. For 10,000 devices over 3 years, that is $180,000 to $720,000. API access is often included in enterprise tiers.

Installation and Maintenance

Installation labor for eSIM provisioning is $5 to $10 per device, totaling $50,000 to $100,000. Maintenance is 10-20% of hardware annually, or $2,000 to $10,000 per year.

Payback

Switching from roaming to local eSIM profiles can reduce data costs by 30-50% based on published carrier rate cards. For a 10,000-device fleet spending $50,000 per month on roaming, savings of $15,000 to $25,000 per month pay back the CMP platform and eSIM hardware in 3 to 6 months.

PROCUREMENT REALITY CHECK

Procurement managers note that eSIM profile certification is the timeline bottleneck, not hardware. In a typical multi-country rollout, eUICC modules can be sourced in weeks, but each carrier's eSIM profile certification can take months. So, start certification before finalizing hardware orders. This also means that vendor selection should prioritize carriers with existing SGP.32 certifications. For a 10,000-device deployment across 5 countries, plan for 6 to 12 months for certification alone.

FROM THE FIELD

Deployment teams report that eSIM profile certification is the timeline bottleneck, not hardware. For deployments above 100 devices, this means starting carrier certification at least one quarter (3 months) before planned hardware installation. Procurement managers note that early engagement with carriers and CMP vendors on certification steps is critical.

CATALOG PRICING VS PROJECT QUOTE

When is catalog pricing enough? If you need fewer than 1,000 devices, operate in one country, use standard data plans, and accept pre-certified eSIM profiles from a single provider, catalog pricing (e.g., Onomondo's published plans) works. When must this go to project quote? If you deploy more than 1,000 devices across 2+ countries, require multi-carrier eSIM profile switching, need custom CMP API integration, or demand bulk SIM activation with negotiated volume discounts, request a project quote. Based on publicly available data, project quotes typically offer 15-30% lower per-device costs at volumes above 5,000 units.