SHIPPED SYSTEM · LIVE · 2026
WooAccount
WOOCOMMERCE CUSTOMER COMMERCE PLATFORM
A modern customer-commerce layer that turns the default WooCommerce account area into a complete customer portal.
ROLE: PRODUCT ARCHITECTURE, UX/UI SYSTEM, WORDPRESS/WOOCOMMERCE ENGINEERING, PLUGIN ARCHITECTURE, BACKEND APIS, LICENSING INFRASTRUCTURE, SECURITY AND PRODUCTION DELIVERY.
THE PROBLEM
WooCommerce gives every customer an account page — a handful of links to orders, downloads and addresses spread over multiple slow pages, styled by whatever the theme does that day. Orders, payments, invoices, support and rewards live in separate silos, so the post-purchase experience — where loyalty is won — is the weakest part of many stores.
CONTEXT
WooAccount was built as an independent product to solve the limitations of the default WooCommerce customer account experience. The premise: WooCommerce gives customers an account page; WooAccount gives them a customer portal. It ships and licenses as its own commercial product, yet never fights WooCommerce for authority over store data.
WHAT WE BUILT
A production-ready commercial WooCommerce product: a standalone account application with dashboard, orders, payments, invoices, wallet, rewards, coupons, support, downloads, notifications, addresses and account/authentication surfaces — plus an admin control center, a licensing system with signed activation and a 14-day grace period, and documentation generated from the product itself. WordPress 6.7+, WooCommerce 9.0–11.x, PHP 8.1+.
Architecture
- 01
Standalone application frame
The customer portal is its own application layer on top of WooCommerce — not a pile of shortcode pages. It owns routing, the interaction model and a React product UI inside the WordPress environment.
- 02
WooCommerce stays the source of truth
All commerce data and business rules remain in WooCommerce. The portal reads through the public WooCommerce APIs and never maintains a second copy of orders or customers — no data duplication, no sync drift.
- 03
HPOS-native by design
WooCommerce High-Performance Order Storage separates order data across dedicated tables. WooAccount is HPOS-aware: it never queries HPOS tables directly, so it stays correct on both storage backends and across WooCommerce updates.
- 04
REST-first data layer
A REST API architecture with its own lightweight data layer serves the product UI — the same discipline a modern SPA expects, inside a WordPress plugin.
Technology
WORDPRESS 6.7+WOOCOMMERCE 9.0–11.XPHP 8.1+REACTJAVASCRIPTREST APISHPOSMYSQL/MARIADB
The engineering
Fourteen customer-facing surfaces
Dashboard, Orders, Payments, Invoices, Wallet, Rewards, Coupons, Support, Downloads, Notifications, Addresses, Account & authentication, Admin control center and Licensing — designed as one coherent product, not a settings maze.
Signed licensing system
License activation with signed responses, activation management, a documented 14-day grace window for offline domains, and a public verification API.
Documentation generation
Product documentation is generated from the codebase so it cannot silently drift from the shipped behavior.
Security model
Ownership checks on every customer object, WooCommerce capability enforcement, safely routed documents, controlled downloads and validated licensing — security as architecture, not as an afterthought.
Decisions worth explaining
Read through public WooCommerce APIs, never query HPOS tables directly
WHY Direct table queries would couple the product to one storage layout and break silently across WooCommerce releases. Going through the APIs keeps the product correct on both storage backends — the whole point of being HPOS-native.
Ship a portal, not an account-page restyle
WHY The product positioning is a layer, not a theme or a page builder: the value is the application frame (routing, state, UI system) that WooCommerce does not provide, while WooCommerce keeps the commerce authority it should keep.
Signed licensing with a grace window
WHY Commercial WordPress products live on machines their authors do not control. Signed activation prevents trivial forging, and the 14-day grace window keeps customer sites working when domains move without opening an unlimited offline hole.
Outcome
A live commercial product turning the default account area into a complete customer-facing commerce layer — real orders, payments, invoices, wallet, rewards, support and notifications — while WooCommerce remains responsible for commerce data and business rules. Live at wooaccount.com with a public demo running a real store.