Variation Swatches for WooCommerce extends the standard product post type for variable products with color, image, label, and radio swatch types stored as attribute meta. Each variable product lives in wp_posts with a post_status of draft, pending, publish, or private, plus the variations in child product_variation rows, the attribute taxonomy assignments, and swatch type metadata in wp_termmeta. The native product list mixes simple, variable, and grouped products together, which makes it hard to focus on the swatch-driven catalog.

SleekView Kanban reads the same variable product rows you would query with WP_Query filtered to the variable product type. Pick post_status as the group column and every variable product becomes a card slotted under Draft, Pending, Published, or Private. Card fronts show the product title, the swatch type from termmeta (color, image, label), the number of variations from the child product_variation count, the price range, and the stock status, so merchandisers see every product's swatch shape at a glance.

Dragging a card between columns runs the same WordPress transition the editor uses, which fires transition_post_status and publish_product. Variation Swatches refreshes the swatch render cache, the variation availability map recomputes, and the storefront product page shows the new swatch state immediately, exactly as it would after a manual publish from the WooCommerce product editor screen.

Storefronts running Variation Swatches typically have dozens of overlapping variable products with color, image, or label swatches across the catalog. Some are evergreen color lines, some are tied to seasonal launches with limited windows, 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 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 swatch product stays Pending past its launch date because nobody noticed the approval bottleneck. A live product runs out of stock on a single color and merchandising never notices the variation is unavailable.

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