WooCommerce GoCardless saves the mandate id, payment id, and customer reference into order meta on every Direct Debit checkout. On HPOS stores these live in wc_orders_meta under keys like _gocardless_mandate_id, _gocardless_payment_id, and _gocardless_customer_id. The default Orders screen never shows them, so checking whether a mandate is active or pending submission means opening each order one at a time.

SleekView reads those keys as real columns alongside the order total, status, and customer email. Mandate tokens stored in woocommerce_payment_tokens and woocommerce_payment_tokenmeta join in too, so a single view can show every active customer with their mandate status, last collection date, and outstanding balance. Payout reconciliation becomes a sort on payout id rather than a CSV export from the GoCardless dashboard cross-referenced against WordPress.

Inline status edits route through WooCommerce CRUD, so woocommerce_order_status_changed still fires when you bulk-flip a batch of submitted Direct Debit orders to processing after the GoCardless webhook confirms them. The plugin's own webhook handlers continue to run; SleekView just gives ops a row-level view of the same data the plugin already writes.

Direct Debit settles slowly. Unlike a card charge that confirms in two seconds, a GoCardless payment moves through submitted, confirmed, paid out, and (sometimes) failed over a window of business days. The default WooCommerce Orders screen does not model that timeline.

It shows order status and total, not mandate status, not payout id, not the gap between submission and confirmation. Finance teams reconcile by exporting from GoCardless and grep-ing through WordPress, support teams handle "is my Direct Debit set up" calls by opening each order one at a time, and risk teams spot failed-DD patterns only after the chargeback. SleekView reads the data the plugin already writes (_gocardless_mandate_id, _gocardless_payment_id, mandate state, payout reference) and turns it into the workspace each team needs.

Same database, same hooks, the same webhook handlers running unchanged. The change is just that the meta keys finally show up as columns ops can sort, filter, and update.