Key points
- Provisioning is one stage, not the entire lifecycle.
- Business, platform and network states must be reconciled.
- Actions and permissions differ across eSIM, physical SIM and IoT.
- Visibility and audit trails are essential for support and scale.
Before activation
The platform manages product eligibility, profile or SIM inventory, assignment rules and the relationship between the order and connectivity asset. Physical SIM may be pre-assigned or activated later. Consumer eSIM commonly requires secure delivery of profile activation information.
Clear reservation and expiry rules prevent the same asset from being sold twice or left unusable after a failed checkout.
Provisioning and installation
For eSIM, the provisioning ecosystem securely downloads a profile to the device under the GSMA architecture. The customer may use a QR code, activation details or supported in-app flows. Installation and network activation are related but not identical events.
For physical SIM, provisioning may include profile configuration, packaging and assignment of serial identifiers before delivery.
Active service management
Once active, teams need status, usage, plan validity, network and top-up information. Customer-facing data should be understandable, while operational data should preserve detailed identifiers and event history.
Threshold alerts, automatic renewal and balance rules can reduce interruptions. The platform should show when usage data is delayed so customers are not given false precision.
Suspension, replacement and termination
Consumer, enterprise and IoT use cases require different permissions. A lost device may require suspension. An IoT fleet may automate status changes. Replacement or profile re-download may be limited by product rules and security policy.
Every action should be authorized, logged and reflected in support tools. Termination should address remaining balances, customer data and any required retention period.
Why lifecycle visibility matters
Without one lifecycle view, commerce may show a paid order while the network shows an uninstalled profile. Support then cannot explain the customer's problem. Good platforms reconcile these layers, expose clear states and give teams safe actions.
The same principle supports eSIM, physical SIM and IoT, even though the exact provisioning architecture and policies differ.
Questions, answered
Is an eSIM active immediately after purchase?
Not always. The profile may first be issued, then downloaded and installed, and the plan may activate on installation, first network use or a defined date depending on product rules.
Can a deleted eSIM always be reinstalled?
No. Re-download rules vary by profile and provider. Customers should be warned before deletion and support should see the applicable policy.
What should support agents see?
Order, payment, profile or SIM identifier, delivery, installation, network status, plan validity, usage, top-ups and event history should be connected in one view.