Checking coverage before you sell it

What “coverage” on a package page means

A travel eSIM is a roaming profile. That single sentence explains most of what confuses people about this product. The profile belongs to an operator somewhere — often not in the country the traveller is going to — and when the phone lands, it attaches to a local network under a roaming agreement between the two. The traveller is a visitor on that network, exactly like a foreign SIM has always been, with a modern way of getting the profile onto the phone.

So “coverage in 200 countries” is a list of the places the underlying operator has agreements in. It is a real claim and it is not a promise about the experience. Everything a traveller actually notices — which local network they land on, how fast it is, whether it drops to a slower generation, whether tethering works, what country the internet thinks they are in — is decided below that number and is usually not printed anywhere.

• Which local networks the profile is allowed to use. One agreement or four, and in a large country that is the difference between signal in a city and signal on a road.
• What speed the agreement carries. Some wholesale deals are capped below what the local network can do, and the phone still shows full bars.
• What happens after the allowance. Cut off, throttled, or a top-up prompt — three different products sold under one word.
• Where the traffic comes out. The exit address is frequently the host operator’s country rather than the destination, which is invisible until something checks it.

None of this makes travel eSIMs bad. They are usually the right product for the trip. It makes them a product whose specification lives one level below the page you are buying from — and a reseller who has not looked at that level is quoting a price for something they have not seen.

What the catalogue does not tell you

Put two suppliers’ listings for the same destination side by side and the columns match: country, data, days, price. The differences are all in the rows nobody prints. These are the ones that turn into email.

The last two rows deserve special attention because they are the ones customers blame you for personally. Data-only is normal and fine — until a traveller expects a text message from their bank on a number that is not connected to this eSIM at all. And an exit address in the host operator’s country is normal too, right up to the moment a local banking app decides the customer is not where they say they are. Neither is a fault. Both are things a product page can say in one line and almost none of them do.

Checking it before you list it

There is no substitute for buying one. It costs a few dollars, it takes an evening, and it is the only way to find out what you are selling. Do this for your top three destinations before launch and for a new destination before it goes on the shelf.

1. Buy the package from your own supplier account at cost, on the same plan a customer would get. Not a demo, not a sandbox — sandbox eSIMs do not attach to anything.
2. Install it on a real phone and read what the profile says: the carrier name the phone shows, the generation it attaches at, and whether it appears as data-only.
3. If you cannot travel, ask somebody who is going. One traveller with your test eSIM and five minutes is worth more than a week of reading supplier documentation. Give them a checklist: a speed test, a map, a video, and a tethered laptop.
4. Check where the traffic comes out. Any address-lookup page will tell you the country, and if it is not the destination, that is a line you now owe your product page.
5. Run the allowance down deliberately on a small package and watch what happens at the end. This is the single most common gap between what a page implies and what a product does.

Then repeat the exercise with a second supplier for the same destination and compare. This is the point at which the two identical-looking listings stop being identical, and it is also the point at which you can price them honestly — a package on a better local network is worth more than the cheaper one next to it, and you can now say why. Tools like eSIMDB are useful for a first pass at what exists, but they are a directory rather than a test.

Speedtest and nPerf both publish where the local networks are actually good, by country and often by operator. Read that before the trip, not after: it tells you which network you WANT the profile to attach to, which turns the vague question “is this eSIM good in Spain” into a specific one you can ask your supplier.

The kinds of destination that catch people out

Rather than a country list that will be wrong by next quarter, here are the three shapes of problem. Almost every angry ticket about coverage is one of them.

Where the network matters more than the country

In a large country with several operators of very different reach, “covered” tells you almost nothing. The traveller who stays in one city will never notice; the one driving between two of them will notice within an hour. If your customers go to big countries, the network list is the specification and you should know it before you list the package.

Where the exit address is the problem

Some services care where the connection appears to come from rather than where the phone is: local banking apps, government portals, regional catalogues, and anything that does a location check for fraud. A roaming profile that exits in another country breaks these while the internet otherwise works perfectly, which is the most confusing possible failure for a customer to describe. It is also the easiest to defuse in advance with one honest line on the product page.

Where the rules are about the device, not the network

A few countries regulate handsets rather than connections — Türkiye is the example your customers will ask about, where a phone brought in from abroad is registered against its IMEI before it can keep using a local subscription. A roaming eSIM is a different situation from a local subscription, which is a large part of why visitors use one. It is also exactly the kind of rule that changes, so the correct answer to a customer is the current official one, not a sentence you copied from a blog last year — including this one.

The pattern across all three: the failure is not the eSIM, and the customer cannot tell that. Which means the work is not choosing a perfect package — there is not one — but saying enough on the page that the traveller recognises what is happening when it happens.

What to put on the product page

Everything you learned in the test is worth one line each, and those lines are the cheapest support you will ever write. Five of them cover almost all of it.

• Data only, no phone number, no SMS — and therefore keep your normal SIM active if your bank texts you.
• The networks it uses in that destination, named. If you do not know them, that is the question to take to your supplier before you sell it.
• What happens when the allowance runs out, in plain words, with the top-up link next to it.
• Whether tethering works, because the answer is yes or no and the customer will find out either way.
• Where the connection appears to come from, if it is not the destination. One sentence prevents an entire class of ticket.

A store that says these things sells slightly fewer eSIMs and keeps considerably more of the money, because the refunds it does not issue and the evenings it does not spend on email are both real. It is also the difference a reseller can actually offer: the brands compete on price and catalogue size, and the specific, honest description of a specific destination is something a large catalogue is structurally bad at.

• Which eSIM packages to sell →
• The support tickets an eSIM reseller gets →
• Choosing what your store sells →