WooCommerce Favorites takes a lightweight approach: each registered customer's favorite product ids live in wp_usermeta under a plugin-specific key (typically woocommerce_favorites) as a serialized array, and guest favorites are kept in a cookie that is migrated to user meta on login. The default admin renders a per-user list inside the user profile, which means there is no surface that ranks products by favorite count or that segments customers by what they have saved.

SleekView reads the user meta directly, expands the serialized array into one row per user-product pair, and joins to wp_posts for product name and price plus wp_wc_product_meta_lookup for stock status. Most-favorited views aggregate by product id, while per-customer views show every favorite for a given user without opening their profile.

Inline edits (removing a favorite, moving a favorite onto a different product variation) route through the plugin's API so any hooks the plugin fires on add/remove are respected. Bulk operations like clearing favorites for inactive users use the same path.

WooCommerce Favorites is a lightweight signal capture: every favorite is a customer telling the store what they like without buying yet, which is one of the cleanest intent signals a merchant gets. The default admin treats favorites as a profile-level detail, so the data sits in wp_usermeta with no surface that ranks products, segments customers, or flags stale favorites pointing at out-of-stock items. SleekView reads the user meta directly, joins to product and stock tables, and exposes favorites as a sortable, filterable, editable table.

Marketing can finally trigger personalised outreach when a favorited product changes price or comes back in stock. Merchandising can finally rank products by intent rather than only by sales. Support can finally pull a customer's saved items during a chat without opening their profile.

The plugin still owns the favorites mechanism; SleekView turns the captured signal into a working surface.