Ecommerce: From WooCommerce Stores to Static Checkout

I run WooCommerce stores for a handful of fashion and lifestyle brands, and Woo earns its place: a familiar back office and a plugin for every shipping and tax rule. But for a small, brand-led catalogue it is a lot of moving parts to patch, cache and secure on a site that is now taking payments. I wanted the option of a store with almost no attack surface and edge-fast pages, without giving up a real catalogue, cart and checkout.

So I built an ecommerce module into Orbit: native static commerce, not a headless WordPress. Products, variants and categories live in Orbit, then render to a static storefront on Cloudflare's edge driven by a single vanilla-JavaScript file. Checkout runs on Stripe, on the client's own account, and the server reprices every line against the database so a tampered cart cannot be charged.

• Catalog with variants, categories and AI-drafted product descriptions
• Cart, wishlist and mini-cart from one store.js, no framework
• Hosted Stripe checkout, orders with a seven-state fulfilment flow and stock decrement
• A WooCommerce importer that pulls an existing store in over the REST API

The first WooCommerce to Orbit conversion is underway now: a 46-product fashion store rebuilt on staging at meloana-store.pages.dev, imported straight from the live Woo catalogue, with the production domain still on WooCommerce until the switch is signed off. I am unromantic about the choice. Woo stays where a big catalogue and a trained team make it right; static checkout is for the brand-led shops where speed, security and a bespoke buying flow are the whole pitch.