1. Scenario overview
Overage management is what you do after a plan or a pool runs out. A traffic pool is about sharing data across SIMs. A traffic alert warns before the allowance is gone. This page answers what happens next. Usage-based billing charges the extra data at a unit rate and keeps the service up. Automatic suspend stops the SIM as soon as the allowance is gone, which caps arrears. Throttle drops the speed so a basic connection remains. An automatic add-on pack orders the next pack and usage continues without a gap.
Pick the policy from what the service is worth and what it costs. High-value services usually stay on usage-based billing. Cost-sensitive ones usually suspend. The platform talks to the carrier and applies the policy you set. In B2B2C, the end user can get an overage notice with a path to renew.
2. Core capabilities
Usage-based billing
Extra usage is charged at the rate you set, for example yuan/GB, and the rate can step by tier. The service does not stop, which is what a high-value line that cannot drop needs. The overage lands on the bill through overage billing and traffic billing, so what is owed is calculated, not guessed.
Automatic suspend
The SIM stops as soon as the allowance is gone, which is how prepaid and cost-sensitive lines keep arrears down. It comes back after the user pays, through suspend and resume, which is what compliance and risk expect.
Throttle
Drop the speed to a low rate, such as 128Kbps, so a basic connection remains and the SIM is not fully offline. Use it when the line should stay up but a slower speed is acceptable. The throttle step is configurable.
Automatic add-on pack
When the allowance runs out, the platform orders an add-on, such as 1GB, and usage continues without a gap. Set the add-on plan and the payment method first. This is the B2B2C auto-renew path, and it runs with plan changes and payment integration.
3. What happens when data runs out
4. Overage, alerts, and billing
Overage management, traffic alerts, and traffic billing answer different questions.
| Dimension | Overage management | Traffic alerts | Traffic billing |
|---|---|---|---|
| Focus | What to do after the allowance is gone | A notice before it is gone | What is receivable and payable |
| Core capabilities | Usage-based billing, suspend, throttle, automatic add-on | Tiered alerts, multi-channel notices, renewal prompts | Plan, overage, and pool charges, and the bill |
| When it acts | After the plan or pool is used up | About to run out, already over, or abnormal | When the billing cycle arrives |
| What teams need | Continuity on one side, cost control on the other | An early warning and fewer stopped SIMs | A posting for the books, including the overage charge |
They work as a set. Traffic alerts warn early so fewer SIMs run over. Overage management sets the policy after the allowance is gone. Traffic billing calculates the overage charge.
5. Policies, including B2B2C
Set a different policy by plan, project, or customer, so each line of business can behave its own way. The overage rate, the throttle step, and the add-on plan are all configurable, including tiered rates where a larger volume costs less per unit than a smaller one. In B2B2C, an overage notice goes to the end user with a renewal link. If they did not renew on the earlier alert, they hear again once they are over, which is a second chance to convert.
6. Typical use cases
- High-value services: connected vehicles and industrial monitoring cannot drop. Overage is billed on usage and the service stays up.
- Cost-sensitive services: prepaid and low-ARPU lines suspend automatically so arrears do not grow.
- B2B2C: a traffic alert asks for a renewal first. After the allowance is gone, a second notice carries the renewal link again.
7. Why it matters
Overage management on the SimtoLink IoT Cloud Platform is how you hold continuity and cost in the same decision. Four policies cover the cases you actually run. A different policy per business means one platform can serve more than one commercial model. With traffic alerts and traffic billing, you can ask for a renewal before the SIM stops and still bill the overage correctly when it does not.
8. Implementation notes
Choose the policy from what the service is worth. Bill high-value lines on usage. Suspend the cost-sensitive ones. In B2B2C, use the traffic alert to ask for a renewal before the allowance is gone. Use tiered overage rates so a spike has a ceiling. An automatic add-on needs the pack and the payment method set first. SimtoLink can help you configure the policy.