
Every WooCommerce order edit screen tells you what was ordered and how much it cost. It tells you almost nothing about who placed the order.
Repeat Customer adds a Customer metabox to the order sidebar showing key metrics for the customer behind the order – all computed locally from your existing WooCommerce data, with no external services.
Metrics displayed:
Why this matters:
When your team is packing order #4832, they have no quick way to know that this customer has been buying from you for two years, has placed 14 orders, and spends an average of 85 per order. That context changes how you handle the order – whether you include a thank-you note, prioritise dispatch, or flag it for a personal follow-up.
Repeat Customer makes that information visible where fulfilment decisions are actually made – on the order edit screen.
Guest customer matching (v1.1):
Not all customers create accounts. Repeat Customer identifies returning guests by matching billing email, phone number, or company name against previous orders. A softer postcode match is also available for stores where address patterns matter. Each match strategy can be enabled or disabled individually from WooCommerce > Settings > Advanced > Repeat Customer.
Visual order history timeline (v1.1):
A proportional horizontal timeline shows all matched orders as clickable markers spaced by real elapsed time. A loyal customer with regular monthly orders looks visually different from a one-time buyer who last ordered three years ago. Hover for order details, click to jump to any previous order.
Orders list column (v1.1):
A lightweight “Customer” column on the WooCommerce orders list shows order count and lifetime value at a glance. First-time customers show as “New customer”. Guest matches via postcode are prefixed with a tilde to indicate the softer signal.
Key features:
Privacy:
No data is transmitted externally. All metrics are computed from your existing WooCommerce order data. The plugin makes read-only queries against WooCommerce orders and caches results using WordPress transients.