How eSIM Reseller Pricing and Margins Work

eSIM reseller pricing works when the way you buy connectivity matches the way you sell it. This matters most to resellers, digital brands and aggregators who are about to publish a price list. Your margin depends on that match more than on any single price point. This article covers the wholesale models, the retail models and the factors that move margin. It contains no figures, because commercial terms are agreed per engagement.

Wholesale cost models: pay-per-bundle and pay-per-megabyte

2SkyMobile supplies wholesale data in two billing models: pay-per-bundle or pay-per-megabyte, with custom data plans and validity periods. Settlement terms are by agreement. Connectivity is delivered through licensed third-party operators and network partners.

Pay-per-bundle. You pay a set cost for each bundle you provision. Your cost per sale is known before the customer buys. Choose this when you sell fixed packages, because your retail price and your cost both attach to the same unit. The risk is unused data: if the customer does not consume the bundle, your cost does not shrink.

Pay-per-megabyte. You pay for what customers actually consume. Your cost follows usage. Choose this when you bill by usage or want to avoid paying for data that is never used. The trade-off is forecasting. Your cost per customer is not fixed at the point of sale, so heavy users can erode margin if your retail price assumes light use.

Neither model is better in general. The right one is the one whose cost unit matches your retail unit.

Retail price models for an eSIM store

An eSIM store can use three common retail patterns.

• Fixed data packages. The customer buys a defined amount of data for a defined period. This is the easiest model to explain and to compare against competitors. It suits travel and short-stay buyers who want a known price before checkout.
• Usage-based billing. The customer pays for what they use. This suits recurring users and business accounts that dislike guessing a package size. It needs clear in-app or in-portal usage visibility, or customers will dispute charges.
• Plans with data rollover and extended validity. Unused data carries forward, or the plan lasts longer. This suits infrequent travellers who resent losing data. It also lengthens the time you carry an obligation to the customer.

When your audience is price-comparing at checkout, choose fixed packages because the offer is legible in seconds. When your audience uses data regularly and unpredictably, choose usage-based billing because it removes the package-size decision. When retention matters more than first-sale margin, add rollover or extended validity because it gives customers a reason to return.

What drives reseller margin

Margin is the gap between what you pay wholesale and what customers pay you, minus the costs of selling. Five factors move it most.

1. Wholesale model and terms. Pay-per-bundle and pay-per-megabyte distribute risk differently. The terms you agree decide who carries unused data.
2. Package design. Package sizes, validity periods and coverage scope change both your cost and what customers will pay. Custom plans let you align them, but only if you design them against your cost unit.
3. Validity and rollover rules. Longer validity and rollover raise perceived value. They also extend your exposure. Check how retail validity relates to wholesale validity before you promise either.
4. Sales channel cost. Payment processing, marketplace fees, affiliate commissions and ad spend all come out of the same gap. A price that works on your own store may fail on a channel with fees.
5. Support and refunds. Install problems, device compatibility questions and refund requests cost time. Low-priced plans with high support load can end up less profitable than higher-priced plans with few tickets.

Commercial terms, including any minimum commitments, are agreed for each engagement. Treat any margin benchmark you read elsewhere as a different deal from yours.

Matching wholesale and retail models

The table shows which combinations keep your cost and revenue units aligned.

A mismatch is not forbidden. It means you carry a risk that you should price in on purpose, not discover later.

Example: a brand sells fixed packages but buys pay-per-megabyte. The package price must then cover the realistic upper range of consumption, not the average. If you cannot estimate that range, start with pay-per-bundle and revisit once you have real usage data.

Where margin leaks after launch

Margin can leak through small mismatches that a price list does not show.

• Validity gaps. You sell a plan that lasts longer than the supply behind it. Align the two, or agree custom validity with your supplier.
• Discount creep. Promotions and partner discounts stack. Set a floor price per package before you run campaigns.
• Channel mix drift. A growing share of sales through a fee-heavy channel lowers blended margin, even if no price changed.
• Unmonitored usage. On usage-based plans, a few heavy accounts can change results. Review consumption by account on a regular schedule.
• Support load on low-priced plans. Track tickets per plan type, not just revenue.

Review these points whenever you change a package, add a channel or renegotiate supply.

Checks before you publish a price list

Run these checks in order.

1. Name your cost unit (bundle or megabyte) and your retail unit (package or usage). Note any mismatch.
2. Confirm settlement terms and any minimum commitments with your supplier in writing.
3. Align retail validity with supply validity, including any rollover promise.
4. Add your channel costs and a support allowance to every package before you set the price.
5. Set a floor price per package and a rule for discounts.
6. Plan a first review once real usage data exists.

If you want to test a pricing model against your own channel mix, talk to 2SkyMobile: terms are agreed per engagement. See also the eSIM reseller program.