You manage 3000 IoT SIMs and pay monthly for 800 that haven't sold. The boss asks 'can we only activate shipped ones?' Yes — if you swap manual provisioning for a lifecycle API.
A SIM has six states in its life
Inventory -> Test -> Active -> Suspended -> Reactivated -> Deactivated. Most firms are stuck at 'all active or none', so unsold devices bill anyway.
Three automation touchpoints
- Activate to shipment: device off the line scans -> calls carrier activation API -> card starts billing; sell one, open one.
- Suspend/reactivate on events: device offline past threshold auto-suspends to save fees; reconnect auto-reactivates, no manual ticket.
- Isolate test phase: pre-shipment uses a test profile outside the billing pool to avoid mistaken charges.
Two things to watch when integrating
- API must support batch + status callbacks, not just your polling.
- Activation/suspension needs an SLA (minutes); breaches hit business, put it in the contract.
A SIM's monthly fee isn't paid 'when you buy it' but 'starts the moment it's activated' — control the state and you control the cost.
FAQ
What's the difference between定向 and full-roam data SIMs?
定向 SIMs are limited to a designated APN/app and are cheap; full-roam SIMs use public networks—wider coverage but costlier.
How is IoT SIM real-name verification done in Vietnam?
Vietnamese carriers require business/personal verification; bulk devices are managed via a CMP platform.
How do you manage the M2M SIM lifecycle?
Covers activate/suspend/deactivate/recover; use a CMP console to monitor traffic and status remotely.
Should I pick 4G or 5G SIM?
Depends on device and coverage; most CPE/pocket WiFi use stable 4G, 5G when coverage exists and high speed is needed.