The Coinbase Commerce WooCommerce gateway persists each transaction's Coinbase charge code, selected coin (BTC, ETH, USDC, LTC, etc.), confirmation state, and refund references on the order row via WooCommerce order meta. With HPOS enabled, that data lives in wc_orders_meta against wc_orders; on legacy stores it sits in wp_postmeta against shop_order posts.

The default WooCommerce orders screen shows none of those identifiers on the row. There's no column for the charge code, no coin column, and no way to filter to charges awaiting blockchain confirmation. Reconciling against Coinbase Commerce's dashboard currently means CSV export plus spreadsheet joins, one row at a time.

SleekView reads wc_orders joined with wc_orders_meta and surfaces the Coinbase charge code, coin, and confirmation state as first-class columns. Sort by charge code to match Coinbase Commerce's dashboard, filter by coin for per-asset reconciliation, and inline-edit status with gateway hooks intact.

Coinbase Commerce orders carry a different operational shape than card-based gateway orders: each charge has a coin selection, a confirmation lifecycle tied to blockchain finality, and an expiry window for unpaid charges. The default WooCommerce orders screen does not surface the charge code, coin, or confirmation state on the row, so finance teams reconcile by exporting CSVs and joining against the Coinbase Commerce dashboard in a spreadsheet. SleekView reads wc_orders joined with wc_orders_meta and puts the charge code, coin, and confirmation state on the row.

Per-coin views let finance close by asset. Awaiting-confirmation charges become a saved triage filter for ops. Expired charges become a cleanup queue.

Inline edits route through the gateway's CRUD so confirmation, expiry, and refund hooks fire as expected. The merchant still has the standard Orders screen if they prefer it; the crypto audit surface is what changes for finance, fulfilment, and support.