“We don’t know which eSIM partner to choose.”

That sentence is becoming common inside banks, OTAs, fintechs, travel companies and enterprise platforms. Not because there are too few options. The opposite. There are now enough eSIM suppliers, wholesalers, API platforms and telecom infrastructure players to make procurement oddly difficult.

Open five sales decks and the language starts to merge: global coverage, competitive pricing, instant activation, white label, API integration, 24/7 support. Most claims may be valid. They simply do not tell a buyer what happens when a customer lands in Bangkok, the eSIM installs but does not attach to a network, and that customer blames your brand rather than the invisible supplier behind it.

That is the real selection problem.

The sameness problem

Consumer eSIM provisioning itself is increasingly standardized. The GSMA’s SGP.22 specification defines the remote SIM provisioning architecture for consumer devices, with version 2.7 published in April 2026. But technical compliance does not standardize network choice, routing, installation flow, usage visibility, support, refunds or recovery when something goes wrong.

This is why comparing partners by “countries covered” and price per gigabyte is becoming less useful. Two suppliers can both advertise 200 destinations while delivering very different products underneath.

The market is also converging. Consumer eSIM brands are opening partner APIs. Wholesale platforms are adding white-label controls. Infrastructure-led telecom players are selling embedded connectivity directly to non-telco brands. Banks such as Revolut and N26 are already proving that connectivity can sit inside a financial app rather than beside it.

The buyer therefore needs to choose an operating model before choosing a company.

Start with the job

A bank embedding travel data for premium customers has a different problem from an OTA adding an eSIM after checkout. A corporate platform distributing connectivity to employees has another problem again.

For a bank, regulatory responsibility, brand control, in-app installation and support standards may dominate. For an OTA, speed to market, conversion, coverage and simple fulfilment may matter more. For an enterprise platform, administration, policy controls, reporting and billing can outweigh consumer-facing branding.

Yet many RFPs still begin with a feature list instead of the customer journey.

A better first question is: what part of the connectivity experience are we prepared to own?

An affiliate or voucher model can be sensible for testing demand. A full API integration makes more sense when connectivity is part of the core product. A deeper infrastructure relationship matters when the business needs more control over regulation, network behaviour or the subscriber lifecycle.

Need help? Contact us: info@alertify.eu

Score the things customers notice

A practical procurement scorecard should give the highest weighting to what happens after launch.

Give 25 points to customer experience. Test installation steps, device compatibility, direct-install options, top-ups, repeat-trip behaviour and whether users stay inside your environment. “API available” is not enough. Airalo, for example, currently documents sandbox testing, usage management and direct iOS installation through its Partner API.

Give 20 points to network quality. Ask for the actual networks used in your ten most important destinations, not only country coverage. Ask about fallback networks, traffic routing, throttling and what changes when the preferred network is unavailable.

Give another 20 to operational control: provisioning status, usage data, webhooks, suspension, refunds, logs and the ability to diagnose failed activation without opening a generic ticket.

Allocate 15 to support and recovery. Who owns first-line support? What is the escalation SLA? Can a failed profile be replaced quickly? eSIM Go’s current documentation explicitly states that the commercial partner handles first-line support while it provides second- and third-line technical support. That may be perfectly acceptable—but the buyer should know before launch.

The final 20 points cover compliance and economics. Look beyond wholesale data price to pre-funding, minimum commitments, FX, refund rules, tax treatment and the internal cost of support. Cheap connectivity becomes expensive when humans have to rescue it.

Run the failure pilot

The best selection process should deliberately try to break the product.

Pick ten commercially important destinations, several iPhone and Android generations, awkward installation scenarios and at least one real support escalation. Test purchase, install, activation, top-up, network switching, low-data notifications, refund handling and reinstallation.

Then measure time to recovery.

This reveals more than another procurement presentation. Procurement sees total cost, product sees friction, engineering sees integration quality and customer support sees what it will inherit.

A supplier that performs beautifully in a demo but gives your team no visibility when something fails is not necessarily the safer partner.

Build for an exit

One question is still strangely absent from many eSIM RFPs: what happens if we want to change provider?

Buyers should understand how tightly their product catalogue, customer records, eSIM lifecycle and front-end journey are coupled to one supplier. Can another connectivity source be added later? Can the brand keep its UX? What data can be exported?

Not every company needs multi-provider orchestration. For a smaller OTA or a first pilot, that can add needless complexity. But larger banks, travel platforms and enterprise products should avoid designing themselves into an unnecessary corner.

The partner is part of your product

The eSIM market is moving beyond simple resale. 1GLOBAL’s deployments with brands including Revolut and N26 show the infrastructure-led direction, while Airalo, Yesim and eSIM Go show how reseller and API platforms are adding deeper integration, branding and lifecycle capabilities. The categories are starting to overlap.

That makes partner selection harder, but also more mature.

The next competitive advantage will not be a spreadsheet showing 200 countries versus 190. It will be control over failed installs, unavailable networks, refunds, support handovers and customers who need data now.

For B2B buyers, the right eSIM partner is not the company with the longest feature list. It is the one whose operating model matches your own, whose failures are visible, and whose problems your team can fix before the customer decides the problem is your brand.