Selling eSIMs on Shopify or WooCommerce

Why the plugin route is tempting

If you already have a store, adding one more product to it is the obvious move. The domain is yours, the theme is done, the payment gateway is approved and your customers already know where the checkout is. An eSIM looks like a digital download — a code delivered by email — and every cart platform sells digital downloads.

Everything in that paragraph is true, and the conclusion is still usually wrong. The reasons are worth understanding rather than taking on trust, because they apply to any cart, any plugin and any marketplace app, present or future.

• The eSIM does not exist until it is bought. There is no file to attach to the product; the provider issues a fresh one, with its own activation code, when your order reaches them.
• The customer will come back to the order — to reinstall, to check data left, to buy more. A download link is a one-way door.
• The price you pay changes. Wholesale costs move, and a product whose cost moves under a fixed price will eventually sell at a loss without telling you.
• The support is specific. “No service” has three causes, none of them visible to a cart, and the customer will write to the address on your store.

What an eSIM order needs that a T-shirt does not

Walk through one order on each kind of product and the gap is obvious. A cart is built for the left-hand column.

Each right-hand cell is a piece of software somebody has to write, host and keep working against a provider’s API that changes. A plugin that does the first row is easy. A plugin that does all six is a product, and the ones that exist are priced like one.

The three ways to do it

A plugin that calls the provider

The cart takes the payment, the plugin buys the eSIM from the provider and emails the code. This is the route the search results sell. It works when the plugin is good, and its weaknesses are the rows below the first two: usage, top-ups, repricing and failed issuance are handled well, badly or not at all depending on the plugin, and you find out which after you have sold something. You are also now responsible for two pieces of software agreeing with each other — the cart and the plugin — and for the plugin surviving the next platform update.

Manual fulfilment

The cart takes the payment and you buy the eSIM by hand in your provider’s dashboard, then paste the code into an email. It is free and it is fine for your first ten orders. It is also the model that fails at the worst moment: a traveller buying at the airport at midnight does not want their eSIM when you wake up, and the one-star review says so.

A hosted eSIM storefront beside your site

You keep your main store for everything else and run the eSIM shop on software built for the six rows, linked from your site and on your brand — a subdomain or, on plans that include it, your own domain. The trade-off is that the checkout is a different page, which costs you a little conversion and buys you delivery, usage, top-ups and repricing you did not have to build. It is the route that scales without you writing code, and it is the one Esimbit is.

Whichever route you pick, the eSIM should be bought with your own provider account and paid into your own gateway. A route that puts somebody else’s keys or somebody else’s merchant account between you and the customer has quietly changed what you are — see the platform models post.

What each route really costs

The sticker price is the smallest part. Count the hours, and count the failure modes.

The manual route is right for a test and wrong for a business. Between the other two, the question is whether you would rather maintain software or subscribe to it, and how many orders a month it takes for the second to be cheaper. For most stores that number is small, because the plugin route’s real cost is the weekend you spend on it when it breaks.

How to decide

Four questions, in order. Most people are done after the second.

1. Is the eSIM the business, or an add-on to one? An add-on to a luggage store can afford a slightly separate checkout. A store whose product is the eSIM needs the software built for it.
2. Will you answer support yourself? If yes, you want the tools that make it short: a permanent order page the customer can reach, remaining data on it, a resend button on your side. Check that the route you are considering has them before the first ticket.
3. Who holds the keys and the money? Your provider account and your gateway, or somebody else’s. If somebody else’s, read the platform models post before going further.
4. Can you leave? Your customer list, your order history and your store address should come with you. A plugin locked to a cart or a marketplace app locked to a platform is a migration you will do later.

If you land on the hosted route, the sensible version is to link it from your existing site rather than replace anything: a menu item, a banner on destination posts, a line in your booking confirmation. Your main store keeps doing what it does; the eSIM store does the six rows.

• The three eSIM platform business models →
• What white-label should actually mean →
• What the storefront does for a customer →