Online shop starter
Products, cart, checkout and an admin of your own. Start with PromptPay and a theme you can make yours. When your business outgrows the starter, the code is there for a custom payment, order flow or storefront.
Talk through your shop See what you can change
A focused Thai commerce starter for businesses that want a working shop, not a mock-up.
A theme decides the type, the spacing and the shape of things — not a different shop. Switch it whenever you like; nothing is rebuilt and nothing is lost.
Six colours, a logo, the shop's name and slogan in Thai and English, your LINE and socials, and the tags you advertise with. Press save, refresh the shop, and it is already different — no rebuild, no deploy, nobody to ask.
แบรนด์และธีม
Saved. Refresh the shop to see it.
There are two kinds of change. Mixing them is how a shop becomes hard to run: an owner should not need a developer to change a colour, and a payment gateway should not pretend to be a toggle.
Owner settings · no deploy
Choose a shipped theme, then set its colours, logo, copy, promotion bar, PromptPay details, social links and marketing IDs from the admin.
Developer extension · versioned and deployed
A custom theme, Stripe or another gateway, a LINE notification, or a sync to an ERP is code in your shop repository. It is reviewed, versioned and deployed with the shop — never pasted into an admin box.
The first release ships PromptPay, bank transfer and cash on delivery. If you need a particular payment gateway or order connection, tell us before launch — we will scope the extension against the real workflow, rather than promise a one-click integration that does not exist.
A PromptPay QR is a string, not a gateway. The bank app reads where the money goes and how much straight out of it, and the transfer is between your customer's account and yours. There is no third party in the middle, so there is nobody to pay and nobody to sign with.
The shop draws the QR itself from the PromptPay number you typed into the admin, with the amount already in it. The customer scans, transfers, and sends you the slip.
Your account number, the name on it and the exact amount, shown on the order page — so nobody has to ask you for it in a message at midnight.
For the customers who will not transfer first. The amount to collect is on the order, and the courier hands it over.
It does not check with the bank that the money arrived. The customer attaches the slip to their own order, you look at it next to the amount, and you press confirm. That is the moment the shop records the money as taken. Slip-checking APIs are sold to registered companies — something your shop may have one day, and not something a starter may assume.
One link, kept from the moment they order. They see where it is without messaging you, and you stop answering the same question all day.
The order exists the moment they press the button. They get the PromptPay QR with the amount in it, or your bank details, or nothing at all if they are paying the courier.
They photograph the transfer and attach it to their own order. It lands against the amount, where you can see both at once.
You look at the slip and confirm. The shop records the money as taken, and the customer's page says so without you sending anything.
You put in the courier and the tracking number. It appears on their page as a link they can follow — Flash, Kerry, J&T, ไปรษณีย์ไทย, whoever you use.
The order closes. It stays in your admin with everything that happened to it, which is what you will want when somebody asks in March about January.
Stock comes down as orders come in, so the shop stops selling what you have run out of. Discount codes and campaigns are built in. Receipts are there to print.
The shop is yours: the code is handed over on request, the database is yours, and the customer records in it are yours — Erawan holds them for you and is not the one who decides what happens to them.
Tell us what you sell, how you collect payment, and where orders need to go. We will show the starter flow and name the parts that need custom work.
curl -fsSL https://erawan.cloud/install | sh
erawan deploy --app medusa --name myshop \
--env STORE_URL=https://myshop.erawan.app \
--env ADMIN_EMAIL=you@example.comErawan asks you to set four passwords in your browser before it starts — they never pass through anything else. Then the shop is at myshop.erawan.app and the admin is at myshop.erawan.app/app.