Orders show what shoppers bought. Wishlist reports show part of what they considered before buying, including products that still have not converted.
That makes wishlist data useful for product investigation, but not as a standalone demand forecast. The strongest analysis compares current saves, historical actions, add-to-cart behavior, variants, and attributed orders, then checks those patterns against inventory, traffic, margin, seasonality, and returns.
Wishlist reports reveal consideration that completed-order data cannot show by itself.
What wishlist demand can reveal
A completed order records the end of a successful purchase journey. It does not show every product the shopper compared, saved, removed, revisited, or moved toward the cart.
Wishlist data can help answer different questions:
- Which products currently remain saved?
- Which products are added most often during a selected period?
- Which products are frequently removed after being saved?
- Which saved products shoppers move toward the cart?
- Which products appear in wishlist-attributed orders?
- Do specific variants behave differently from the product total?
- Does the pattern change by market or customer type?
These questions describe consideration and progression. They do not guarantee future sales or prove why a shopper made a decision.
Use the right report for the question
TValue separates report views so that item-level, customer-level, product-level, event-level, and order-level data are not collapsed into one ambiguous total.
| Report | Primary question |
|---|---|
| Wishlists | Which products and variants are currently saved, by whom, and since when? |
| Customers | How does one shopper's saved list, activity, and attributed orders fit together? |
| Products | How do products and variants compare across saves, removals, cart actions, and orders? |
| Activity logs | Which individual wishlist actions occurred, and when? |
| Orders | Which Shopify orders contain products connected with recorded wishlist activity? |
Start with the report that matches the decision. Use Products for assortment comparisons, Wishlists for the current saved items behind a total, and Activity logs when an aggregate number needs event-level investigation.
See the Reports documentation for the complete set of views.
Separate current saves from historical activity
The most important distinction in the Products report is between a current state and recorded behavior.
| Metric | Interpretation |
|---|---|
| Wishlisted | Current number of saved wishlist items for the product |
| Add to wishlist | Recorded add actions during the selected filters |
| Remove from wishlist | Recorded remove actions during the selected filters |
| Remove rate | Remove actions divided by add actions |
| Add to cart | Recorded cart actions from the wishlist experience |
| Orders | Orders containing wishlist-attributed items for the product |
| Orders / Add to cart | Attributed orders divided by recorded wishlist add-to-cart actions |
A product can have many historical additions but fewer current saves because shoppers removed it, purchased it, or changed their shortlist. Treating Wishlisted and Add to wishlist as interchangeable would produce the wrong conclusion.
Read Products for the exact metric definitions.
Read combinations instead of ranking one number
The top saved product is not automatically the product to restock, promote, or discount. Metric combinations provide more useful hypotheses.
| Pattern | Possible interpretation | Investigation |
|---|---|---|
| High current saves, low cart activity | Strong interest with unresolved purchase friction | Review price, availability, product content, and delivery conditions |
| High additions, high remove rate | The product enters comparison but often loses | Compare alternatives, variants, price, and lifecycle |
| High cart activity, low attributed orders | The wishlist journey progresses but purchase completion is weak | Review availability, checkout, shipping, and market conditions |
| Moderate saves, strong attributed orders | The product converts efficiently from saved intent | Review what makes its product journey clear |
| High saves for one variant | Demand may be concentrated rather than product-wide | Review variant inventory and assortment |
| Email clicks without product progression | The message attracts attention but the destination does not resolve the decision | Test landing experience and purchasability |
Each row is a starting hypothesis. Validate it with Shopify analytics, inventory, sessions, margins, returns, support questions, and order data.
Expand products to understand variant demand
Product totals can hide the real constraint. A fashion product may receive most saves in one size, a jewelry product in one metal, or a home product in one finish.
The Products report can expand a product into its individual variants using the same metrics. The Wishlists report also identifies the selected variant on each current saved item.
Use variant detail to investigate:
- Demand concentrated in unavailable options.
- Strong product interest but weak availability in the preferred variant.
- Differences in removal or cart behavior between variants.
- Whether the stocked assortment matches what shoppers save.
Do not infer replenishment quantities from saves alone. Variant saves still need to be compared with traffic, conversion, inventory lead time, returns, and profitability.
Compare markets and customer types carefully
Wishlists and Products can be filtered by market and customer type. This helps distinguish patterns that a store-wide total may hide.
For example, a product may receive substantial saves in a market where its final price, delivery promise, or availability differs. Guest behavior may also look different from logged-in customer behavior because identification and repeat access are not the same.
Use these filters to form a narrower question, not to create a permanent customer label. Country, locale, and timezone may be unavailable for some shoppers, and the available context can reflect their latest recorded activity.
See Customers for the shopper-level fields and limitations.
Use Activity logs to verify the journey
An aggregate total cannot explain the order of events. Activity logs provide recorded actions such as:
- Added to wishlist.
- Removed from wishlist.
- Opened the wishlist popup.
- Clicked a product link.
- Clicked Add to cart.
- Clicked Go to cart.
- Completed checkout.
A shopper may save a product, return several days later, open the wishlist, click the product, and then complete checkout. Another may repeatedly add and remove the same item. These journeys can produce similar totals while representing different behavior.
Use the timeline to investigate a specific customer, product, or attributed order. Do not assume that every missing step failed to occur outside the actions TValue records.
Read Activity logs for event and filter details.
Interpret attributed orders conservatively
The Orders report shows Shopify orders containing products connected with recorded wishlist activity. It includes the order, market, related customer, wishlisted item count, and wishlisted item value.
This provides evidence that saved-product interest and a purchase are related. It does not prove the wishlist was the only cause of the order. The shopper may also have returned through search, advertising, another email, direct navigation, or a separate storefront path.
Use attributed orders to investigate contribution and product progression, not to claim exclusive causation.
See Orders for the attribution definition.
Turn report patterns into actions
Wishlist reports become useful when each observation leads to a testable response.
Improve product information
If products receive many saves but weak cart activity, review whether the page answers the questions delaying purchase: dimensions, materials, fit, compatibility, delivery, returns, care, or variant availability.
Review assortment and inventory
If current saves cluster around unavailable variants, compare that interest with actual sales and replenishment constraints. The report can identify where to investigate, not make the buying decision automatically.
Adjust recovery messaging
If reminder emails earn clicks but saved products do not progress, inspect the destination, availability, market context, and template. If products lose relevance before the reminder, reconsider the delay.
Select a manual campaign audience
Manual sends can narrow recipients by recent activity or saved product. Use this when a real campaign applies to selected wishlist shoppers rather than sending the same promotion to every contact.
Monitor without opening reports every day
Report emails can summarize new wishlist items, new customers with wishlists, and new wishlist activities every 3, 7, 15, or 30 days. Use the summary to notice change, then open the detailed reports to investigate the underlying products, shoppers, and events.
See Report emails and Manual sends for these workflows.
A practical product-demand review
- Choose a meaningful activity period and market scope.
- Sort Products by current Wishlisted count.
- Compare additions, removals, remove rate, cart actions, and orders.
- Expand important products to inspect variants.
- Open Wishlists to review the current saved items behind the totals.
- Use Activity logs to trace unusual customer or product journeys.
- Review attributed orders without treating attribution as exclusive causation.
- Compare the findings with Shopify traffic, sales, inventory, returns, and margin.
- Define one change to test, then review the same metrics over another comparable period.
Mistakes to avoid
- Treating current saves and historical additions as the same metric.
- Ranking products by one number without examining progression.
- Treating saves as guaranteed future demand.
- Ignoring variant-level concentration.
- Comparing markets without accounting for price, availability, and delivery differences.
- Assuming a recorded event explains every part of the customer journey.
- Claiming the wishlist was the only cause of an attributed order.
- Discounting highly saved products before investigating other friction.
- Acting on a short period without checking traffic and seasonality.
Final recommendation
Wishlist reports are most valuable as a view of unresolved and progressing product interest. Use them to ask better questions about products, variants, markets, customer journeys, and recovery messages. Then validate those questions against the operational and sales data that determine the final business decision.