In the Werx | 002: Stormfront Commerce what “beta” means for you
Date Published
Stormfront is Thunderwerx’s commerce module: products, cart, checkout, and order flows that sit on the same ThunderBolt CMS tenant as your marketing site. One admin, one theme system, one place to manage what you sell.
Today Stormfront is in beta. “Beta” here means the core paths are built and dog‑food tested on internal and friendly‑client stores, but we are still stress‑testing edge cases: tax and shipping rules across regions, high‑traffic sale days, refund and partial‑capture flows, and third‑party payment quirks. We expect rough edges; we do not expect you to discover fundamental architectural gaps. Those were settled when we designed Stormfront alongside our multi‑tenant data model.
What you get in beta: a real storefront you can link from live pages, real payments in sandbox or production (depending on agreement), inventory and product management inside Payload, and the same Anvil‑backed hosting story as the rest of our web stack. What is still tightening: operational runbooks, self‑serve toggles for every payment provider, and polished reporting exports.
If you are on Growth or Scale and commerce is in scope, ask us whether your use case fits the current beta matrix (SKU count, fulfilment model, UK/EU vs global). We may enable Stormfront per tenant with a short checklist rather than a public self‑serve switch until we call it 1.0.
For everyone else: ThunderBolt CMS and Package Builder remain the stable, general‑availability path for brochure and lead‑gen sites; Stormfront is the optional layer when you are ready to sell online. Next up in In the Werx: ThunderPOS (ePOS), point of sale in development, not yet a SKU you can buy.