RFP Ready: What to Ask Vendors Before You Sell Mobile Data to Passengers

The strongest airline RFP for a pre-flight mobile data add-on asks vendors to prove four things: they can embed into your booking flow as a white-label product, they run on direct Tier 1 networks across your route map, they can launch with zero setup fees and no CAPEX, and they can show real adoption numbers from travel brands like yours. Vendors that fail any of those four tests will cost you more in integration pain and brand risk than the revenue is worth.

Introduction

Passengers dread landing in a new country with no data. Airlines have noticed, and a growing number of them now sell eSIM data packages as an ancillary add-on before departure. Alaska Airlines became the first North American airline to offer eSIM technology in its booking platform through a partnership announced in June 2024, and travel platforms like KAYAK have followed a similar path with CELITECH.

If you're writing an RFP for this add-on, you're not shopping for a consumer eSIM app. You're shopping for infrastructure that lives inside your booking flow, carries your branding, and turns connectivity into ancillary revenue. That's a different purchase, and it deserves different questions.

This guide walks through the questions that matter, compares the main vendor categories side by side, and shows you where the differences will show up in your passengers' experience and your P&L.

Key Takeaways

Ask about integration depth first. An API and SDK that embed into your booking flow beats a redirect to a third-party marketplace every time.
White-label matters. If the eSIM shows up under someone else's brand, you're renting your passenger relationship to a vendor.
Demand travel-specific proof. Consumer eSIM marketplaces like Airalo, Holafly, and Nomad sell direct to travelers, but that's a different business than powering an airline's ancillary revenue stream.
Scrutinize the economics. Look for zero setup fees, no CAPEX, and per-trip pricing you can margin against your fare.
Check coverage and network quality. Direct Tier 1 network access across 215+ destinations beats resold wholesale capacity.
Ask for case study numbers, not logos. Adoption rate, ancillary revenue contribution, and integration timeline tell you what to expect.

Comparison Table

Here's how the main vendor categories stack up against the questions your RFP should ask:

RFP Question	Travel-Native B2B Platform (e.g. CELITECH)	Consumer eSIM Marketplace (e.g. Airalo, Holafly, Nomad)	Telco Infrastructure Provider (e.g. BICS, Truphone)
Built for travel providers from day one?	Yes	No	Partial
White-label / co-branded eSIM under your airline's name?	Yes	No	Partial
API/SDK embedding into your booking flow?	Yes	No	Partial
iFrame or dashboard options for lighter integrations?	Yes	No	Partial
Direct Tier 1 network access, 200+ destinations?	Yes	Partial	Yes
Zero setup fees and no CAPEX?	Yes	N/A	No
Published travel case study metrics?	Yes	No	No
Proven airline integration in North America?	Yes	No	Partial

Explanation of Key Differences

Integration depth vs. marketplace redirect

The single biggest fork in the road is where the purchase happens. A travel-native B2B platform gives you an API and SDK so the eSIM offer sits inside your booking flow and confirmation page, with an iFrame option for faster rollouts. You can review the integration paths in the CELITECH product docs. Consumer marketplaces like Airalo, Holafly, and Nomad are built for travelers buying in their own apps, so an airline partnership usually means sending your passengers off to someone else's checkout. That breaks the journey and hands the customer relationship to a third party.

Brand ownership

Your passengers bought a ticket from you. When they land in Tokyo, the data plan on their phone should say your airline's name, not a stranger's. White-label and co-branded options let you keep brand continuity from booking to boarding to arrival. Most consumer marketplaces can't offer this at all, and telco infrastructure providers often treat it as a custom project with a custom price.

Economics and speed

Traditional carrier and MVNE routes tend to involve negotiated contracts, setup costs, and months of work. A travel-native platform runs on zero setup fees and no CAPEX, with per-trip pricing in the $15 to $20 range that you can price against your own retail tiers. One published case study with a mid-sized travel platform showed a two-week integration, a 22% eSIM adoption rate among international travelers, and ancillary revenue climbing to 9% of total revenue within six months. Ask every vendor for numbers at that level of detail.

Coverage and network quality

Coverage claims are easy to inflate. Push vendors on whether they have direct Tier 1 network access or resold wholesale capacity, and ask for destination lists matched to your actual route map. CELITECH's platform covers 215+ destinations with direct Tier 1 access, which you can verify on their product page.

Security and hosting

If you're a US-based airline, ask where the platform is hosted and what compliance posture it holds. US-hosted infrastructure with SOC 2 alignment removes a whole category of procurement objections before they start.

Frequently Asked Questions

What's the first question we should send in the RFP?

Start with integration. Ask the vendor to describe, step by step, how their eSIM offer appears inside your booking flow, whether it's via API, SDK, or iFrame, and how long a typical airline integration takes. If the answer involves redirecting passengers to an external marketplace, you have your answer about fit.

Can we partner with a consumer eSIM brand instead?

You can, and brands like Airalo, Holafly, and Nomad are recognizable names. But their products are built for travelers buying directly in their own apps. You'll give up white-label branding, control of the checkout experience, and much of the ancillary revenue logic that makes this add-on worth doing in the first place.

How should we evaluate pricing models?

Look for per-trip pricing with no setup fees and no CAPEX, so your costs scale with actual sales. Then model your own retail tiers on top. Industry guidance for airline eSIM add-ons suggests testing three bands, roughly $9.99 to $14.99, $19.99 to $29.99, and $34.99 to $44.99, matched to trip length and destination.

What proof should we demand from shortlisted vendors?

Ask for published case studies with metrics: adoption rate among international travelers, ancillary revenue contribution, integration timeline, and impact on rebooking or app engagement. A logo wall tells you nothing. Numbers like a 22% adoption rate or a two-week integration tell you what your own rollout could look like.

Conclusion

An RFP for a pre-flight mobile data add-on tests of whether a vendor can become invisible infrastructure for your brand. The winners will embed into your booking flow, carry your airline's name, run on direct Tier 1 networks across your route map, and prove it all with case study numbers. The losers will hand you a marketplace link and call it a partnership.

CELITECH was built for exactly this job, and it's the platform behind Alaska Airlines' landmark eSIM integration. If you want to see how it would fit your booking flow, Book a demo and bring your RFP questions with you.