Definition
Decommissioning (Recycling Termination) refers to the process of transitioning a SIM card or eSIM from active status to terminated status (EOL, End of Life), including resource release, operator-side deregistration, data archiving, and cleaning. It works in conjunction with GDPR data retention policies and Audit Trail auditing to meet compliance, asset inventory, and cost management requirements.
Process and Steps
Typical Decommissioning steps include: the customer initiates a deactivation request or the platform automatically triggers it based on policy; a deregistration request is sent to the operator to release the subscription in HLR/HSS; the platform updates the card status to Decommissioned and stops billing; related data is handled according to GDPR and internal policies—records needed for auditing are retained, and personal data is deleted or anonymized; physical cards can be returned to the card pool or scrapped, and eSIM profiles are deleted from the device. The process needs to be recorded in Audit Trail to facilitate traceability.
Relationship with lifecycle
Decommissioning is the final stage of the Card Lifecycle. Prior to this, it may go through Activation and Suspension. Suspension can be reversed, whereas Decommissioning is usually irreversible (unless the card pool is reclaimed and reassigned). The platform needs to clearly define the boundary between suspension and termination to avoid operational errors that could lead to resource waste or compliance risks.
Compliance and Data Retention
GDPR requires that data retention has a clear purpose and time limit; data must be deleted or anonymized after the deadline. After Decommissioning, the platform needs to retain data necessary for auditing, reconciliation, and dispute handling for a certain period, while other sensitive data must be promptly cleared. In cross-border scenarios, data clearing must comply with regulations in each region, and Audit Trail must record the clearing operations.
Whether termination releases the subscription or the inventory
Termination has to separate two things. The subscription is the registration that lets this SIM attach on the operator side. After termination, the core network no longer accepts it, and the number and subscriber identity enter recycling or a quarantine hold. Inventory is the plastic SIM, the embedded chip, and the profile held by the customer or the platform. A successful subscription cancellation can leave the chip still in the device. A plastic SIM back in the warehouse does not mean the operator side has released it. Both have to be finished before the connection has left the books and the network together.
Deleting a profile affects only the credentials on the chip. It does not mean the subscription in the home register has been cleared. If only the profile is deleted, the network may still believe the subscriber exists, and the monthly fee continues. If only the subscription is cancelled and the chip is left alone, the device keeps trying to attach with credentials that no longer work. The termination record should write both the network-side receipt and where inventory went: scrapped, returned to stock, or left in the device pending physical recovery.
What must be settled before a final state
Before an irreversible final state, unbilled usage must be collected or explicitly moved to an adjustment account, open orders must be closed, and channel commission must be reversed or kept according to the rules. On the data side, the parts of detail records and audit logs that must be kept are archived for their purpose and period. Personal data that is no longer needed is deleted or de-identified. Retention and deletion have to be written separately. “Termination” is not a reason to wipe every record at once, or a billing dispute still in progress loses its basis. “We might need to look it up” is not a reason to keep all personal data without a time limit.
The permission required should be higher than for an ordinary suspension. Bulk termination needs a confirmed list and a replayable failure list. SIMs that fail keep their previous state. A batch timeout must not mark the whole batch terminated. For a cross-border SIM, confirm that the visited-network session has been released. Otherwise, after local cancellation, the visited network can still send late detail records. The line with suspension is this: suspension keeps the subscription, termination releases it. If it is unclear whether the device will return to the site, suspend first. When a trace is required, what goes into the audit trail is the termination request and the operator receipt, not only a status word changed in a spreadsheet.
Turning a recoverable suspension into an irreversible cancellation
Field maintenance, non-payment, or seasonal shutdown needs only a suspension. If a support menu maps “disable” straight to termination, the SIM is cancelled on the operator side. Restoring it means issuing a new subscriber identity. Configuration in the device, historical links on the platform, and an unfinished billing period all break. An embedded SIM is worse. After the profile is deleted, nobody on site can insert a card. The device has to go through remote provisioning again, and remote provisioning depends on a bootstrap profile that can still communicate. If the bootstrap profile was deleted as well, the device can only go back to the factory.
Another error is inventory recovered while the subscription is not cancelled. The SIM is fitted to the next device and still tied to the previous customer’s rate and data. Or the subscription is cancelled while inventory still says in service, and monitoring keeps alerting that this SIM is offline. After a number is reassigned at the end of quarantine, old detail records and the new customer’s usage can land in the same query because the number matches. Queries after termination should filter on the SIM’s unique identifier and the termination time, not on the number alone. If a termination was a mistake, stop assigning that same identifier to a new customer immediately, then ask the operator whether it is still inside a recoverable window. If the window has passed, treat it as a new subscription, and keep an archive index of the old record.
Do not release numbers and subscriber identities still in quarantine to a new order early. Old detail records may still arrive under those identifiers, and the new customer’s usage mixes with the old customer’s late records in one query. Allocate again only after quarantine ends, and use the termination time in queries to cut the two lifecycles apart. Before a plastic SIM returns to stock, confirm that the network-side receipt has succeeded. A warehouse scan with no receipt means the SIM can be issued again and keep generating charges. If an embedded device cannot delete the profile remotely, the termination list should say physical recovery is required. Inventory status must not be flipped straight to available for resale.