YITH WooCommerce Wishlist stores every customer wishlist in the wp_yith_wcwl_lists table with related rows in wp_yith_wcwl_items. Each list row carries a user_id, a wishlist_token, a session_id for guest lists, a is_default flag, and a privacy column with values 0 for public, 1 for shared, and 2 for private. The native admin shows it all as a flat table, which makes it hard to see which customers have abandoned saved baskets versus which are sharing wishlists publicly.

SleekView Kanban reads the same wp_yith_wcwl_lists rows you would query with YITH_WCWL_Wishlist. Pick privacy as the group column and every wishlist becomes a card slotted under Public, Shared, Private, or Archived. Card fronts can show the customer name from wp_users, the wishlist title, the item count from wp_yith_wcwl_items, and the date created, so a merchandiser triaging a viral wishlist campaign sees enough context to act on the board.

Dragging a card between columns calls the YITH helper for updating the privacy value, which writes back to wp_yith_wcwl_lists.privacy and refreshes the customer's My Wishlist view. Sharing tokens regenerate when a list moves between Public and Shared, customer notifications fire if you have the email module enabled, and any extension listening on the yith_wcwl_after_update_wishlist hook reacts exactly as it would after a manual edit.

Stores running YITH Wishlist often accumulate thousands of saved lists. Some belong to one-time guest sessions and quietly die. Some are public gift registries that go viral and drive real conversion.

A small but steady stream get reported by customers for inappropriate content. The default YITH admin treats all of them the same, which means merchandising never knows which lists to surface, retention never knows which to reactivate, and moderation hand-codes a SQL query whenever they need to find reported content. The disconnect between what the storefront shows and what the team can find shows up in the worst places.

A public wishlist with offensive content stays live for days because nobody noticed the report. A viral gift list does not get promoted because nobody scans the public lists weekly. A kanban view that reads and writes the same wp_yith_wcwl_lists rows the storefront reads keeps the team and the database honest.

Every drag is a real privacy change, every column count reflects the real catalog of saved lists, and the cards themselves carry enough context for a new merchandiser to pull a gifting campaign together on day one.