How to add eSIM to a travel booking flow

The most useful eSIM offer arrives after the traveler commits to the trip. The destination is known. The dates are known. The next question is data.

A booking flow already holds the facts that a plan needs. The work is to place the offer at the right moment, pass the right data, and give the traveler a clear install path.

Place the offer after the booking

The post-booking page is a high-intent moment. The traveler has paid for the flight or the hotel. A data plan is a small add-on with a clear benefit.

The pre-trip email is the second good moment. It arrives when the traveler prepares the trip and has time to install the eSIM. The check-in flow is a third moment, and a good one for a traveler who books late.

Do not place the offer before the traveler chooses a destination. The message is too early, and the plan list is too broad.

Pass four facts

The checkout needs four facts:

1. The destination.
2. The start date.
3. The end date.
4. The order reference.

With these facts, you can show a plan that fits the trip. Without them, the traveler has to choose from a long list. The eSIM API matches plans to the destination and the days, and keeps your booking reference on the order. The booking flow use case shows the plan card step by step.

If the trip crosses a border, pass the full route, not only the first stop. A regional plan can cover the route, and a local plan can leave a gap.

Show the total price and the install step

Show the total price, the data amount, and the validity. Say that the eSIM is data-only when that is true. Do not add a second price at the checkout.

Show the install step before the traveler pays:

• The phone must be unlocked and support eSIM.
• The eSIM installs from a QR code or an install link.
• The traveler can install it before departure over Wi-Fi.
• The home SIM stays in the phone.
• More data needs a new eSIM.

A short phone check removes most failed installs. Link to a guide for the phone maker, or show the settings path for the two main phone systems.

Keep the offer small

The add-on should not compete with the booking. Use one card, one plan, and one action. Put the details behind a link.

A good card answers four questions:

• What data does the traveler get?
• For how many days?
• What does it cost?
• When and how does it install?

A long plan list belongs on a separate page, not in the booking confirmation.

Deliver the eSIM

The traveler can get the eSIM in three ways:

• On the confirmation page: show the QR code and the install steps at once.
• By email: send the QR code or install link with the booking documents.
• In the account: keep the eSIM with the trip and let the traveler open it later.

Do not put the eSIM QR in a forwarded email if the order is not paid. Do not print the QR. For a desk sale, use a one-time voucher and let the guest redeem it. The digital vouchers page shows that flow.

Plan the support path

A failed install is a product event. The traveler needs a first answer that does not depend on the booking agent.

• Link to the install guide on the confirmation page and in the email.
• Give a support contact with the order reference.
• Let support resend the eSIM or check the order status.
• Set a refund rule for an eSIM that was never installed.
• Keep the booking agent out of the technical support path where possible.

Measure the right events

Measure the steps that show whether the offer works:

1. The plan card is shown.
2. The traveler opens the details.
3. The traveler starts the add-on.
4. The payment completes.
5. The eSIM is delivered.
6. The eSIM is installed.
7. The traveler asks for help.

The last two events show where the product breaks. They matter more than the click.

Common mistakes

• A plan list that does not match the trip dates.
• A price that changes at checkout.
• No phone support check.
• No support path when the install fails.
• A promise of coverage that the plan does not have.
• A QR code in an email that anyone can forward.
• No new eSIM for a trip longer than the plan.

A simple flow

1. The traveler completes the booking.
2. The confirmation page shows one plan that fits the trip.
3. The traveler checks the phone and adds the plan.
4. The payment completes in your checkout.
5. The eSIM appears on the page and in the email.
6. The traveler installs it before departure.
7. Support can find the order by your reference.

Sources and checked

• Apple Support, About eSIM on iPhone, checked 27 October 2026.
• Information Commissioner's Office, UK GDPR guidance and resources, checked 27 October 2026.
• RoamWorks booking and delivery notes, checked 27 October 2026.

Talk to us about the booking flow and the data you already hold. The contact page starts the fit call.