The portal, not a page
The origin argument for WooAccount: the account area is the most-visited authenticated surface in e-commerce, and it deserves the same design rigor as checkout.
8 articles tagged with this topic.
The origin argument for WooAccount: the account area is the most-visited authenticated surface in e-commerce, and it deserves the same design rigor as checkout.
Everything the account area should get right in 2026 — session security, HPOS-safe customization, accessibility, honest states, RTL — condensed into one audit-ready checklist with links to the deep dives.
From confirmation to delivery to the second purchase: designing the post-purchase window in WooCommerce with status honesty, invoices, wallet refunds and support that starts where the order left off.
WISMO tickets, refund requests, invoice demands and login loops: where support friction actually comes from in WooCommerce, and the self-service patterns that remove it — with numbers to watch.
A developer's tour of every legitimate way to change the My Account page: endpoint registration, template overrides, the woocommerce_account_content hooks, and when a full portal replacement beats DIY.
Repeat revenue is won in the account area: order history that invites reorders, store credit that returns to spend, rewards that are visible, and support that closes the loop. A practical map of post-purchase retention.
From login flow to order tracking to self-service refunds: a practical checklist for stores that want the account area to stop leaking goodwill, ordered by effort and impact.
The default WooCommerce My Account page lists endpoints. A customer portal answers questions. We compare the two surfaces side by side — information architecture, mobile behavior, self-service and the numbers that move.