
EmDash is a CMS, not a commerce platform. It ships no cart, no checkout and no orders, and its page for WordPress developers says nothing about WooCommerce. To sell with EmDash you have to pick a path. We have worked with three while building our templates and client sites; this article says what each one asks of you.
Path 1: a shop run from EmDash
This is what our Shop plugin does, and the Kai template is built around it. Everything lives in the EmDash back office:
- products, on the WooCommerce model: simple, grouped or with variations, virtual or downloadable;
- stock counted per product and per option: a paid order counts it down, a sold-out product can no longer be bought;
- orders, customers, shipments and invoices, with prices shown with or without VAT;
- payment through Stripe, or PayPal or SumUp when the site has no Stripe key;
- shipping through Colissimo (labels and pickup points), Mondial Relay, or your own rates by weight.
Around it, the plugins that help you sell more: promo codes, gift cards, loyalty, abandoned cart reminders through Brevo, sales statistics. All of them ship in the seven templates with the Kailua 3 licence, and each one is switched on from the Plugins page.
What this path needs: a Cloudflare account, since the shop runs on a Worker with a D1 database, and an account with the payment provider you choose, whose key is pasted in the back office.
Path 2: keep WooCommerce, change the storefront
If the shop already runs on WooCommerce and its orders, stock and extensions suit you, nothing forces a full migration. The Nalu template is an Astro storefront in front of an existing WooCommerce shop: one address to fill in, and the public pages move to Astro. Orders, payment and stock stay with WooCommerce. The Headless shop plugin does the same for a Shopify shop.
It is the lowest-risk path: nothing to migrate on the commerce side. The WordPress install is still there to maintain.
Path 3: write your own commerce layer
It can be done, and it is a real project: a cart, a checkout that checks amounts on the server, a signed payment webhook replayed without duplicates, numbered invoices, VAT, refunds, admin screens. In EmDash those screens need a native plugin, which runs in the same process as the site and has to be reworked at each EmDash release. The EmDash plugins guide explains sandboxed versus native.
What stays the same on every path
- The catalogue can stay static. Our templates build two ways from one repository: engine off, the catalogue is plain HTML; engine on, the checkout opens. A shop can start as a fast catalogue and switch on sales when it is ready.
- Backups are planned before the first sale. On an EmDash D1 database,
wrangler d1 exportfails because of the search tables; the recovery point is D1 Time Travel. Details are in EmDash 1.5.0: what the release changes for a theme. - Migration moves content, not the shop. The EmDash WordPress importer brings posts, pages, menus and media; WooCommerce products, orders and customers are a project of their own.
Where to start
- For a shop run from EmDash: the Kai demo.
- To keep WooCommerce: the Nalu demo.
- To weigh the decision against WordPress: Astro + EmDash vs WordPress for a shop.
Both templates and the sales plugins are in the Kailua 3 licence, detailed on the EmDash templates page.




