WooCommerce Product Bundles stores every bundle as a WooCommerce product with the bundle product type and the child item definitions in the wp_woocommerce_bundled_items and wp_woocommerce_bundled_itemmeta tables. Each bundle row in wp_posts carries a post_status of draft, pending, publish, or private, plus metadata in wp_postmeta for the bundle's pricing rules, layout, and discount. The native admin lists every product together, which makes it hard to see which bundles are queued behind a launch versus already live on the storefront.

SleekView Kanban reads the same bundle product rows you would query with WP_Query filtered to the bundle type. Pick post_status as the group column and every bundle becomes a card slotted under Draft, Pending, Published, or Private. Card fronts show the bundle title, the bundle SKU, the child item count from wp_woocommerce_bundled_items, the price, and the discount percentage from postmeta, so merchandisers see the shape of every bundle without opening the editor for any of them.

Dragging a card from Pending to Published runs the same WordPress transition the editor uses, which fires transition_post_status and publish_product. Bundle inventory recalculates against child stock, price tiers recompute, and the bundle Schema markup refreshes for SEO, exactly as they would after a manual publish in the WooCommerce product editor screen.

Stores running Product Bundles often have dozens of overlapping bundles at any given moment. Some are evergreen starter packs, some are tied to seasonal launches, and some exist only as private SKUs for wholesale customers. The default WooCommerce product list treats them all the same and mixes them in with simple, variable, and grouped products.

The disconnect between what the merchandising team needs to see and what the screen offers shows up in the worst places. A seasonal bundle stays Pending past its launch date because nobody noticed the approval bottleneck. A live bundle goes out of stock because a single child item ran dry and no one was watching the stock_status column.

A wholesale bundle accidentally goes Public because someone clicked the wrong dropdown. A kanban view that reads and writes the same bundle product rows the storefront reads keeps the team and the storefront honest. Every drag is a real publish, every column count reflects the real catalog, and the cards themselves carry enough context for a new merchandiser to launch a holiday bundle on day one with zero training overhead.