SleekView for YITH WooCommerce Wishlist: wishlists & items as tables
YITH stores wishlists and items in dedicated yith_wcwl_lists and yith_wcwl_items custom tables. SleekView reads them directly so most-wanted reports, abandoned-wishlist outreach, and per-customer wishlist history live on one screen.
♾️ Lifetime License available
Turn wishlist data into action
YITH WooCommerce Wishlist persists data in two purpose-built custom tables: yith_wcwl_lists for the wishlist itself and yith_wcwl_items for each product line. The default admin treats those tables as separate screens, which means cross-cutting questions — most-wanted products, abandoned wishlists older than thirty days, per-customer histories — require navigating between the tabs and stitching results in spreadsheets.
SleekView joins the two tables and exposes views that match the actual operational questions. Most-wanted products aggregates item rows by product and ranks by add-count or estimated revenue. Abandoned-wishlist segmentation filters lists by last-update older than a configurable window for win-back outreach. Per-customer history sorts wishlists by owner email so support sees full context during chat.
Privacy and share-token columns surface inline, so shared-list workflows are auditable without clicking into each list. Inline edits route through YITH's API for status changes that need hooks to fire, with direct DB edits available per view for clean-up tasks where hooks are an explicit non-goal.
Workflow
How SleekView reads YITH wishlist data
Join yith_wcwl tables
Aggregate for merchandising
Save outreach segments
Edit through YITH API
Sample columns
A typical wishlists view
wp_yith_wcwl_lists + wp_yith_wcwl_items
| List | Owner | Items | Last update | Privacy | Status |
|---|---|---|---|---|---|
| Studio gear | alex@studio.co | 12 | Apr 24 | Public | Active |
| Birthday picks | ria@design.io | 5 | Apr 22 | Private | Active |
| Maybe later | tom@hello.dev | 3 | Mar 30 | Private | Stale |
| Gifting | mia@brew.coop | 1 | Feb 14 | Shared | Abandoned |
Comparison
Default YITH admin vs SleekView
Default YITH admin
- Wishlists and items are split across separate screens
- Most-wanted product reports require navigating analytics tabs
- Filtering by wishlist size, age, or privacy isn't a saved view
- Abandoned-wishlist marketing exports need third-party tools
- Per-customer wishlist history needs custom queries
SleekView
-
Read
yith_wcwl_listsandyith_wcwl_itemsdirectly - Aggregate items per product for most-wanted views
- Filter abandoned wishlists by last-update date
- Pivot privacy and share-token columns into the list
- Save views per marketer or merchandiser
Features
What SleekView gives you for YITH WooCommerce Wishlist
Joined wishlist + item views
Combine yith_wcwl_lists with yith_wcwl_items into one row per wishlist with item counts, last-touched dates, and privacy badges sortable in any direction.
Most-wanted products
Aggregate item rows by product to surface the items most often added across wishlists, sortable by add-count or estimated revenue potential for promotion planning.
Abandoned-wishlist filters
Filter by last-update older than thirty days to build a clean outreach segment for win-back campaigns, exportable directly to CSV for marketing automation tools.
Audience
Who uses SleekView for YITH WooCommerce Wishlist
Marketing
Abandoned-wishlist segmentation and most-wanted reports for re-engagement and Black Friday planning, without exporting raw tables and joining them in spreadsheets.
Merchandising
Sort products by wishlist adds to plan stock and promotions against real latent-demand signals, instead of relying solely on past best-seller lists.
Support
Per-customer wishlist history visible during chat or call, with privacy and share-token state surfaced for shared-list troubleshooting in seconds.
The bigger picture
Why wishlist data deserves an operational layer
Wishlist data is the closest a WooCommerce store gets to a real signal of latent demand, and most stores throw it away. The default YITH admin lists wishlists in one screen and items in another, with no built-in cross-aggregation. Marketing wants most-wanted products to plan promotions; merchandising wants stock alignment with wishlist demand; support wants per-customer wishlist history during chat.
None of those are one click in the default UI. The operational consequence is that wishlist data sits unused while the team relies on coarser signals — best-seller lists from past orders, traffic from analytics — to make stocking and promotion decisions. Joining the two YITH tables and exposing them as ranked, filterable views changes the calculus.
A merchandiser looking at next month's promotion picks the top-twenty most-wanted-but-low-stock products in one query. A marketer building a Black Friday segment exports abandoned-wishlist owners from a saved view. The plugin is doing all the work of capturing the data; the operational layer just makes it usable instead of leaving it to gather dust in two custom tables.
Questions
Common questions about SleekView for YITH WooCommerce Wishlist
Yes. Guest wishlists tied to a session cookie persist in the same yith_wcwl_lists table with a session_id rather than a user_id. SleekView shows them with a generic guest label, so merchandising aggregation works against the full data set rather than just authenticated customers.
Yes. The token column from yith_wcwl_lists is exposed as a filterable column. That's the route to debug shared-list issues — a customer says their shared wishlist URL doesn't work, you filter by token to find the row and verify the privacy state in seconds.
Yes when SleekView uses YITH's API for status changes. Direct DB edits skip hooks by design — useful for bulk privacy normalisation where you don't want every change to send a notification. The behaviour is selectable per view, so editorial and clean-up workflows don't conflict.
Yes. Any SleekView view exports to CSV or JSON, including aggregated views like most-wanted-by-product. Marketing teams pipe that export directly into Klaviyo or similar tools for segmented campaigns built against the actual wishlist signal.
Yes. Wishlist data lives in YITH's own custom tables and is independent of order storage, so HPOS settings don't change SleekView's queries. Joins to orders — for example, attributing converted wishlist items — read from whichever order table HPOS is configured to use.
Yes. Views are gated by WordPress capability, so a marketing role sees outreach segments while a merchandising role sees most-wanted aggregates and a support role sees per-customer history. Column sets save per role for predictable workflows.
Yes. The plugin records share events; SleekView exposes them as a separate view alongside lists and items, so social-share volume and converted-from-share counts surface for campaign analysis.
Yes. By joining yith_wcwl_items with the orders view through product ID and customer ID, SleekView shows which wishlist items eventually converted to orders. That conversion column lights up the items worth promoting harder versus the ones that languish across cycles.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout