1. Scenario overview
Batch activation is activation done in bulk, for a project rollout or a channel purchase that turns on hundreds to tens of thousands of IoT SIMs at once. Single-SIM activation works one SIM at a time. Here you import ICCID, data plan, and project or customer from Excel or CSV, then activate, assign the plan, and bind ownership together. Progress and results update as the job runs. Failed rows can be exported and retried.
The platform talks to the operators and fans the batch out so several operators can process it at once. An async queue runs the job, so a ten-thousand-SIM batch does not lock the screen. It pairs with SIM activation: activation defines the flow and the policy, and batch activation is how you run it in volume.
2. Core capabilities
Batch import
Download the Excel or CSV template, fill ICCID, plan ID, and project or customer, then upload. The system checks format and values. The template can add fields such as device number and notes. Preview the file, then submit.
Batch activation
After the check passes, pick when it takes effect — now, or a set time — and run it. The platform sends activation to the operators by batch, and several operators can run at once. Keep a batch at or under 5,000 SIMs. Split anything larger.
Async run and progress
Large jobs use an async queue and do not lock the screen. After you submit, open Batch tasks to see success, failure, and in progress. Task status and progress are stored.
Failure trace and retry
Export the failed SIM numbers and the reason. Typical reasons: the SIM number does not exist, it is already active, the plan is invalid, or the operator side failed. Retry the failed SIMs on their own, or fix the file and import it again.
3. How a job runs
4. Batch activation and single-SIM activation
The two modes fit different jobs. The differences:
| Dimension | Batch activation | Single-SIM activation |
|---|---|---|
| How you work | Excel or CSV, hundreds to tens of thousands at once | One SIM at a time |
| Where it fits | Project rollout, channel purchasing, migration and replacement | Scattered activation, replacing one SIM |
| How it runs | Async queue, the screen stays usable | Synchronous |
| Progress | Live counts of success, failure, and in progress | Immediate result for that SIM |
| When it fails | Export the failed rows and retry the batch | Retry that one SIM |
5. Where teams use it
- Project rollout: Connected vehicles, shared devices, and industrial IoT often activate hundreds or thousands of SIMs at once. Import ICCID and plan, and let the job run asynchronously.
- Channel batch activation: Agents and distributors buy and activate in batches, managed by batch so the purchase can be traced and reconciled.
- Migration and replacement: A project move uses a large batch. A replacement uses a small import, and the new SIM is online quickly.
6. What changes in daily operations
Batch activation is how a project goes live faster. Ten-thousand scale covers a large rollout. Async keeps the screen usable. Progress is traceable, with success and failure counted as the job runs. Failures can be retried, and the export is what you use to fix them. Together with SIM activation and SIM management, activation is covered end to end. Single-SIM activation works one SIM at a time. A batch imports hundreds or thousands at once and runs without locking the screen.
7. How to put it in place
Activate by project or by batch, and check ICCID, plan, and project or customer before you submit. Split a large job. Keep a single batch at or under 5,000 SIMs. Review failed rows promptly, fix them, and retry. The import template can add fields such as device number and notes. The async run leaves the screen free, and progress is shown as it happens. An import template and operating guidance are available.