Ecommerce

Wishlist

Also called saved items, save for later, favourites

A saved list of products a shopper wants to keep in view but is not buying yet.

Quick facts: Wishlist

Category
Ecommerce
Also called
saved items, save for later, favourites
Level
Beginner
Affects
Return visits, email relevance, merchandising decisions
Where to see it
Shopify and WooCommerce wishlist apps, email platforms, GA4 custom events
In this article4
  1. How a wishlist works
  2. Why wishlists matter
  3. Where wishlists go wrong
  4. How to act on it

How a wishlist works

A wishlist is a saved list of products a shopper wants to keep in view without buying today. On most store platforms it is a heart or bookmark control on the listing and product pages, and the saved items sit either against a customer account or, for a visitor who has not signed in, in the browser’s own storage until they do.

Underneath it is nothing more than a stored list of product identifiers attached to a customer identifier, plus the date each item was saved. That simplicity is what makes it valuable. A page view might mean curiosity or a mistaken click. A save is a shopper stating, in the only language a website understands, that they want this particular item and not the others they looked at.

Why wishlists matter

A save is one of the strongest intentions a shop can collect short of an add to cart, and unlike most behavioural data it belongs to you. It sits in your own database, so it survives whatever browsers and platforms do next to third-party cookies, and it can be used in email without depending on any ad network.

It also fits how people actually buy in markets where money arrives on a schedule. A shopper who finds something in the middle of the month and expects to buy it after payday, or before a festival such as Dashain, needs somewhere to park it. Without a wishlist they either abandon a basket, which reads as a failure in your reports, or they leave and try to remember your shop later.

Where wishlists go wrong

Demanding an account before anything can be saved kills most saves outright, and it collects nothing from the visitors you most wanted to learn about. Let guests save first and ask for an email address only when they want the reminder, which is a moment they can see the value of.

The second failure is building the feature and never using what it collects. A wishlist nobody acts on is a column in a database. The third is the opposite: emailing saved items too eagerly. A save is not consent to a daily sequence, and a price-drop alert sent every time anything moves teaches customers that patience is rewarded, which quietly feeds margin erosion.

How to act on it

Make saving visible on listing pages as well as product pages, allow it without a login, and confirm the save without navigating the shopper away from what they were doing. Then put the list where they will find it again — in the account area, and in the header if you sell the kind of product people compare over several visits.

Use the data for messages that are genuinely useful: an item is back in stock, a saved size has become available, delivery to their area has changed. Keep discount alerts deliberate and occasional rather than automatic. And read the aggregate as merchandising research, because items saved often but bought rarely usually have a price, a photograph or a delivery problem worth investigating.

Do and do not

Do

  • Let guests save before asking for an account
  • Alert on back in stock and size availability
  • Review items saved often but bought rarely

Do not

  • Hide the save control on listing pages
  • Send a price alert every time anything changes
  • Collect saves and never use the data

Questions people ask about this

Is a wishlist worth adding to a small shop?

It depends on what you sell. For considered purchases that people compare over several visits — furniture, electronics, clothing, jewellery — a wishlist earns its place. For low-price repeat items bought in a single visit, it adds a control nobody uses. If you are unsure, look at how many visitors return more than once before buying.

Should shoppers have to log in to save items?

No. Requiring an account before the first save loses most of them, and those visitors are exactly the ones you know least about. Let guests save into browser storage, then ask for an email address at the point where they want something in return, such as a back-in-stock or price alert. The request makes sense there.

How is a wishlist different from an abandoned cart?

A cart says the shopper started buying and stopped, which is usually a friction or cost problem at checkout. A wishlist says they want the item but not yet, which is usually a timing or budget matter. The two deserve different messages: a cart reminder should remove an obstacle, while a wishlist reminder should give a reason that today is the day.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.