The abandoned wishlist is a signal most retailers never act on

A page view says someone was curious, a saved item says someone made a decision. The gap matters more than most teams realise. You watch for traffic, page views and conversion rates closely, then let one of the clearest intent signals sit untouched in a database table that no one owns

After 42 years in technology, I've seen the same pattern many times. The data that looks like a minor feature often turns out to be the most useful data in the business.

The myth: a wishlist is a convenience feature

Most platforms treat wishlists and save for later as a favour to the customer. A button, a heart icon, a page in the account area, build it, ship it, move on. That thinking is where the value leaks out!

A customer who saves a product has done something browsing never asks of them. They have picked one item from hundreds, decided it matters and told you they plan to come back. No ad prompted that, no discount nudged it.

It is first party intent data, handed over freely.

Why a saved item outranks a browsed page

Browsing is noisy. Someone clicks a product because the image caught their eye, because they were comparing, or because they were killing five minutes on the train. Saving is deliberate. The customer has filtered out the noise for you.

That makes wishlist activity a stronger indicator of purchase intent than almost anything in your standard analytics. It also tells you something page views can't: which specific product, at which price point, at what moment in the customer's thinking. If you could only keep one behavioural signal, I'd keep the save.

What happens when the data sits in a silo

Here is the usual setup. The wishlist lives inside the ecommerce platform. Marketing automation runs on a separate system. Stock planning runs on a third. Reporting pulls from whichever of them someone remembered to export, none of them talk to each other, so the signal goes nowhere.

For a technology lead at a scale up, this is a familiar problem with a familiar cost. Every disconnected system adds manual work, delays decisions and leaves the business guessing about things it already knows.

The fix is rarely a new platform. It is usually a handful of well designed events. A product saved, a product removed, a saved product that drops in price, comes back into stock or runs low. Publish those events cleanly, tie them to a single customer record, and every other system can use them.

Turning saves into communication that feels helpful

Once wishlist data reaches your marketing platform, the quality of your communication changes. A generic campaign says "here's what's new", a connected one says "the jacket you saved is back in your size." One of those feels like noise, the other feels like a shop that was paying attention.

The practical wins are straightforward:

• Back in stock and low stock prompts on saved items
• Price change alerts for customers who have shown interest
• Personalised recommendations built from what people chose to save, not just what they happened to click
• Timely reminders that respect the customer's pace rather than hammering them

The restraint matters as much as the trigger. Done well, these messages help the customer. Done badly, they feel like surveillance. Be clear about consent, keep frequency sensible and let customers manage their own lists.

Saves as demand intelligence

This is the part most retailers miss completely. Look at saves in aggregate and you have an early demand signal. Which products are being saved faster than they are being bought? Which sizes and colours sit on wishlists but not in stock? Which items attract saves but never convert, which may point to a price, delivery or product page problem?

Merchandising and inventory teams spend a great deal of effort trying to forecast demand from past sales, past sales only tell you what people bought when you happened to have it. Saves tell you what people wanted.

Feed that data into stock planning and the conversation changes. You can see unmet demand before it turns into lost revenue. You can back a product that is quietly building interest. You can stop over ordering something that gets looked at but never wanted.

Where to start

You don't need to rebuild anything. Start with three questions. Where does our wishlist data live today, and who can actually access it? Can our marketing platform see a save as it happens, tied to a known customer? Does anyone in merchandising or stock planning ever look at saved-item trends?

If the answer to the last one is no, you have found your first opportunity. A simple weekly report of the most saved products against current stock is often enough to show the value, and it builds the case for connecting the rest.

From saved item to future sale

A wishlist is not a convenience feature. It is one of the clearest statements of intent a customer will ever make, and most businesses let it sit in a corner of the platform doing nothing. Connect saved item data to your marketing, your stock planning and your customer segmentation, and a feature becomes a source of demand intelligence. The brands that do this treat a saved product as a future sale, not an abandoned interaction.

So this week, review how your business uses wishlist and save-for-later data. If it exists purely as something customers can click, ask what it would take to put it to work across marketing, stock and reporting. If you'd like to talk that through, I'm glad to have the conversation.