“We want a dashboard” is one of the most common requests in WooCommerce projects — and one of the most misunderstood. A dashboard is not a pile of widgets; it is an answer to the question “what should I look at first?”. For a customer, that question has a short list of honest answers.
The six elements that earn their place
1. The active order
One order, chosen by status priority — processing before completed, pending payment above all. Show state in customer language and the tracking link the moment it exists. This single element is the reason most customers open the account area at all.
2. Pending actions
Unpaid orders, incomplete account details, expiring cards on subscriptions. A dashboard that surfaces actions instead of data converts itself from decoration into a working surface — the pay-pending-order link alone often recovers real revenue.
3. Recent orders, compact
Five rows, not a paginated table. Each row: number, date, status chip, total, one-tap open. Dense beats exhaustive; history lives behind a “view all”.
4. Balances and credits
Wallet balance, reward points, active coupons — if the store runs any of these programs, the balance belongs on the first screen. Invisible balances don't drive repeat purchases, as covered in the retention breakdown.
5. Open support threads
A ticket with a new reply is a notification; the dashboard should show it like one. This closes the loop between “something is wrong” and “the store is already on it”.
6. Downloads, when relevant
For stores with digital goods, the latest three downloads with expiry states. For stores without them — omit entirely; nothing reads “template” like a Downloads card with a zero.
The three things to delete
- Welcome hero text. “Welcome back, Sara!” costs a full screen height on mobile and answers no question.
- Account-completion nagging. One quiet checklist is fine; a modal is not.
- Marketing banners. The account area is not a billboard; it's where trust is maintained. Promotions there read as desperation.
Hand your phone to someone who just ordered. Ask them to find their delivery estimate. If they hesitate longer than a second, the dashboard has failed regardless of how it looks.
How to tell if it's working
You don't need an analytics stack for this — two numbers suffice. Sessions that touch exactly one screen and leave (should fall as the dashboard absorbs single-purpose visits), and support tickets asking about order status (should fall because the answer is on the first screen). The WooAccount dashboard was built around exactly these six elements, and the demo lets you feel the difference in a minute. If you maintain the default page instead, the same principles apply — start by demoting everything that isn't answering a customer question, as outlined in the account experience checklist.