Skip to content

E-commerce site

Products, payments and shipping notifications, done in one go

Self-built or open-source-based shops: products and stock, Taiwanese payment gateways (ECPay, NewebPay), e-invoices, logistics, LINE notifications and a back office. We run an e-commerce business ourselves and know where it gets stuck.

A good fit when

  • You have products and customers and want your own brand store
  • Need Taiwanese payment, e-invoice and logistics integrations
  • Want LINE for after-sales and re-marketing

Not a fit when

  • Only need to list on Shopee or other marketplaces
  • Products and supply are not confirmed yet

What you get

  1. 01A transactional store with back office
  2. 02Payment, e-invoice and logistics integrations
  3. 03Order notifications and reports

Related articles

Write-ups on our founder's blog, covering how it was done and the problems along the way.

Related work

Systems we run ourselves or have published that are the same kind of thing as this service.

  • eSIM 226 storefront

    E-commerce

    eSIM 226 storefront

    A travel eSIM store in eight languages with multi-currency pricing and two Taiwanese payment gateways. Paid orders are provisioned with the upstream supplier automatically and the install email goes out on its own.

    • Eight locales and multiple display currencies, so Japanese buyers see yen
    • Automatic provisioning across two suppliers, with failover

    Next.js · PostgreSQL · Keycloak · ECPay/NewebPay · Kubernetes

    See insideE-commerce siteVisit site
  • eSIM back office

    Admin system

    eSIM back office

    The operations side of the same store: products, pricing, orders, refunds, suppliers and payments in one place. It actively surfaces problems like "paid but never fulfilled" instead of waiting to be asked.

    • Orders, revenue, unpaid and unfulfilled counts at a glance
    • AI pricing suggestions and bulk listing changes

    Next.js · PostgreSQL · Keycloak · GA4 Data API

    See insideE-commerce site
See all work

Frequently asked

Yes. We recommend by scale: customised open source for small catalogues, custom build when deep integration is needed.