Definition
Activation validity is the number of days an IoT SIM has to complete activation after it is stocked. A SIM that misses the date can be reclaimed automatically or flagged as an exception, so it does not sit in inventory and keep holding resources. The IoT Cloud Platform stores this policy. It is used when SIMs are issued in bulk and for pre-installed SIMs.
What the window is for
- Stock turnover: Stop SIMs from staying unactivated, free the inventory, and move the SIM pool faster.
- Exception tracing: An overdue unactivated SIM can be flagged so operations can follow the channel or the project that still holds it.
- Reclaim: Overdue SIMs can return automatically to the available pool for another project, which limits the cost of idle stock.
- Operator quota: Some SIM products must be activated inside the period the operator requires, or the resource quota is affected.
Typical day counts
The window is set in days. Common values are 30, 90, 180, and 365 days. The platform can use a different count by SIM product, by project, and by operator. The clock starts when the SIM is first entered on the platform or when it is assigned to a channel. If it is still unactivated when the window ends, the platform can reclaim it or mark it “overdue and unactivated.”
How it sits next to first activation time
First activation time decides when billing starts after the SIM is activated. Activation validity decides the latest date the SIM must be activated after it enters stock. One controls when activation has to happen. The other controls when charges start once it has. A SIM can be required to activate within 90 days of stocking, and at activation the choice can be “bill immediately” or “bill on the 1st of the next month.” Those are two different first-activation-time rules.
Where it is used
It fits bulk issue to an agent, a distributor, or a project, when the channel has to sell and activate inside an agreed period. It also fits plug-and-play SIMs and pre-installed SIMs: the SIM is already in the device when it leaves the factory, and activation still has to happen within a set period after the device is sold. The enterprise sets the window on the platform and runs it with card lifecycle so stock and operator resources stay under control.
What to configure
Set the day count on the SIM product or on the project, and decide what happens when it expires: reclaim the SIM, or only flag it. The platform can list overdue unactivated SIMs and report them, so operations can chase the channel or the project. Used with resource allocation, a SIM assigned to a channel and left unactivated past the date can return to the available pool for another channel or project.
Which timestamp starts the countdown
Activation validity is a cutoff that begins at a chosen timestamp and advances by calendar day or by whole day. It is not a decorative day count parked on the product. The start event has to be named as one of three: the number range entering stock, assignment to a project or channel, or the physical goods leaving the warehouse. If the contract says the SIM must be opened within a set number of days after arrival, but the platform counts from an earlier stock-in time, the channel is judged overdue before the goods are even in hand. The setting should also keep a time zone. Domestic SIMs should cut the day at midnight in the agreed Beijing time, not in the application server’s default zone, or one batch stocked across midnight will come out a day apart. At acceptance, take one unactivated SIM and place the stock-in log, the assignment log, and the expiry date shown on the page next to each other. If the three do not match, change the start event before making the day count longer. A SIM that has already attached during a factory or warehouse test also needs a check that the test did not write the status as activated. If it did, the validity job treats the SIM as already finished and skips it.
Reclaim the numbers, or only flag them
The action after expiry should be two policies that cannot both run. Reclaiming the number range detaches the SIM from the channel or project stock and returns it to the enterprise pool that can be assigned again. The old sales attribution should lapse with it, or the next activation will still book the order to the previous channel. Only stamping “overdue and unactivated” leaves the SIM under the original owner, and the activation interface must refuse it. That path is for chasing responsibility and for stocktaking, not for putting the SIM back into circulation. Whether either action is allowed depends on four conditions together: the SIM is still unactivated, it has no usage record, it is not bound to an end user, and there is no unfinished purchase order. A SIM that already has a formal usage record cannot go through unactivated reclaim, or an in-service SIM is pulled out of the project and the bill no longer matches the resource on the operator side. Both reclaim and flagging should record who did it, why, and the previous owner, so the result can later be checked against resources the operator has not opened. SimtoLink batch activation keeps the validity days and the overdue action on the project policy, stored apart from “when billing starts after activation,” so one switch does not rewrite both the stock deadline and the plan start.
Built into a device, the deadline and the bill stay apart
When the SIM is already fitted into a module before the device leaves the factory, warehouse time and shipping consume the activation window, but that wait should not start plan charges early. Validity only answers the latest day by which activation must be finished. First-use start answers which session, after activation, begins to draw down the plan. A preinstall project usually sets the window long enough to cover production, distribution, and installation, and leaves the billing start at the first real attach. The usual miss is a production-line test that registers on the network. The platform then records that test as activation, or as first use, so the SIM is treated as expired before it ships, or the monthly bundle has already run for several days. Test ranges should be marked on their own, and test records should not be written as a formal activation event. If devices sit for a long time in a dealer warehouse while the window counts from the factory stock-in date, expiry reclaim takes back a SIM that is already soldered into hardware, and the installer finds the number unusable. Those projects should move the start event to “device sold” or “channel signed for,” and, before reclaim, check again whether the SIM is already bound to the hardware.