Upload Native Mode & Rate Plan Changes
The Batch Operations module allows administrators to perform large-scale native mode and rate plan updates using bulk upload workflows.
This is commonly used for:
- SIM activations
- Service suspensions
- Rate plan migrations
- Customer onboarding
- Operational lifecycle changes
[IMAGE PLACEHOLDER: Batch upload overview]
Bulk operational changes can affect large numbers of live devices simultaneously. Always validate upload data carefully before submission.
Supported upload methods
Native mode and rate plan updates can typically be submitted using:
- CSV file uploads
- Clipboard paste operations
[IMAGE PLACEHOLDER: Upload method selection]
Upload a CSV file
To upload a batch operational file:
- Open Batch Operations
- Select Native Mode / Rate Plan Updates
- Choose Upload File
- Select the CSV file
- Review validation results
- Submit the operation
[IMAGE PLACEHOLDER: CSV upload workflow]
Example CSV format
Upload files typically contain:
- Device identifiers
- Target native modes
- Rate plan assignments
Example structure:
#iccid,native_mode,rate_plan
89011702272013815124,Active,Standard Plan
89011702272013815235,Suspended,Low Usage PlanUse consistent naming conventions for rate plans and operational states to reduce validation errors.
Paste updates from clipboard
For smaller operational updates, values can also be pasted directly into the platform.
To use clipboard upload:
- Open the batch operation workflow
- Select Paste from Clipboard
- Paste the dataset
- Validate the data
- Submit the operation
[IMAGE PLACEHOLDER: Clipboard paste workflow]
Validate upload data
Before processing begins, the platform validates:
- Device identifiers
- Supported operational states
- Rate plan availability
- File structure
- Provider compatibility
Validation errors are displayed before execution.
[IMAGE PLACEHOLDER: Validation results]
Advanced settings
Some workflows may include advanced operational settings such as:
- Scheduled execution
- Provider-specific controls
- Synchronisation handling
- Retry behaviour
[IMAGE PLACEHOLDER: Advanced batch settings]
Available advanced options depend on provider capabilities and account permissions.
Monitor processing status
After submission:
- The operation is queued for processing
- Provider synchronisation begins
- Job progress becomes visible in Batch Operations
[IMAGE PLACEHOLDER: Processing status]
Common operational scenarios
Typical workflows include:
- Activating newly deployed SIMs
- Suspending inactive devices
- Migrating customers between rate plans
- Updating operational states during migrations
- Managing staged deployment rollouts
Some provider platforms may apply operational or billing changes immediately after processing begins.