eUICC Profile Lifecycle: Who Controls Your SIM From the Factory Floor to the Scrap Heap
June 3, 2026 · 7 min read · Technical Whitepapers
Your eUICC has an immutable EID burned into silicon. Under SGP.02, whoever controls the SM-SR that holds that EID controls every profile operation for the life of the device. Switching providers means an EID release that some operators refuse.
TL;DR: Deploy 10,000 eUICC devices on SGP.02. The connectivity provider becomes unacceptable. Their SM-SR holds your EIDs and will not release them. Physical SIM replacement on 10,000 devices is the only way out. This is the default state of the SGP.02 installed base.
Stage 1: Manufacturing
Every eUICC ships with a 32-character EID burned into silicon. Permanent. Whoever registers that EID on their SM-SR first controls the device. Under SGP.02, this is the provider, and they own the relationship before the device ships.
Stage 2: Bootstrap
Two paths. Operator-specific bootstrap: device connects only to that platform. Contract ends, device stranded. Neutral bootstrap: platform-independent server redirects to whichever eIM is current. Contract must specify neutral bootstrap with documented exit.
Stage 3: Active Life and EID Lock-In
SGP.02: SM-SR controls profiles. Enterprise requests, provider executes. SGP.32: enterprise eIM orchestrates via API. The lock-in: SGP.02 EIDs cannot be touched by another SM-SR without release. Some providers refuse.
Stage 4: Decommissioning
Documented EID release before signing: timescales, cost per EID, delivery format. No auto-renewal extending custody. Test on 10-50 devices before fleet scale.
Source: eUICC.co.uk, "eUICC SIMs, eSIM Routers and the Specs That Matter", 2026. Available at https://euicc.co.uk/euicc-esim-router-guide-2026/