1. Scenario overview
Data plan design is about what the product is: the tiers, the cycle, and the billing model. Plan packaging is the later step that maps a carrier tariff and puts the plan on or off the shelf. Design covers monthly, quarterly, and yearly cycles, tiers from 1MB to 100GB, and billing by usage, by time online, or by traffic pool. You shape the mix from the customer you want, your cost, and what competitors sell.
Packaging then turns that design into a plan you can sell, mapped to a carrier tariff. This page also covers promotions — a trial, a discount, a bundle — and the results, orders and revenue, so the mix keeps getting better. Design owns the tiers and the billing logic. Packaging owns the mapping and whether the plan is on sale.
2. Core capabilities
Tiers and cycles
Monthly, quarterly, and yearly cycles, with data tiers from 1MB to 100GB that you can combine. Prices can step by tier: a 1GB, 5GB, and 10GB monthly plan each at its own price. Set the tiers from how your customers actually use data, what the carrier costs, and what else is on the market. A larger tier should cost less per unit than a smaller one, so people pick the tier that fits.
Billing models
By usage: a plan on one SIM, when you can estimate the volume. By time online: when the volume matters less than how long the device stays connected. By traffic pool: many SIMs share one allowance, which fits a traffic pool, an enterprise private network, or connected vehicles where usage swings. Any of these can feed traffic billing.
Promotions
A trial (first month free or cheap), a discount (a promotion for a limited time), or a bundle of several tiers. Offers can be for new users only, or a renewal price for users you already have, which helps both acquisition and retention. A bundle of tiers also lifts the average order value.
Results
Orders and revenue, by plan, by time, and by channel. You can see which plans sell and which sit still, then change a tier or a promotion. With traffic statistics and the data dashboard, the same numbers support the next change and an A/B test.
3. How a plan is designed
4. Design, packaging, and billing
Data plan design, plan packaging, and traffic billing answer different questions.
| Dimension | Data plan design | Plan packaging | Traffic billing |
|---|---|---|---|
| Focus | What the product is, and how the tiers work | Carrier mapping, and on or off the shelf | What is receivable and payable |
| Core capabilities | Tiers, cycles, billing models, promotions, results | Tariff mapping, listing, and the form you can sell | Plan, overage, and pool charges, and the bill |
| What you get | Tiers, a cycle, a billing model, and a suggested price | A plan you can sell, and the SKU setup | Bills and a reconciliation report |
| What teams need | A mix that can compete | The design made sellable, and that catalog managed | A posting for the books, and a cost you can explain |
They work as a set. Design defines the product. Plan packaging makes it sellable. Traffic billing calculates the charge.
5. How to set the tiers
Look at how the customers you want actually use data. Low usage, such as meter reading or positioning, fits a small monthly tier. Medium and high usage, such as video monitoring or connected vehicles, fits a large tier or a traffic pool. When prices step, a larger tier should cost less per unit than a smaller one, so people land on the tier that fits. Price it against the carrier tariff, so there is still a sensible margin after packaging.
6. Typical use cases
- Stepped monthly plans: 1GB, 5GB, 10GB, 30GB, and other monthly tiers for different volumes.
- Quarterly and yearly plans: a longer cycle costs less per unit and holds customers who stay.
- A pool plan: many SIMs share one pool, which fits an enterprise private network or connected vehicles where usage swings.
7. Why it matters
Data plan design on the SimtoLink IoT Cloud Platform is how you put a competitive catalog on the table. Tiers and billing you can configure cover more than one kind of customer. Results tell you what to change next. With plan packaging, design defines the product and packaging is what you can actually sell.
8. Implementation notes
Design the tiers and the billing model first, then map them to a carrier through packaging. An A/B test is a fair way to see whether a plan works. Look at orders and revenue on a regular cadence and adjust the mix. SimtoLink can help with the design and the analysis, including a design workshop that starts from the customer you want, your cost, and the competitive set.