WooCommerce Purchase Order Gateway is the official Woo.com payment method that accepts a customer-supplied PO number at checkout and leaves the order in on-hold until the merchant collects payment offline. Every order writes the PO number to order meta, the gateway slug to payment_method, and the on-hold-to-processing transition is timestamped. That is exactly the data an AR aging report needs, and exactly the data the default orders screen makes hard to filter.

SleekView reads wp_wc_orders filtered to payment_method equals purchase_order and renders PO, Customer, Total, Status, Created, Days outstanding and Paid as sortable, filterable columns. Filter to status equals on-hold and total over $500 for the next collections queue. Sort by days outstanding descending for the past-due list. Group by customer to see who is the slowest payer without building a pivot in a spreadsheet.

The gateway keeps owning the PO checkout flow, on-hold transition and the order notes that accompany payment. The table view owns the audit surface, so the same orders the gateway flagged become an AR-ready grid finance and account managers can open on Monday morning.

B2B WooCommerce stores live on AR aging and collection priority, and Purchase Order Gateway already captures the data both need: PO number, customer, total, on-hold status and timestamps for created and paid. The default orders screen is fine for processing the next order and clumsy for managing a portfolio of open POs across thirty customers. SleekView reads the same orders the gateway flagged and renders PO, customer, total, status, days outstanding and paid as a sortable, filterable AR grid.

Filters stack so the collections queue, the past-due cohort and the per-customer brief become one-click views. The gateway keeps owning the checkout method; finance, sales and operations get the per-row surface the dataset always deserved.