Orbit Commerce
We run WooCommerce stores for a handful of fashion and lifestyle brands, and we built a native static commerce module into Orbit for the shops that want edge-fast pages instead. Catalog, cart and Stripe checkout, no WordPress underneath.
WooCommerce 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.
We 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 we 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 34 KB vanilla-JavaScript file that runs cart, wishlist and mini-cart with no framework. 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. Orders follow a seven-state fulfilment flow with stock decrement, product descriptions are AI-drafted, and a WooCommerce importer pulls an existing store in over the REST API.
The first WooCommerce to Orbit conversion is underway: 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. We are 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.
- WooCommerce store builds & maintenance
- Static storefront module for Orbit
- Catalog, variants & AI-drafted product copy
- Stripe checkout on the client's own account
- WooCommerce migration over the REST API
- Live at doselabel.com ↗
A storefront with almost no attack surface.