Wishlist and Save-for-Later Features: Do They Actually Drive Sales?

A wishlist feature request usually arrives justified by "customers expect it" more than by any specific evidence it'll move revenue, which makes it a good candidate for the same scrutiny we bring to any feature request: what's it actually supposed to accomplish, and how will we know if it worked?

What a wishlist feature genuinely does well

It captures purchase intent that would otherwise be lost entirely — someone not ready to buy today, but interested enough to want to find the product again later. Done well, it's a low-friction way to keep that intent from evaporating, and a natural trigger point for a well-timed reminder or price-drop notification.

Where it underperforms expectations

• When it's just a static list with no follow-up mechanism — capturing intent and then doing nothing with it wastes most of the feature's actual value.
• When it requires an account to use, adding exactly the kind of friction we described in cart abandonment at the moment someone was just casually browsing.
• When the saved items aren't genuinely easy to find again, buried in a menu nobody remembers exists.

What actually makes it worth building

Pairing it with automated re-engagement — a reminder email, a price-drop alert — turns a passive list into an active sales channel. Without that follow-through, it's a nice-to-have with unclear ROI, exactly the kind of feature that should get the same prioritization scrutiny as anything else on a roadmap.

A wishlist without a follow-up mechanism is a place where purchase intent goes to be quietly forgotten, by both the customer and the business.

We build the follow-up mechanism as part of the same project, not a separate future phase — the wishlist itself is the easy half of this feature.