What is Fulfilment?

Fulfilment sounds like a back-office word that customers should never have to think about. In practice it describes the moment an eSIM buyer feels most uneasy: payment has gone through, the screen is still spinning, and nothing has arrived yet. That is the window in which most people make the wrong move. Some tap pay again, some close the tab, some open a fresh checkout from the beginning. All three turn an easy problem into a harder one.

This page sets out the stages a delivery passes through, what can go wrong at each one, how to read an order status, and what to do when you have paid but hold no QR code. We do not quote a fixed number of minutes, because different plans sit behind different suppliers and each downstream provider answers at its own pace. What we can describe is the shape of the process, which is broadly the same wherever you buy.

A successful payment is not a delivered order

The first distinction to hold onto is that a successful payment and a successful delivery are entirely separate states. A successful payment means your bank or payment provider has confirmed that the amount is authorised or captured. A successful delivery means the eSIM profile has actually been issued and the details you need to install it are in your hands. Between those two states sits a queue of work the system still has to do, and that work takes time.

A well-built system never orders a profile from the supplier before the payment is confirmed, because doing so would create ownerless profiles every time somebody abandoned a checkout. Equally, a well-built system never charges twice when a delivery fails. The correct order is: settle the money first, then fetch the goods. If the goods cannot be fetched, the charge has to be reversed or the order put right, rather than leaving the customer holding a receipt and nothing else.

Understanding that changes how you respond to a stalled screen. If you know the money has been taken but nothing has arrived, what is happening is that your order is sitting in the next stage of the queue, not that it has vanished. Paying again at that moment makes nothing faster; it only raises the chance of a duplicate. The right move is to look at the status of the order you already have, not to create another one.

The sequence after you tap pay

The details vary between sellers and between plans, but eSIM delivery generally follows the same skeleton. Knowing that skeleton lets you work out roughly where an order is stuck and what question is worth asking.

1. 1The order is createdThe system records which plan you chose, which destination it covers, and ties that order to your email address. This happens before any money leaves your account, and it is why the email field deserves a second look: everything that follows is sent to whatever you typed there.
2. 2Payment is confirmedThe payment provider replies with an approval or a decline. On approval the order moves to a paid state; on a decline it goes no further. This stage sometimes includes a bank verification step, and closing the window in the middle of it can leave the payment half-finished.
3. 3The profile is requested from the supplierA request goes to whoever actually issues profiles for that destination. This is the stage nobody fully controls, because it depends on someone else's system. Most of the time the answer comes back quickly, but certain destinations or certain moments are slower than usual.
4. 4The profile comes back and is attached to the orderWhen the profile returns, the installation details are stored, both the QR code and the manual fallback fields, and attached to your order. This is the point at which the status changes from processing to ready to install.
5. 5You are notifiedAn email goes out and the order page updates. Email can be delayed or filed somewhere unexpected, which makes the order page the more reliable of the two. If the order page says ready, the profile really has been issued, whether or not the message has landed yet.
6. 6You install and use itDelivery is not really finished until the profile is installed and attaches to a network at the destination. That step sits with you and with your handset, but if installation fails it is still a fulfilment problem that needs resolving.

Reading the order status

Sellers label their statuses differently, but the meanings underneath tend to line up. The table below pairs the labels you are most likely to see with what each one actually tells you and what to do next. If the wording on your screen does not match exactly, look for the row whose meaning is closest.

Why some orders take longer than others

The question we hear most often is why a friend received theirs instantly while yours has not arrived. The answer usually lives in the third stage, the one that waits on somebody else's system. Plans for different destinations can sit behind different suppliers, and each supplier keeps its own rhythm. Sometimes the delay is a queue, sometimes it is maintenance on their side. What nobody can do is predict in advance which destination will be slow and when.

Another common cause is a security review on the payment side. A transaction that looks unusual to the system, such as a card issued in one country being used from another, may be held for a human to look at. That is not an accusation of anything; it is the mechanism that stops other people's cards being used. This kind of check adds time to the second stage rather than the third.

The third cause is at your end: one wrong character in the email address, a full mailbox, or a strict corporate spam filter. In each case the profile really has been issued but the news never reaches you. That is why the order page matters more than the inbox: nothing filters the order page.

You paid and there is no QR: what to do

The checklist below is ordered by what resolves fastest. Work down it rather than jumping ahead, because the item that looks too simple to matter is the one that turns out to be the cause most often.

• Open the order page from the confirmation link or your order history and read the current status.
• Search the mailbox for eSIM or the shop name instead of scrolling, and check the spam and promotions folders too.
• Confirm the address you typed at checkout is spelled correctly, reading it off the order page rather than from memory.
• Look in the banking app to see whether the amount is held or actually charged, because the two point to different answers.
• If the status is still processing, wait, and do not open a second order while you wait.
• If the status says failed, message support with the order number and the time of the transaction.

There are two things not to do. The first is tapping pay again in the hope of speeding things up. The second is opening a fresh checkout and running the whole purchase from scratch. Both create separate orders that the system reads as separate intentions, and if both succeed you end up with two profiles and two charges. That is fixable, but fixing it costs time and a conversation.

Read the install walkthrough before you fly

When delivery fails, where does the money go

This is the question that worries people most when they see the word failed. The principle should be simple: if the goods were not delivered, the money should not be kept. How that plays out depends on which stage failed and on whether the amount was an authorisation hold or a completed charge. The table below sets out the cases you are likely to meet.

Delivery is measured in use, not in email

Some sellers consider the job done the moment the email leaves their server. That is a convenient view for the seller and a false one for the traveller. For somebody standing in an arrivals hall, delivery is finished when the phone has signal and the map opens. Everything before that is just an intermediate step.

In practice there are two gates. The first is having the installation details in hand. The second is having the installed profile attach to a network at the destination. The first can be cleared while you are still at home; the second is only truly proven once the aircraft lands. Sensible planning means clearing the first gate several days early, leaving room to fix anything that goes wrong.

The detail people forget is that installing a profile requires internet access, which sounds circular because internet access is what you are buying. The handset has to download the profile from a server. If you wait until you land and there is no Wi-Fi, you are stuck needing connectivity in order to get connectivity. Install while you are still on a reliable network.

Why buying again is the last resort

When the wait starts to feel long, the instinct is to buy again and be done with it. The trouble is that a new order does not cancel the old one. It is a separate transaction that runs its own sequence, and if the first one succeeds afterwards you have two profiles for one trip and two lines on your statement.

If circumstances really force a second purchase, do two things at once: buy, and immediately send a message saying there are now two orders and which one you intend to use. Flagging it at the time settles the matter far faster than waiting for the statement to arrive and raising it then.

What to have ready before you contact support

A first message that already contains the facts removes the back-and-forth that eats the most time when you are in a hurry. Only a handful of details actually help.

1. The order number, or the email address used at checkout if you cannot find the number.
2. The approximate date and time of the transaction and the payment method used.
3. The status the order page is showing right now, copied as it appears.
4. The make, model and operating-system version of the handset, if the problem is at installation.
5. A screenshot of any error message, since the full wording says more than a description of it.

There are three ways to reach us: LINE at https://lin.ee/skDPoNx, account @esimonline, email at esimonline.asia@gmail.com, and phone at 089-942-0818 or 088-521-6848. We take messages around the clock, every day, though replies can run a little slower late at night Thailand time. If you are travelling overnight, having everything sorted in advance will serve you far better than hoping for an instant reply.

Message us with your order number

How much slack to leave before you fly

We will not promise a number of minutes, because it depends on the destination and the supplier. What we can offer is a planning principle: buy and install while you still have options, not when you have run out of them. The difference between buying two days before departure and buying at the check-in desk is not the speed of the system; it is what you can do if something goes wrong.

For a trip you have planned in advance, settling the eSIM two or three days ahead is a comfortable margin. You have time to read the email, install over home Wi-Fi, confirm the profile appears in the handset's menus, and still ask a question if something is unclear. Last-minute trips are workable too, but accept that if anything goes wrong you will have far less room to fix it.

Three things should be true before you leave the house. The profile is on the phone; you know how you will switch it on at the destination; and you have a copy of the order details somewhere you can open without a connection, such as a screenshot in your photo library. The third is the one people skip, and it is missed precisely when it is needed most.

Fulfilment for top-ups and renewals

Adding data to a profile you already have is also a fulfilment process, but with no new profile to install. What changes is the allowance or the validity attached to the profile already on your handset. The consequence is that no new QR code arrives, and you should not sit waiting for one.

A frequent source of confusion is that a top-up may not appear on screen straight away. The handset shows the figure it has recorded itself, which need not match the network's figure immediately. Toggling flight mode or restarting the phone usually brings the two into line sooner. If nothing shifts after a reasonable wait, report it with the order number of the top-up rather than of the original purchase.

It is also worth knowing that whether a plan can be topped up at all depends on the plan and the supplier. Not every plan supports it, and some allow it only before expiry. Once a profile has expired, buying a new plan is usually the only route. Check this when you choose the plan, if you expect to need more data mid-trip.

Signs of a fulfilment system that works properly

When comparing sellers, people look first at price and allowance, which is understandable. But the quality of the fulfilment process is the thing you only notice when something goes wrong. The characteristics below can be observed before you buy and say a fair amount about how the machinery behind the shop was built.

• An order page you can open yourself, so the email is not the only channel.
• Statuses written in language a customer can read, rather than internal codes.
• A clear statement of what happens to your money if the order does not complete.
• Contact channels that are actually stated, without unconditional promises of always-on replies.
• Manual installation details kept alongside the QR code, not a QR code alone.

That last point is more useful than it sounds, because a QR code needs a camera and a second screen to display it. If you are travelling alone with one phone, typing the server address and activation code by hand is the practical route. The menu for entering those details is named and placed differently by each manufacturer and operating-system version, so find it while you are not yet in a hurry.

What to remember

Fulfilment is the stretch between money leaving and goods arriving. It has several stages and each can fail for its own reasons. What separates a smooth experience from a stressful one is rarely speed; it is knowing where to look and what to do next. People who know where their order page lives almost never hit a problem that cannot be sorted.

If only one sentence survives, make it this: when you have paid and see nothing, check the status rather than buying again. That single habit prevents almost every problem described on this page, and it is why the companion page on duplicate-request protection matters to you directly.