WooCommerce Product Add-Ons stores global add-on groups as a custom post type registered by the plugin. Each row lives in wp_posts with a post_status of draft, future, publish, or private, plus metadata in wp_postmeta for the add-on field definitions, the price modifier rules, the priority, and the product or category restrictions. The native admin lists every add-on group as a flat table, which is fine for archive lookups but blind to the live state of an ongoing customization launch on the storefront.

SleekView Kanban reads the same add-on group rows you would query with WP_Query filtered to the plugin's post type. Pick post_status as the group column and every add-on group becomes a card slotted under Draft, Scheduled, Published, or Private. Card fronts show the group title, the field count from the add-on definitions in postmeta, the priority, the target product or category restriction, and the price modifier strategy, so a merchandiser sees the shape of every group at a glance.

Dragging a card from Draft to Published runs the same WordPress transition the editor uses, which fires transition_post_status and publish_ hooks for the plugin's post type. Add-on caches refresh for the targeted products, the add-on JSON used by the storefront rebuilds, and any extension layered on Product Add-Ons reacts to the visibility change, exactly as they would after a manual publish from the admin editor.

Stores running Product Add-Ons accumulate dozens of overlapping add-on groups across the catalog. Gift wrap on every product. Engraving on watches.

Custom color on sneakers. Monograms on bags. Holiday personalization launches that need to go live on an exact date and disappear the day after.

The default admin lists them all together, which means merchandising never knows which groups are scheduled, which are private, and which are accidentally still live a month after a campaign should have ended. The disconnect between what the merchandising team intends and what the storefront actually offers shows up in the worst places. A holiday gift wrap stays live in February.

A VIP early access add-on group is visible to anyone with a guest session. A scheduled launch quietly misses its date because nobody confirmed the post_status was set to future correctly. A kanban view that reads and writes the same add-on group rows the storefront reads keeps the team and the catalog honest.

Every drag is a real publish, every column count reflects the real personalization shelf, and the cards themselves carry enough context for a new merchandiser to launch a campaign on day one of the season.