Topic starter
14/07/2026 4:26 pm
TL;DR: eSIM adoption is accelerating toward billions of devices, according to Workz Group, but telcos now face profile lifecycle, delegation, and inventory control gaps that manual provisioning cannot absorb at IoT scale. The core risk is governance drift across distributed channels, where profile assignment and ownership must become policy-driven rather than operator-led.
Editorial analysis by NHI Mgmt Group, based on content published by Workz Group: “How telcos can implement eSIM IoT”.
By the numbers:
- More than six billion eSIM-capable devices will be shipped between 2024 and 2028, according to Workz Group.
- Global IoT eSIM connections are expected to rise from 165 million in 2024 to nearly 1.3 billion in 2028, according to Workz Group.
- Seven out of every 10 cellular devices shipped in 2030 will have eSIM, according to Workz Group.
Key questions
Q: What breaks when eSIM profile management is still handled manually at IoT scale?
A: Manual profile handling breaks when device volume, device diversity, and channel count rise faster than operators can match profiles, track inventory, and update lifecycle state.
Q: Why do delegated eSIM channels create governance risk?
A: Delegated channels create risk when partners can provision widely without clear scope, logging, and revocation.
Q: How should telcos prioritise bulk orchestration versus channel expansion?
A: Telcos should prioritise orchestration first when channel growth increases the number of profiles, hand-offs, and inventory decisions.
Practitioner guidance
- Map every provisioning role and delegation path Document which telco, OEM, enterprise, enabler, or aggregator can request, approve, issue, update, and retire eSIM profiles, then remove any unowned path that lacks a revocation authority.
- Automate profile selection by device capability Tie profile issuance to real-time device attributes such as capability, region, and network requirements so that manual profile matching does not become the bottleneck.
- Build inventory monitoring into the control plane Track profile stock in real time across all channels and define alerting thresholds before stockouts affect customer fulfilment or activation latency.
Bottom line: eSIM IoT scale turns profile issuance and retirement into a governance problem, not just a delivery problem.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
14/07/2026 4:33 pm
Profile lifecycle is now a governance control, not an operations detail. The article shows that eSIM growth turns provisioning into an identity-like lifecycle problem because each profile must be issued, updated, delegated, and retired with policy precision. Traditional manual fulfilment cannot sustain that model once channels, device types, and geographies multiply. Practitioners should treat lifecycle orchestration as part of access governance, not back-office logistics.
A question worth separating out:
Q: What should organisations do when multiple distributors share eSIM management responsibilities?
A: They should define one accountable control plane, require consistent lifecycle state across every distributor, and verify that revocation reaches all downstream systems. Shared responsibility only works when roles, scope, and auditability are explicit enough to prevent duplicate or stale provisioning actions.
👉 Read our full editorial: eSIM IoT scale exposes telco profile lifecycle and delegation gaps