WooCommerce Shop as Customer (the official Woo.com extension) lets admins and shop managers log in as any registered customer to place orders or troubleshoot a cart. Each session is logged on the originating admin user, and every order placed inside the session is tagged with the _created_via_shop_as_customer meta plus the original admin user ID. The plugin surfaces a toggle on the user list, but the trail of who impersonated whom and what they bought is not a table anywhere in the admin.

SleekView reads wp_wc_orders and wp_wc_orders_meta, filters to orders carrying the impersonation flag, and renders admin user, target customer, order id, total_amount, status and date_created as sortable, filterable columns. Filter to orders placed in the last 7 days for support QA. Sort by admin to spot which agents drive most assisted checkouts. Group by customer to see which buyers received the most assisted orders.

The extension keeps owning the impersonation flow, role checks and toggle UI. The table view owns the audit surface, so the meta the plugin already writes stops hiding inside one-off order screens and becomes a query the compliance and support leads can actually open.

Shop as Customer is one of the more sensitive Woo extensions because it lets staff act as real buyers, and the plugin already records which admin started which session and which orders followed. The default surface tucks that signal behind a toggle on the user list, which is right for starting a session and wrong for almost everything compliance, support QA or finance actually do with the data. SleekView reads the same flagged orders and renders them as a queryable audit table with admin, customer, order id, total, status and date_created.

Filters stack into a single query so the per-agent review, the high-value cohort and the compliance trail become one-click views. The extension keeps owning the impersonation flow and role checks, while the team gets the per-row surface the dataset always deserved.