Current Wishlisters seems different from wishlist-item counts

Two useful counts, two different questions

GoScript Advanced Wishlist WordPress Plugin for WooCommerce treats saved wishlist items and Current Wishlisters as separate signals. One reflects how customers organise their lists; the other reflects how many distinct customers still actively care about a given product.

1. What wishlist-item counts measure

A wishlist-item count is a count of saved rows. It is ideal for understanding the contents of a customer’s lists and how individual saved selections are organised.

One row per saved selectionEach product or variation saved into a particular wishlist is represented as its own item row.

Multiple lists can add rowsA customer can keep the same product in more than one wishlist for different occasions or plans.

Different variations can add rowsDifferent selected options of the same parent product can be saved as distinct wishlist selections.

Customer organisation contextItem rows support features such as notes, priorities, and moving or copying products between lists.

2. What Current Wishlisters measures

Current Wishlisters measures distinct customers with active saved-product interest. For each product, one customer contributes one active demand count, even if they have more than one saved reference to it.

• A customer who saves the same product in two wishlists contributes one Current Wishlister for that product.
• A customer who saves more than one variation of the same parent product still contributes one active demand count for that parent product.
• A second customer saving the product adds a second Current Wishlister.
• The count stays active while the customer has at least one saved reference to the product.
• The customer is removed from the active demand count only after their final saved reference to that product is removed.

3. A simple example

Imagine one customer saves a jacket in a “Winter wardrobe” wishlist and also in a “Gift ideas” wishlist. Another customer saves the same jacket once.

1. The first customer has two wishlist-item rows for the jacket.
2. The second customer has one wishlist-item row for the jacket.
3. There are three saved item rows in total.
4. There are two distinct customers with active interest in the jacket.
5. The jacket’s Current Wishlisters value is therefore two-not three.

This approach keeps the product’s demand signal grounded in the number of shoppers who are actively considering it.

4. Why the numbers can change at different times

The two counts can move independently because they serve different customer and reporting purposes.

• Adding another copy of the same product to a second wishlist increases saved item rows but does not increase Current Wishlisters.
• Removing one of several saved copies decreases saved item rows but keeps Current Wishlisters unchanged because the customer still has the product saved elsewhere.
• Removing the customer’s final saved copy decreases both the item count and the product’s Current Wishlisters count.
• Moving an item between a customer’s lists can change list organisation without necessarily changing active product demand.
• Historical Adds and Removals are period activity metrics, so they should not be expected to equal the live Current Wishlisters total.

5. Use each count for the right decision

Rather than treating the difference as a mismatch, use it as extra context. Together, list-item data and Current Wishlisters help you understand both the depth of customer organisation and the breadth of product demand.

• Use wishlist-item details to help customers manage and organise their own saved selections.
• Use Current Wishlisters to compare distinct active customer demand across products.
• Pair Current Wishlisters with Wishlist Adds to see both current interest and new momentum.
• Pair it with purchase metrics to identify products where active demand is progressing into sales.
• Use Products Worth Attention and Most Wanted Products to turn the customer-aware count into practical merchandising priorities.