1. Scenario overview
A plan change replaces the current plan on an activated SIM. It is not suspend and resume, which turns the network on or off, and it is not plan subscription, which is a new purchase. When data runs short, a user can move up a monthly or quarterly tier, move down to cut cost, or switch into a shared data pool. SimtoLink handles one SIM or a batch, and the three types — upgrade, downgrade, and switch — can take effect immediately or from the next month.
The target is your own plan after plan packaging. In a B2B2C setup, end customers can upgrade themselves, tied to plan subscription and payment. The change syncs to the operator so the platform and the operator show the same plan status.
2. Core capabilities
Upgrade, downgrade, and switch
Upgrade moves a lower tier to a higher one, for example a 1GB monthly plan to a 5GB monthly plan. It usually takes effect at once, the new allowance is available immediately, and you can charge the difference or prorate. Downgrade moves a higher tier to a lower one and is often set for the next month, so leftover data in the current cycle can still be used. Switch moves between plans at the same tier, or from a single-SIM plan to a shared pool. Leftover data and the billing cycle both matter.
When the change takes effect
Take effect now, next month, or on a chosen date. Upgrades are usually immediate. Downgrades usually wait until next month. You can require a confirmation before the change and send a notice after it, so a mis-click does not go through. Leftover data is configurable: an upgrade can apply at once, and a next-month downgrade can keep the rest of this month’s allowance.
Batch changes
Filter by SIM list, project, plan type, or usage, then change them together. Preview, review, and run in batches to keep the risk down. This fits a company-wide plan adjustment or a channel migration. The change syncs to the operator so both sides show the same plan status.
Self-service upgrades
An end customer picks a higher tier on the self-service site and pays, and the platform applies the upgrade. Tied to plan subscription and payment integration, that closes the loop from choosing a plan, to paying, to the plan taking effect. You can allow upgrades only and block downgrades, depending on the business rule.
3. Change flow
4. Plan changes, subscriptions, and suspend/resume
Plan changes, plan subscriptions, and suspend/resume solve different problems. The differences:
| Dimension | Plan change | Plan subscription | Suspend and resume |
|---|---|---|---|
| What it covers | Swap the plan on an activated SIM | Buy a new plan | Turn the network on or off |
| Who it applies to | Activated SIMs | First purchase, renewal, or upgrade | Activated SIMs |
| What it does | Upgrade, downgrade, or switch | Choose a plan, pay, and provision | Suspend or resume |
| Creates an order | No. A change does not create a subscription order | Yes | No |
The three work together. Plan subscription creates an order and provisions the plan. A plan change replaces the plan on an activated SIM. Suspend and resume turns the network on or off.
5. Typical use cases
- Upgrade when data runs short: The monthly allowance is not enough. The user moves to a higher tier and it takes effect at once. Linked with data alerts, you can prompt that upgrade.
- Downgrade to cut cost: Once usage settles, move to a lower tier next month so unused data is not paid for again.
- A project-wide change: When a project ends or the policy changes, change the plans on every SIM in that project in one batch.
6. What you gain
Plan changes on the SimtoLink IoT Cloud Platform let you run plans with more flexibility. Users adjust with their usage, the business can reshape the plan mix, and batch changes raise operating efficiency. Linked with data alerts and overage management, you can prompt users to upgrade, which lifts revenue and the experience.
7. Implementation notes
Set clear rules, such as upgrades now and downgrades next month. Self-service upgrades for end customers can sit on plan subscription and payment. Try a small batch before a large change. Keep the change in sync with the operator so the status matches. SimtoLink can help with the change flow and the API connection.