WooCommerce Purchase Orders adds a PO gateway that writes the PO number, billing account, and approval status to wp_postmeta (or order meta on HPOS) using keys like _po_number, _po_account, and _po_status. Each order moves through pending, approved, and invoiced states with the date of each transition logged in the plugin's PO log table.

SleekView joins the order to its PO metadata and the latest approval-status row from the PO log. A single row exposes order, PO number, billing account, order total, PO status, due date, and the approver. Filter by _po_status to find the pending queue, sort by due date ascending to plan invoicing, or filter overdue POs for collections outreach.

Inline edits move a PO through its approval states via the plugin's wc_po_set_status hook so any AR or buyer notification fires correctly. Bulk operations let you approve a vetted account's batch, send invoices for a cohort of approved POs, or mark a group as paid after a bank reconciliation, with each change logged for audit.

Purchase order workflows are fundamentally a piece of paperwork that needs to move through an approval chain on a deadline. The buyer issues the PO, the seller waits for AR to approve, an invoice gets generated, and payment lands days or weeks later under the negotiated terms. Each step has its own state, and each state has its own operator and timestamp that the audit team will eventually ask about.

WooCommerce Purchase Orders captures the workflow in _po_status meta and the wp_wc_po_log table, but the default WooCommerce admin treats a PO as a standard order with the PO context tucked behind the edit screen. SleekView joins the order to its PO meta and the approval timeline, exposes due date and status as sortable columns, and gives sales ops, finance, and support each a view tuned to their workflow. The PO program scales: as PO volume grows the operators' daily working list gets faster, not slower, because the right saved view shows them only the rows they need to touch today.