What Is a Good Wishlist Conversion Rate for Ecommerce?
Why a Universal Benchmark Number Does Not Exist
Wishlist conversion varies far too much between stores for a single figure to be meaningful. A $19 candle and a $900 sofa have completely different consideration windows, and both are ecommerce.
Category matters just as much. Fashion has size and fit uncertainty that creates saves which convert only after a restock. Print-on-demand rarely goes out of stock at all, so its saves convert on a different rhythm entirely.
Measurement windows distort things further. A store measuring conversion within 7 days of a save will report a much lower number than a store measuring within 90 days, and neither is wrong. They are just answering different questions.
That is why merchants on OpoShop are better served by tracking their own trend than by chasing a figure quoted somewhere else. If your number went from 6 to 9 over a quarter, that is real information. If someone tells you the industry average, you cannot verify what they counted.
Define the Metric Before You Measure It
Most confusion about wishlist conversion is definitional. There are three reasonable metrics and they produce very different numbers.
- Save-to-purchase rate: Of all items saved, what share are eventually bought by the person who saved them. This is the strictest definition and produces the lowest number.
- Saver-to-customer rate: Of all shoppers who saved at least one item, what share went on to place any order. This is more generous and usually the most useful for judging the feature.
- Alert-attributed revenue: Revenue from orders that followed a back-in-stock or price-drop email within a set window. This is the one that justifies the effort in plain money.
Each measures something legitimate. Save-to-purchase tells you how predictive an individual save is. Saver-to-customer tells you whether savers are better customers than non-savers. Alert-attributed revenue tells you whether your reminders are doing work.
Pick one as your headline number and stick with it, because switching definitions mid-quarter makes the trend meaningless. Most OpoShop merchants get the most value from saver-to-customer, with alert-attributed revenue as the money check.
The Arithmetic, With a Worked Example
Numbers make this concrete. Take a store with 10,000 monthly visitors and a 2 percent site-wide conversion rate, so 200 orders a month.
Say 700 of those visitors save at least one item, and between them they save 1,400 products. Over the next 60 days, 91 of those 700 savers place an order. That is a saver-to-customer rate of 13 percent, which is well above the 2 percent site-wide rate.
Now the strict version. Of the 1,400 saved items, 168 are eventually purchased by the person who saved them. That is a save-to-purchase rate of 12 percent. Lower-priced categories tend to land higher, considered purchases lower.
The money check is the third one. If back-in-stock and price-drop emails drove 40 of those orders at an average order value of $62, the alerts produced $2,480 in the month. Against an app cost and a few hours of setup, that is the number that settles whether the feature is worth running.
Run this same arithmetic on your own store for two months before drawing conclusions. One month is too noisy, especially if a single restock skews the period.
Notice which comparison did the persuading. It was not the absolute 13 percent. It was 13 percent against 2 percent, measured on the same traffic in the same month. That internal gap is the only comparison that holds up, and any OpoShop store can produce it without extra tooling.
How to Build Your Own Baseline
Measuring properly takes about a month of patience and very little work. The point is to get a number you trust, not a number that looks good.
Two parts of that need care.
1. Choose a window that fits your price point
A $25 accessory and a $400 piece of furniture do not deserve the same window. If your average order value is low and purchases are impulsive, 30 days is plenty. If you sell considered items, 90 days will capture conversions a 30 day window silently discards.
Getting this wrong is the most common way stores conclude that wishlists do not work. They measure a 14 day window on a category where the average buyer takes two months, then switch the feature off just as it was starting to pay. Check your own OpoShop order history for the typical gap between a customer's first visit and their first order, and use that as your window.
2. Compare savers against non-savers, not against a benchmark
The single most convincing measurement is internal. Take everyone who saved at least one item in a month and everyone who did not, then compare what share of each group ordered within your window.
If savers order at several times the rate of non-savers, the feature is working, regardless of what any published figure claims. That comparison is also easy to explain to yourself six months later, which matters more than precision.
Three Ways to Measure, and What Each One Is Good For
Since the three definitions answer different questions, it helps to see them side by side.
| Metric | What it answers | Typical use | Main weakness |
|---|---|---|---|
| Save-to-purchase | How predictive is one individual save | Judging demand quality per product | Punishes considered categories with long windows |
| Saver-to-customer | Are savers better customers than browsers | Deciding whether the feature earns its place | Credits purchases the shopper may have made anyway |
| Alert-attributed revenue | Are my reminder emails producing money | Justifying the cost of running the feature | Attribution window choices swing the number a lot |
Save-to-purchase is the metric to use per product, not per store. Sorting your catalog by it reveals which pages have a demand problem and which have a conversion problem.
Saver-to-customer is the right headline for the store overall, because it captures the real behaviour: shoppers save several things and buy one of them, sometimes a different one entirely.
Alert-attributed revenue is the one to check quarterly. If your OpoShop store sends few alerts because nothing goes out of stock and prices rarely move, expect this number to be modest, and lean on the other two.
What Actually Moves the Number
Once you have a baseline, a small number of changes move it more than anything else.
Placement is first. Adding the save control to collection tiles typically increases save volume substantially, because most reactions happen in the grid rather than on the product page. More saves at the same conversion rate is more revenue.
Variant-level capture is second. Recording that a shopper saved the navy size 8, not just the dress, means your restock email reaches exactly the right people. A generic restock blast to everyone who saved the dress converts far worse and irritates the rest.
The landing destination is third. Alert emails that drop the shopper on the homepage waste the click. Emails that land on the saved items page, with live price and stock and an add-to-cart button, convert noticeably better.
Cadence discipline is fourth. Event-triggered emails only fire when something real changed, which keeps the list healthy. Scheduled nudges lift short-term clicks and quietly destroy the channel over a few months, and rebuilding an OpoShop alert audience after you have burned it takes far longer than growing it did.
- Move the button to the grid: More saves from the same traffic.
- Capture the variant: Precise restock emails instead of blanket ones.
- Land on the saved list: One tap from click to cart.
- Trigger on events only: A list people stay subscribed to.
What a Low Number Usually Means
A low wishlist conversion rate is rarely a verdict on wishlists. It is usually one of four specific problems.
The first is a save button nobody can find. If saves per hundred visitors is very low, conversion is not your problem yet. Fix visibility first.
The second is alerts that were never switched on. Saves without follow-up are a report, not a channel. Plenty of stores collect saves for months and never enable the back-in-stock email that makes the data pay.
The third is a mismatched window. Measuring a 30 day window on a category where shoppers take two months to decide will always produce a disappointing number.
The fourth is a product page problem that shows up as a high save-to-sale gap on specific items. If one product collects heavy saves and almost no purchases while the rest of your catalog is fine, look at that page's sizing information, delivery estimate, and photography before blaming the feature.
Work through those four in order. In most OpoShop stores, at least one of them is the whole explanation, and fixing it changes the number more than any amount of copy tweaking.
Best answer: A good wishlist conversion rate is one that clearly exceeds your own site-wide conversion rate and improves against your own 30 to 60 day baseline. Define the metric precisely, choose a window that matches your price point, compare savers against non-savers, and then move the levers that matter: button placement, variant-level capture, and landing shoppers back on their saved list in your OpoShop store.
FAQs
Should wishlist conversion be higher than my site-wide conversion rate?
Almost always, yes. Savers chose a specific product deliberately, so they are a self-selected, higher-intent group, and a wishlist conversion rate below your site-wide rate usually points at a measurement or follow-up problem.
How long should I wait before judging the number?
Give it at least 30 days, and 60 is better. A single restock or a seasonal spike can distort one month badly, so the trend across two or three months is far more trustworthy than any single figure.
Does a low save volume mean shoppers do not want the feature?
Usually it means they cannot find it. Check whether the save control appears on collection tiles and search results, since that is where most saves happen, and whether the icon has enough contrast to be noticed.
Which metric should I report if I only track one?
Saver-to-customer rate. It reflects real shopper behaviour, where people save several items and buy one, and it is the easiest to compare fairly against non-savers.
Do anonymous saves count toward conversion?
They should, because anonymous savers do come back and buy. You will not be able to email them, but their saves still feed the demand ranking and still convert when they return to the store.
How do I attribute a purchase to a wishlist alert?
Pick a fixed window, commonly a few days after the email, and count orders containing the alerted product from recipients within it. Keep the window consistent, because changing it is the fastest way to make your own trend meaningless.
Want a baseline you can actually trust? Start measuring in the store you already run.
