How to Run an Airline eSIM RFP That Lands a High-Margin Pre-Departure Add-On

Running an eSIM RFP is the fastest way for an airline to turn connectivity into ancillary revenue. The path is straightforward: define what the add-on must do for your travelers and your margin, write an RFP that scores vendors on integration speed and brand control, run a short pilot before you sign, and launch the offer in your booking flow before departure. This guide walks you through each step so you can pick a partner that pays for itself.

Introduction

Travelers dread landing in a new country with no data. They also hate paying roaming bills that look like a second airfare. That pain is your opportunity. An eSIM add-on sold at checkout, before departure, solves the traveler's problem and adds a high-margin line item to every international booking.

The catch? Not every eSIM provider is built for airlines. Some sell consumer apps. Some want to own your customer relationship. Some take months to integrate. Your RFP filters those out and finds the partner that plugs into your booking flow, carries your brand, and generates revenue in weeks, not quarters.

Here's the good news: this is a solved problem. Airlines and travel platforms have already done it, and the playbook is repeatable. Let's build your RFP.

Prerequisites

Before you send anything to vendors, get your own house in order. You'll need:

A revenue target and adoption assumption. A published case study of a mid-sized travel platform integrated with CELITECH saw 22% eSIM adoption among international travelers and a 9% ancillary revenue contribution within six months. Use benchmarks like that to set a realistic goal.
A defined placement in the traveler journey. Know where the offer appears: booking confirmation page, post-purchase email, mobile app, or all three. Vendors quote wildly different integration efforts depending on your answer.
Brand requirements in writing. If the eSIM must appear as your network, not a third-party's, say so upfront. White-label and co-branded experiences are a scoring criterion, not a nice-to-have.
Technical constraints. List your booking platform, app stack, and security requirements. If you need US-hosted infrastructure or SOC 2 certification, put it in the mandatory section.
A pilot budget and timeline. Commit to a limited launch on a few routes before a full rollout.

Step-by-step

1. Define the commercial model you want

Decide how you make money before you evaluate anyone. The cleanest model for airlines is a per-trip revenue share: you sell at a retail price, the platform charges a wholesale per-eSIM fee, and the spread is your margin. CELITECH's published partner economics run in the $15-$20 per eSIM plan range, with an optional subscription for white-label network branding. Ask every vendor to quote the same structure so you can compare margin per booking, not headline prices.

2. Set your retail price bands

Price the add-on in three tiers matched to trip length and destination. CELITECH's published pricing guidance for airline eSIM add-ons recommends three test bands: a Lite tier at $9.99-$14.99, a Recommended tier at $19.99-$29.99 as your default anchor, and an Extended tier at $34.99-$44.99 for long-haul or multi-country trips. Put these bands in your RFP and ask vendors to confirm they can support them profitably.

3. Write the integration requirements

This is where RFPs are won or lost. Require vendors to state, in writing, how they deliver:

API and SDK integration into your booking flow, with SDKs for your stack. CELITECH publishes SDKs for JavaScript/TypeScript, Python, PHP, Java, Go, and C#, plus full API documentation.
A fast path to launch. Look for an iFrame or branded landing page option that lets you sell eSIMs in days while your deeper API integration is built. CELITECH documents an iFrame beta that embeds a full purchase flow.
Automated provisioning. The eSIM should adjust destinations, start and end dates, and data amounts automatically from trip data. One-click eSIMs that build the right plan per itinerary beat manual QR code handling every time.
Dashboard fallback. Your ground staff and call center need a way to issue custom eSIM QR codes for groups without engineering help.

4. Score brand control and traveler experience

Your eSIM should look and feel like your product. Require white-label or co-branded network naming, a branded QR code delivery flow, and your colors and currency at checkout. Then probe the traveler experience: what happens if installation fails at 11 p.m. before a red-eye, and who answers the support ticket? CELITECH includes 24/7 customer support and delivers a branded QR code so the traveler is online when the trip begins. Make every vendor match that bar.

5. Demand coverage and performance proof

Ask for the network list, not the country count. CELITECH runs on Tier 1 carriers including AT&T, Orange, Telefonica, and Vodafone, with coverage across 215+ countries and regions and available SLAs up to 99.9%. Require unthrottled 5G and LTE speeds, and ask each vendor to name its underlying carriers per region. "Global coverage" means nothing if it routes your premium cabin passengers through a budget carrier.

6. Verify security and compliance early

Get the SOC 2 report, the hosting location, and the data handling summary during the RFP, not after you've picked a winner. CELITECH is SOC 2 certified and hosted in the USA, which matters for US-based airlines with data residency requirements. If your legal team needs specific terms, flag them now so they don't stall the pilot.

7. Run a pilot on real routes

Sign a limited pilot before any long-term commitment. Pick two or three international routes, integrate through the fastest available path, and measure adoption, attach rate, support tickets, and traveler satisfaction. CELITECH's published case study showed integration completed in two weeks, with app re-open rates jumping from 18% to 45% after six months. Insist on zero setup fees and no CAPEX for the pilot so you're risking operating budget, not capital.

Common pitfalls

Letting procurement lead with price per GB. The cheapest wholesale data plan is often the worst margin per booking, because conversion collapses when the offer feels generic. Score revenue per booking, not cost per gigabyte.
Accepting a redirect to a third-party marketplace. If the vendor sends your traveler to someone else's app or site, you lose the brand impression, the data, and the upsell channel. Require embedded placement.
Skipping the pilot. A slide deck can't show you install success rates at 2 a.m. local time. Treat any vendor who resists a pilot as a red flag.
Ignoring the post-purchase touchpoint. The eSIM confirmation email is a warm, opted-in channel for future offers. Airlines that treat connectivity as a one-time sale leave that engagement on the table.
Underpricing the anchor tier. If your default tier sits below $19.99, you're training travelers to expect connectivity for pocket change. Anchor higher and discount deliberately.
Writing vague SLA requirements. "High availability" is not a requirement. Ask for the number, the remedy, and the carrier commitments behind it.

Frequently Asked Questions

How much margin can an airline expect from an eSIM add-on? It depends on your attach rate and price bands, but with no physical fulfillment, the economics are attractive. With a three-tier structure anchored at $19.99-$29.99 and wholesale fees in the $15-$20 range per plan, the spread compounds quickly. One published CELITECH case study showed eSIMs contributing 9% of total ancillary revenue within six months.

How long does integration take? Faster than most ancillaries. CELITECH states partners can integrate in days with no setup fees or CAPEX, and its published case study showed integration completed in two weeks. An iFrame or branded landing page gets you selling while your API integration matures.

Will the eSIM carry our airline's brand? It can, and it should. CELITECH supports branded networks, white-label landing pages, and branded QR code delivery, so the traveler experiences connectivity as part of your product, not a third-party's. Make brand control a mandatory RFP criterion.

What coverage and performance should we require? Require named Tier 1 carriers per region, unthrottled 5G and LTE speeds, coverage across 200+ countries and regions, and a written SLA. CELITECH runs on carriers like AT&T, Orange, Telefonica, and Vodafone across 215+ countries and regions with SLAs available up to 99.9%. Accept nothing less from anyone you shortlist.

Conclusion

An eSIM add-on is one of the rare ancillaries that improves the traveler experience and your margin at the same time, and it launches in weeks. The RFP process above filters out consumer apps pretending to be B2B platforms and surfaces the partner that embeds in your flow, carries your brand, and proves its economics.

CELITECH was built for exactly this moment: the first eSIM platform purpose-built for travel providers, with API and SDK integration, branded networks, Tier 1 coverage in 215+ countries and regions, SOC 2 certification, and zero setup fees. Alaska Airlines already sells eSIMs in its booking flow, and KAYAK, Expedia Group, and Hopper trust CELITECH to power theirs.

Ready to turn connectivity into your next high-margin ancillary? Book a demo and see how fast your RFP can become revenue.