TI WooCommerce Wishlist stores every customer wishlist in the wp_tinvwl_lists table with the items in wp_tinvwl_items. Each list row carries an author, a share_key, a status column with values public, share, and private, plus timestamps in date. Guest lists store under session. The plugin's admin lists every row in a flat table, which is fine for archive work but blind to the live merchandising and moderation workflows the store really needs to run every day.

TI Wishlist's API exposes the same data through tinv_wishlist_get_user_lists and helper functions. SleekView Kanban reads those rows directly. Pick the status column as the group field and every wishlist becomes a card slotted under Public, Shared, Private, or Archived. Card fronts show the customer name from wp_users, the list title, the item count from a join on wp_tinvwl_items, and the share_key, so an outreach lead has the shareable URL ready right on the card without opening the list.

Dragging a card between columns calls the TI helper for updating the status field, which writes to wp_tinvwl_lists.status and fires the tinv_wishlist_after_update_status hook. Share keys regenerate when a list moves between Public and Shared, customer notifications fire if the email module is on, and any extension listening for visibility changes reacts exactly as it would after a manual edit from the customer account screen.

Stores running TI WooCommerce Wishlist accumulate thousands of saved lists over the lifetime of the storefront. Some belong to one-time guest sessions and quietly die. Some are public gift registries that go viral on social media and drive real conversion.

A small but steady stream get reported by customers for inappropriate or off-policy content. The default TI 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 a reported list. The disconnect between what the storefront shows and what the team can find shows up in the worst places.

A reported list stays live for days because nobody noticed. 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_tinvwl_lists rows the storefront reads keeps the team and the database honest.

Every drag is a real visibility 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 of the job.