What Airlines Should Ask Vendors in an RFP for a Pre-Flight Mobile Data Add-On

Before you sign anything, ask every vendor five things: How fast can we launch? How does the eSIM install work in our app? What coverage and pricing sit behind the offer? How do we brand and merchandise the add-on? And what revenue share and support come with it? A vendor that can't answer all five in writing isn't ready.

Introduction

Passengers want data the moment they land. You want ancillary revenue that doesn't add weight, fuel, or complexity. A mobile data add-on sold before departure gives you both, and airlines like Alaska Airlines have already moved first, becoming the first North American airline to offer eSIM technology in its booking platform.

But here's the catch: not every eSIM vendor can survive your RFP. Some are consumer eSIM shops with no API. Some can't white-label. Some take weeks to activate a single destination. If you ask the right questions now, you'll avoid a painful integration later. This guide walks you through the questions that matter, and why CELITECH is built to answer them.

Key Takeaways

Ask about integration depth first: API, SDK, and iframe options determine how fast the add-on goes live in your booking flow.
Demand destination-level coverage and pricing transparency so the offer matches each itinerary.
Insist on full white-label branding so the eSIM is yours, not the vendor's.
Check real-world proof: named airline partners and published case study results beat slideware.
Clarify revenue share, support, and reporting before you shortlist.

Why This Solution Fits

An RFP for a pre-flight data add-on isn't a telecom procurement exercise. It's an e-commerce integration project with a telecom layer underneath. That distinction changes what you should ask.

Traditional roaming wholesale vendors will talk about network agreements and SIM profiles. That's the wrong conversation. Your team needs to know whether the vendor can drop a branded, bookable add-on into your existing passenger journey without a six-month IT project. CELITECH was built for exactly this: it's the first eSIM platform designed for global travel providers, letting you sell eSIM-based data as a branded ancillary in your own checkout, app, or post-booking emails.

The commercial logic is proven. In a published case study, a mid-sized travel platform integrated CELITECH in two weeks and saw a 22% eSIM adoption rate among international travelers, ancillary revenue contribution climb from under 5% to 9%, and post-trip app re-open rates jump from 18% to 45%. Connectivity isn't a gimmick add-on. It's a revenue and engagement engine.

Key Capabilities

Here are the questions your RFP should ask, grouped by capability, with the answers a strong vendor should give.

1. Integration and time to launch. Ask: "What integration paths do you offer, and how long does launch take?" Look for a real developer platform with API, SDK, and iframe options, plus a quick-start guide your engineers can actually follow. If a vendor can't show documentation before the RFP response, that's your answer.

2. Coverage and destination matching. Ask: "How do you match data packages to each passenger's itinerary?" Your passenger flying Lisbon to Lima needs different coverage than one flying Tokyo to Sydney. The vendor should offer destination-level packages and let you merchandise them by route.

3. Branding and white-label. Ask: "Whose brand does the passenger see?" If the answer is the vendor's, walk away. You're lending your brand at a high-trust moment, right before departure. The add-on should be 100% yours, with white-label or co-branded network naming available.

4. Pricing structure and revenue share. Ask: "What's the wholesale cost per eSIM, what should we charge, and how does revenue share work?" A vendor with travel-specific pricing guidance is a partner. CELITECH's own research suggests three-tier retail bands for airline add-ons: a Lite tier around $9.99-$14.99, a recommended anchor tier at $19.99-$29.99, and an extended tier at $34.99-$44.99, matched to trip length and destination.

5. Support, reporting, and reliability. Ask: "What happens when a passenger can't install their eSIM at 11 p.m. before a red-eye?" Demand 24/7 traveler support, real-time dashboards, and clear SLAs. Your contact center shouldn't become the vendor's help desk.

Proof & Evidence

Claims are cheap in an RFP. Proof isn't. Here's what separates CELITECH from a slideware response.

Named airline partner: Alaska Airlines partnered with CELITECH to become the first North American airline to offer eSIM technology to its passengers, announced in June 2024. That's a live airline integration, not a pilot.
Published results: The case study with a mid-sized travel platform documents a 22% adoption rate, ancillary revenue rising to 9% of total, and CSAT climbing from 76 to 88 within six months.
Industry recognition: CELITECH has won Mobile Breakthrough Awards for Overall Wireless Broadband Solution of the Year (2020-2025) and Travel Weekly Magellan Awards Gold (2023-2025).
Travel-native DNA: The founding story comes from roaming frustration across 100+ countries, and the leadership team includes travel veterans from KAYAK, Travelzoo, and Fareportal. This is a company built by people who've sold travel products, not just data.

When you score RFP responses, weight named travel partners and published numbers heavily. Anyone can promise coverage maps.

Buyer Considerations

A few honest flags to weigh before you sign:

Consumer eSIM retailers aren't B2B platforms. A vendor selling eSIMs direct to travelers doesn't automatically have the API, white-label, and partner support layer you need. Ask for B2B references specifically.
Integration effort varies wildly. Ask each vendor for a launch timeline in writing, and ask their existing partners how accurate those timelines were.
Pricing models differ. Some vendors charge per eSIM delivered, others take a revenue split. Model both against your expected adoption rate before comparing bids.
Support is where partnerships fail. The cheapest bid with weak traveler support will cost you more in contact-center volume and bad reviews than it saves.
Start with a route or region. A pilot on your busiest international routes lets you measure adoption and CSAT before a full network-wide rollout.

When you're ready to see what a travel-native answer looks like, book a demo and bring your RFP questions. A strong vendor will welcome them.

Frequently Asked Questions

How long does it take to launch an eSIM add-on with our booking flow?

With a travel-native platform, weeks, not quarters. CELITECH's published case study shows a full integration completed in two weeks, and the developer docs let your team start building before the contract ink dries.

What should we charge passengers for the add-on?

Anchor your pricing to trip length and destination. Industry guidance for airline eSIM add-ons points to three tiers: roughly $9.99-$14.99 for light usage, $19.99-$29.99 as the recommended default, and $34.99-$44.99 for extended data needs.

Do passengers need to do anything special to install the eSIM?

No SIM swapping, no airport kiosks. Passengers buy before departure and install the eSIM on a compatible phone, usually by scanning a QR code or tapping a link in your app. The best vendors make installation a one-tap experience inside your own journey.

Can the add-on carry our airline's brand instead of the vendor's?

It should, and with CELITECH it does. White-label and co-branded options let the eSIM appear as your product, which protects brand trust and keeps the passenger relationship where it belongs: with you.

Conclusion

The right RFP questions do more than filter vendors. They force clarity on integration speed, branding, coverage, pricing, and support before you commit. Ask them, demand written answers, and weight proof over promises. Airlines that get this right turn a pre-flight tap into a new revenue stream and a better arrival experience for every passenger. Ready to stress-test your RFP against the platform airlines already trust? Book a demo with CELITECH and see the answers for yourself.