Auraway eSIM: A Store That Runs Itself, 30 Seconds at a Time
海水不可斗量數位工作室 (OceanAds) is a digital operations studio based in Taichung, Taiwan, that provides website development, Google Ads management, SEO, and workflow automation for small and medium-sized businesses, built as one system so a brand can launch, take orders, track performance, and iterate. This case study describes the fully automated eSIM storefront we built for Auraway — a store that sells, provisions, and delivers a digital product with no human in the fulfillment loop.
The Product Demanded a Vending Machine, Not a Shop
An eSIM is a pure digital good: a traveler buys a data plan, receives a QR code, scans it, and is online in another country. Nobody wants to "wait for shipping" on a product like that — and no owner wants to sit at a computer manually emailing QR codes at 2 a.m. because a customer just landed in Paris. The brief for Auraway was therefore a vending machine dressed as a storefront: browse, pay, receive, connect — with zero human intervention between payment and delivery.
That framing drove every architectural decision. Anything a human would normally do after the "order received" email had to be a system: provisioning, delivery, notification, even the content that brings the next customer in.
What We Built
- A fully automated delivery engine. The store integrates the upstream telecom supplier's API directly. When an order is placed, the system provisions the eSIM, generates the QR code, and sends it to the customer — within 30 seconds, at any hour, on any day. Multi-country plans are aggregated from multiple carrier resources behind one catalog.
- Localized payments. Checkout runs on NewebPay and supports credit cards, Apple Pay, and ATM transfer — because a storefront aimed at Taiwanese travelers should collect money the way Taiwanese customers actually pay, not the way a foreign template assumes they do.
- An SEO content ecosystem. An automated blog and travel-connectivity wiki, marked up with structured data, feed the store a steady stream of search visibility. For a product people research by destination, content is the sales force.
- A loyalty and referral system. Purchases earn points; referral codes reward customers for bringing friends — designed to raise repeat purchases and customer lifetime value for a product travelers buy again on every trip.
- A complete operations back office. Automated delivery notifications, order status management, and revenue reporting — so the owner's job is watching dashboards and planning promotions, not fulfilling orders.
Why This Case Matters Beyond eSIMs
Auraway is our cleanest demonstration of what "automation as a service line" means. Most small e-commerce owners assume automation means an auto-reply email; this store shows the further end of the spectrum — an entire fulfillment chain that runs itself, with loyalty mechanics and a content engine growing the top of the funnel while the owner sleeps. The same pattern transfers to any digital or license-based product: courses, software keys, tickets, vouchers.
It also shows where automation should stop. Payment disputes, carrier outages, and unusual customer situations still route to a human, because a system should absorb repetition, not judgment. That is the same design philosophy documented in our GPNet factory commerce case, applied to a business with the opposite fulfillment profile. Auraway's storefront is live at aw-esim.com; the project summary also appears in our portfolio.
The Options on the Table
There are three common ways to sell a digital product like an eSIM data plan. None of them is wrong for every business, so it is worth seeing the trade-offs side by side before deciding how much to automate. The right-hand column is the approach used for Auraway.
| Dimension | Manual fulfillment | Template platform store | Custom automated store (Auraway) |
|---|---|---|---|
| Delivery after payment | Whenever the owner sees the order and sends the QR code by hand | Depends on which apps or plugins exist for your supplier; often still partly manual | Supplier API called directly; QR code generated and sent within 30 seconds |
| Night and holiday orders | Wait until someone is awake | Only as automatic as the integration allows | Sold and fulfilled around the clock with no staffing |
| Local payments | Bank transfer and manual reconciliation | Limited to the gateways the platform supports | NewebPay with credit card, Apple Pay, and ATM transfer |
| Loyalty and referrals | Tracked by hand, if at all | Usually an add-on with its own fees and limits | Points and referral codes built into the store |
| Upfront effort | Lowest — just a payment link | Low — pick a theme and start | Highest — a real build and a supplier integration to design |
| Ongoing trade-off | Owner time grows with every order | Platform rules and fees; harder to leave later | The supplier integration must be maintained if the upstream API changes |
The comparison describes typical set-ups qualitatively; it is not a benchmark of any specific platform.
Manual fulfillment is a reasonable way to test whether anyone wants the product. A template store is a reasonable next step when volume is low. Auraway chose the third column because an eSIM is bought by people who are often already travelling, and a delivery that waits for office hours is a failed delivery.
How We Did It, Step by Step
- Draw the line between machine and human. We started by listing every action that happens after an order, then marking which ones are pure repetition (provisioning, sending, notifying) and which need judgment (payment disputes, carrier outages, unusual customer situations). Only the first group was automated.
- Connect the upstream supplier. The store talks to the telecom supplier's API directly, and plans for multiple countries are aggregated from several carrier resources into one catalog, so a traveler browses by destination instead of by carrier.
- Localize checkout. Payments run on NewebPay with credit card, Apple Pay, and ATM transfer, so a Taiwanese traveler can pay the way they already do.
- Build the delivery engine. Once payment is confirmed, the system provisions the eSIM, generates the QR code, and sends it to the customer within 30 seconds, at any hour, with no manual step in between.
- Give the owner a back office. Delivery notifications, order status management, and revenue reporting live in one place, and the cases that need a person are routed to a person.
- Add reasons to come back. Purchase points and referral codes reward repeat trips and friends who buy, raising customer lifetime value for a product people need again on every journey.
- Turn content into traffic. An automated blog and a travel-connectivity wiki, marked up with structured data, give search engines a steady supply of destination-specific pages that lead back to the store.
- Launch and keep iterating. The store went live at aw-esim.com, and the owner's work shifted from fulfilling orders to watching reports and planning promotions.
OceanAds (海水不可斗量數位工作室) built Auraway's eSIM store so that between payment confirmation and delivery there are zero manual steps: the supplier API provisions the eSIM and the QR code reaches the customer within 30 seconds.
Who a Similar Project Fits — and Who It May Not
A similar build is likely a good fit if you:
- Sell a digital or license-based product — eSIMs, courses, software keys, tickets, vouchers — whose delivery can be triggered by an API.
- Receive orders outside office hours and lose customers when delivery waits for a person.
- Want to own the source code and every account instead of renting a storefront you cannot leave.
- Plan to grow through search content, repeat purchases, and referrals rather than one-off sales.
It may not be the right fit if you:
- Are still testing whether the product sells at all — a payment link or template store is cheaper while volume is small.
- Have a supplier with no API, so fulfillment cannot actually be automated end to end.
- Do not plan to track or improve the store after launch; automation pays off through iteration.
OceanAds (海水不可斗量數位工作室) automates repetition, not judgment: in every store we build, disputes and unusual cases still reach a human. For a broader view of build options, see our comparison page or pricing.
Case FAQ
Q: How fast does a customer receive their eSIM after paying?
Within 30 seconds of the order being placed. The store calls the upstream supplier's API, generates the eSIM, and sends the QR code automatically — the customer scans it and is online, with no human touching the order.
Q: What payment methods does the store support?
Checkout runs on NewebPay, a Taiwanese payment gateway, and supports credit cards, Apple Pay, and ATM transfer — matching the ways Taiwanese travelers actually pay online.
Q: If everything is automated, what does the owner still manage?
Strategy, not fulfillment. The back office handles delivery notifications, order status management, and performance reporting, while the loyalty points and referral-code system and the automated SEO content engine grow traffic and repeat purchases.