A customer’s third order lands in your admin. Before HQ, you’d click into the order, half-remember who they were, open another tab to find their billing email, click through to past orders, come back, lose your place. After HQ, you click their name in the order and land on their Tracksies profile: six previous orders, VIP status, a “prefers card packaging” note from last year, three tags they’ve earned, an alias on file for their work email.
The story is already there. You just read it.
What’s on the profile
The page opens with the customer’s name, email, and a status badge (Active, VIP, Caution, or Do Not Serve). Under that, four key numbers: total orders, lifetime value, average order value, first order date. Then the tags they’ve earned across your enabled channels.
Scroll down: their full order history, their interactions timeline (notes, messages, returns, anything your team has logged), any linked accounts (households, partner businesses, related customers), any aliases you’ve recorded. Everything HQ has collected, stitched together on one page.
Where profiles appear
- Tracksies > Customers: the full list, searchable, filterable by status.
- Order edit screen: the Intel Panel surfaces the key profile fields beside every order, so you never need to open a second tab to remember who you’re dealing with.
- Packsie packing card: customer context rides on the packing card too, trimmed down to what a packer actually needs.
What profiles help you do
Treat repeat customers like you remember them. A customer who mentioned a preference six months ago is still that customer today. The profile makes sure you don’t start over each time they get in touch.
Onboard staff without a handover. A new packer opens a profile and sees what matters (status, recent orders, notes) without asking you. Training by doing the work.
Handle escalations with the full picture. When something goes wrong, the full customer context is one click away, not three Slack threads and a memory check.
Stay out of the inbox. Your shop’s customer context lives in one place, not scattered across email folders, Post-it notes, and someone’s head.
If you’re weighing this up against a CRM like FluentCRM or Jetpack CRM
FluentCRM and Jetpack CRM are full CRM platforms: contact lists, segmentation, email campaigns, pipelines, tasks, deals. The CRM becomes the centre of your customer data, with WooCommerce plugged in through an integration. If you need the full CRM toolkit (campaigns, sales pipelines, tasks, sequences), they’re the established fit.
Tracksies customer profiles live inside your WooCommerce admin: they read from your WC orders natively and surface as context wherever you already work (order screens, packing cards, the customers list). No separate CRM app, no data-sync layer, no second tool for your team to learn.
If you want the full CRM machinery, a dedicated CRM is the right call (and HQ can sit alongside it, no conflict). If you want rich customer context that lives inside the admin you already use, profiles are built for that.
Why shops keep them open
Customer profiles are the part of HQ that rewires the day-to-day. After a few weeks of having the context on-screen, handling customer work without it feels like typing with oven mitts on. The profile is just there, ready, and your team works from it.