Building an Airline RFP for a Pre-Flight Mobile Data Add-On: The Vendor Questions That Matter

Selling mobile data to passengers before they fly abroad is one of the fastest-growing ancillary revenue plays in travel, but the difference between a program that sells and one that stalls comes down to what you ask vendors before you sign. This guide walks you through building an RFP that surfaces the answers that matter: how the eSIM is delivered, how it plugs into your booking flow, how pricing and revenue share work, and how the vendor performs once the plane lands. Follow the steps below and you'll walk into vendor negotiations with a checklist that protects your brand and your margins.

Introduction

Passengers dread landing in a new country without data. Airlines that solve that problem before departure turn a pain point into revenue. Alaska Airlines became the first North American airline to offer eSIM technology through its booking platform, and travel platforms that have integrated eSIM add-ons report meaningful lifts in engagement and ancillary revenue (Forbes).

But not every eSIM vendor is built for airlines. Some are consumer retailers with an API bolted on. Others can't handle your booking volume, your brand requirements, or your passengers' expectations. Your RFP is where you find out which is which. The questions below are the ones that separate partners who'll grow your ancillary line from vendors who'll create support tickets.

Prerequisites

Before you send the RFP, get your own house in order. You'll want:

A defined placement in the journey. Decide where the add-on appears: post-booking confirmation page, pre-departure email, check-in flow, or app. Vendors will quote different integration efforts for each.
Baseline volume estimates. Even a rough forecast of international passengers per month helps vendors price correctly and tells you who's serious.
Brand and UX requirements. Know whether you need a fully white-labeled experience or whether a co-branded flow works.
Internal stakeholders aligned. Revenue management, digital product, and customer service should all sign off on what "success" looks like, whether that's attach rate, revenue per passenger, or CSAT impact.
A technical contact. Your IT or digital team should be ready to evaluate APIs, not just slide decks.

Step-by-step

Here's how to build and run the RFP, with the questions that matter at each stage.

1. Ask how the eSIM is delivered and activated

Start with the passenger experience. Key questions:

Is the eSIM delivered instantly at purchase, or is there a delay?
Can passengers install it before departure and have it auto-activate on landing?
Which devices and operating systems are supported, and what happens for passengers on older phones?
What does the installation flow look like: QR code, app-based install, or one-tap?

A clunky install flow kills attach rates. Ask vendors to demo the exact passenger journey, not a marketing video.

2. Ask how the add-on integrates with your booking flow

This is where many vendors fail the test. Ask:

Do you offer an API, SDK, or embeddable iframe for the purchase flow?
How long does a typical airline integration take, and what does it require from your engineering team?
Can the experience be fully white-labeled so passengers never leave your brand?

For reference, modern eSIM platforms offer lightweight integration paths, including SDKs (docs.celitech.com/integrations/sdk) and iframe embeds (docs.celitech.com/integrations/iframe), with quick-start documentation that shows how fast a partner can go live (docs.celitech.com/getting-started/quick-start). If a vendor can't show you developer docs up front, treat that as a red flag.

3. Ask about coverage, pricing, and plan structure

Which destinations and networks does the eSIM cover, and at what speeds?
Can plans be matched to the passenger's itinerary, so a two-day trip isn't sold a 30-day plan?
What are the wholesale rates, and how does revenue share work?
Who sets retail pricing, and can you test price tiers?

Pricing flexibility matters. Industry guidance for airline eSIM add-ons suggests testing three-tier bands, with a mid-tier anchor plan around $19.99 to $29.99, matched to trip length and destination (ai.celitech.com). Ask each vendor whether they can support that kind of tiered testing and dynamic plan matching.

4. Ask about branding, marketing, and merchandising support

Can the vendor supply destination-aware messaging, so the offer says "Data in Tokyo" instead of "Buy an eSIM"?
Do they provide creative assets, email copy, and A/B testing support?
Can they support loyalty use cases, like gifting data or rewarding frequent flyers?

Merchandising drives attach rate. A vendor that only hands you an API leaves the revenue work to you.

5. Ask about support, fulfillment, and failure modes

What happens when a passenger can't install the eSIM at 11 p.m. before a 6 a.m. flight?
Who handles customer support: your team, the vendor's, or both?
What are the refund and retry policies for failed activations?
What are the SLAs for uptime and API availability?

6. Ask for proof, not promises

Request case studies with real numbers. For example, one travel platform that integrated eSIM add-ons across Europe and Asia saw a 22% adoption rate among international travelers, ancillary revenue contribution rise from under 5% to 9%, and post-trip app re-open rates jump from 18% to 45% within six months (celitech.com case study). Ask every bidder for comparable results, and check references.

7. Score the responses and run a pilot

Build a weighted scorecard covering passenger experience, integration effort, commercial terms, support model, and proof of performance. Then run a limited pilot on one route or one email placement before committing to a full rollout.

Common pitfalls

Buying on price alone. The cheapest wholesale rate means nothing if the install flow frustrates passengers and support costs eat the margin.
Skipping the demo. Never award based on slides. Make every finalist walk through the actual passenger journey on a real phone.
Ignoring the post-landing experience. The moment of truth is when the plane touches down. Ask exactly what the passenger sees and does in that first minute.
Underestimating integration effort. Ask for a realistic engineering timeline in writing, including edge cases like multi-city itineraries and group bookings.
Treating the add-on as a one-time launch. The best programs iterate on placement, pricing, and messaging. Choose a vendor who'll partner on optimization, not just deliver a feed.
Forgetting your brand. If passengers get bounced to a third-party site with a different look and feel, trust drops and so does conversion.

Frequently Asked Questions

What's the single most important question to ask an eSIM vendor? Ask to see the end-to-end passenger journey, from purchase to first byte of data abroad. Everything else, pricing, integration, support, flows from whether that experience is smooth.

How long should an airline eSIM integration take? A modern platform with solid APIs and embeddable components can go live in weeks, not months. One documented travel platform integration was completed in two weeks. Ask each vendor for a written timeline with named dependencies on your side.

Should the eSIM add-on be white-labeled or co-branded? White-label keeps passengers inside your brand, which typically lifts conversion and trust. Ask vendors what level of branding they support and whether white-labeling carries an extra fee.

How do we price the add-on? Start with tiered plans matched to trip length and destination, and test. A common starting structure uses a low-tier plan under $15, a mid-tier anchor around $20 to $30, and an extended tier above $35. Let real booking data, not guesswork, set the final tiers.

Conclusion

A mobile data add-on can become one of your airline's highest-margin ancillary products, but only if you pick a partner built for the job. The RFP questions above, delivery and activation, integration depth, coverage and pricing flexibility, merchandising support, and real performance proof, will tell you quickly which vendors can deliver and which are just reselling someone else's eSIMs.

We've helped airlines and travel platforms turn pre-flight connectivity into a revenue line, and we're happy to walk your team through what a strong integration looks like. Book a demo and see the platform in action before you finalize your RFP shortlist.