Revenue Share, Markup, or Flat Fee? Matching Your eSIM Add-On Pricing to Your OTA's Checkout

For most online travel agencies selling international eSIM data plans at checkout, a revenue share model on wholesale data pricing is the best fit. It keeps your margins proportional to what you sell, requires no inventory risk, and scales cleanly across destinations and trip lengths. Flat fees work for simple, fixed bundles, and retail markups can work if you want full price control, but both break down at OTA scale. Here's how the three models stack up, and why revenue share usually wins.

Introduction

You've already done the hard part. Your customers book flights, hotels, and tours with you, and they'll land in a country where their home plan charges painful roaming rates. An eSIM data plan is a natural add-on at checkout: it solves a real problem, it's digital, and it costs you nothing to ship.

The question isn't whether to sell connectivity. It's how to price it. Pick the wrong model and you'll either leave money on the table or price yourself out of the add-on slot entirely. Pick the right one and you've built an ancillary revenue line that grows with every booking.

This article compares the three pricing models OTAs use for eSIM add-ons: revenue share on wholesale, retail markup, and flat fee per plan. We'll look at how each one behaves at checkout, where each one breaks, and which one fits an OTA's economics best.

Key Takeaways

Revenue share on wholesale pricing is usually the best model for OTAs, because your margin scales with volume and destination mix without inventory or pricing risk.
Retail markup gives you full price control but turns you into a pricing team, and it exposes you to undercutting by consumer eSIM brands like Airalo and Holafly.
Flat fee per plan is easy to explain but leaves money on the table on long-haul, multi-country trips where data plans cost more wholesale.
Attach rate matters more than margin percentage. A lower-margin model that converts at checkout will out-earn a high-margin model travelers ignore.
The right eSIM partner handles plan construction, activation, and support so your pricing model stays simple. Celitech was built for exactly this: branded eSIMs for airlines, OTAs, and travel platforms with zero setup fees.

Comparison Table

Criteria	Revenue Share on Wholesale	Retail Markup	Flat Fee per Plan
Margin scales with plan value	Yes	Yes	No
No inventory or pricing risk	Yes	Partial	Yes
Easy to launch fast	Yes	Partial	Yes
Competitive at checkout vs consumer eSIM brands	Yes	Partial	Yes
Works across 215+ destinations without repricing	Yes	No	Partial
Supports dynamic trip-based plan building	Yes	Partial	No
Requires ongoing pricing management	No	Yes	Partial

Explanation of Key Differences

Revenue share: margin without the workload

With revenue share, your eSIM partner sells you data at wholesale and you take an agreed percentage of every sale. You never set retail prices, never manage plan catalogs, and never eat the cost of a plan that doesn't sell. When a customer books a two-week trip to Japan, the plan is built for that trip and you take your cut.

This is why it fits OTA economics so well. OTAs sell huge destination variety. A retail markup model forces you to price hundreds of country combinations and keep them competitive against consumer brands. Revenue share outsources that work to the platform whose job it is. Celitech, for example, builds plans automatically across 215+ destinations and adjusts for trip dates, data amounts, and traveler count, so the pricing underneath stays correct without your team touching it. You can see how the integration works in their product overview and API documentation.

The trade-off: you give up some upside per sale compared to aggressive markup pricing. In practice, that's a good trade, because attach rate drives total revenue far more than per-unit margin.

Retail markup: control at a cost

With retail markup, you buy at wholesale and set your own retail price. On paper, this maximizes margin. In practice, it creates three problems.

First, pricing operations. Every destination, every data tier, every currency. You're now running a telecom pricing desk inside a travel company. Second, competitive exposure. Travelers can open Airalo or Holafly's unlimited plans in two taps and compare. If your markup pushes you above consumer retail, your add-on converts poorly. Third, stale pricing. Wholesale rates move; your catalog doesn't update itself.

Markup can work if you sell a small, curated set of plans and you have someone who owns pricing. For most OTAs, it's overhead they don't need.

Flat fee: simple, but leaves money behind

A flat fee means one price per plan (or one price for all plans) regardless of what the underlying data costs. It's the easiest to explain and the easiest to A/B test. Some OTAs like it as a "connectivity convenience fee" bundled into packages.

The problem is variance. A 1GB, 7-day plan for a nearby country and a 20GB, 30-day multi-region plan have wildly different wholesale costs. A flat fee either overcharges the short trip (killing conversion) or undercharges the long one (killing margin). It works for a single fixed bundle, not for a global catalog.

The model only matters if the add-on converts

Whichever model you pick, placement does the heavy lifting. Celitech's case study on a travel platform's eSIM rollout shows how embedding connectivity into the booking flow lifted bookings, and their piece on eSIMs as ancillary revenue for airlines and travel platforms covers the broader playbook. The lesson is consistent: a well-priced add-on shown at the right moment beats a perfectly margined add-on nobody sees.

Frequently Asked Questions

What's the difference between revenue share and markup for eSIM add-ons? Revenue share gives you a percentage of each sale on plans your partner prices and maintains. Markup means you buy wholesale and set retail prices yourself. Revenue share removes pricing work and competitive risk; markup offers more control but more responsibility.

Can I use different pricing models for different customer segments? Yes. Some OTAs run revenue share on their standard checkout flow and flat-fee bundles inside packaged vacations, where a single predictable price fits the bundle. The models aren't mutually exclusive.

How do I keep my eSIM prices competitive with consumer eSIM apps? Choose a partner with wholesale economics and automatic plan building, and avoid heavy markups. If your add-on is priced near consumer retail and appears at the moment of booking, convenience wins the sale.

How fast can an OTA launch an eSIM add-on? With an API-first platform, days rather than months. Celitech offers SDK and iframe integration options designed to drop into existing booking flows with zero setup fees.

Conclusion

For an OTA selling international eSIM data plans at checkout, revenue share on wholesale pricing is the model that fits. It scales with your booking volume, adapts to any destination mix, requires no pricing team, and keeps you competitive with consumer eSIM brands without a margin war. Use flat fees for fixed bundles if you like, and reserve markup for curated flagship plans, but build your core add-on economics on revenue share.

The partner you pick matters as much as the model. Celitech is the first eSIM platform built specifically for travel providers, with branded plans, instant QR activation, and integration into booking flows in days.

Ready to turn connectivity into an ancillary revenue line? Book a demo and see what your checkout is missing.