YITH WooCommerce Product Bundles defines each bundle as a product with bundled-item postmeta and writes the bundled items as line meta on every order that includes one. The default WooCommerce orders screen treats a bundle like any other product line, which is right for fulfilling one order and wrong for almost every operational question about which bundles drive revenue, which child items move together and how seasonal the bundle program is.

SleekView reads wc_orders joined with wc_order_items and wc_order_itemmeta, parses the YITH bundle meta keys and exposes parent bundle, child SKU, bundle total and order status as columns. Filter to one bundle to scope to its order history. Sort by bundle total to surface high-value lines. Group by child SKU to see which products move attached to which bundles.

The plugin keeps owning bundle definition, cart logic and child rules. The table view owns the audit surface, so the bundled lines YITH already records become a queryable cohort instead of a string buried under each order.

Bundles change the economics of a catalog: child SKUs that wouldn't sell alone move because they ship attached to a hero product, and revenue per bundle often differs from the simple sum of its parts. Default WooCommerce reports treat bundles like any other product, which loses the entire story. SleekView reads wc_order_itemmeta where YITH records each bundled line and renders bundle name, child SKUs, bundle total and order status as real columns.

Filters stack so the bundle leaderboard, the refund cohort and the fulfilment pick list all become one-click views. The plugin keeps owning the bundle definition and cart logic, while merchandising, finance and operations get the per-row surface the order tables always implied.