The Cart and Checkout blocks have become the canonical front end for most modern WooCommerce stores. Each completed order still lands in wp_wc_orders on HPOS or wp_posts on legacy, with checkout context written to wp_wc_orders_meta: source URL, created_via flag, shipping method, customer note. The standard Orders screen exists, but it treats Blocks orders identically to admin-created ones, with no column for the entry page or the front-end block that produced the cart.

SleekView reads wp_wc_orders directly and pulls the Blocks meta keys onto the same row. created_via separates checkout-block orders from REST API, admin-created or subscription-renewal orders. Source URL turns a date-sorted order list into a per-page conversion audit. Shipping method joins the row so finance can spot which rates customers actually pick at the Checkout block. The same orders that feed the chart dashboard now read as rows.

The plugin keeps owning the Cart and Checkout blocks on the front end. SleekView owns the audit surface, so the order data the new checkout writes stops hiding inside per-order panels and becomes a sortable, filterable table.

The Cart and Checkout blocks have replaced shortcode checkouts on most modern WooCommerce stores, and each one writes useful context per order: created_via, source URL, shipping method, customer note. The default Orders screen treats every order identically, with no column for the front-end block that produced the cart, no filter to isolate Checkout-block orders and no per-page conversion audit. SleekView reads wp_wc_orders (or wp_posts on legacy) and pulls those meta keys onto each row, so a shop manager can filter to block-driven orders, a marketer can sort by source URL, a theme builder can prove block adoption across templates.

The plugin keeps owning the Cart and Checkout blocks on the front end, while operators get the per-row audit surface block orders always deserved.