A Shop Wishlist Is Not an Order: What Should Saved Products Remember?

A wishlist should help a shopper return to a product without pretending that the shopper has bought it or secured its availability. Before adding a heart button to your shop, agree what is saved, who can recover the list and what happens when the shopper decides to buy.

This is a brief for a personal product shortlist, not a shared purchasing approval system or a stock-reservation feature. A wishlist may be useful when customers compare purchases over several visits; do not add it simply because another shop has one.

Define the saved item

In a fictional lighting shop, a customer saves a particular lamp in a particular finish. Saving only the general lamp page may lose the finish they selected. Saving an exact discontinued version without explanation can be equally unhelpful.

Decide whether each entry identifies a general product, a specific variant or a configured selection. Show enough information for the customer to recognise it later. If personalisation text is excluded, say so rather than presenting the saved entry as a complete future order.

The Odoo 19 additional eCommerce features guide describes its wishlist as saving products for later. It also documents moving products from the cart into the wishlist and from the wishlist into the cart. That is a concrete product example, not evidence that every selection detail survives either move. Ask the developer to demonstrate the details your own shop needs.

Choose whose list survives

Agree the difference between an anonymous browser list and a list connected to an account. Must the customer sign in to save? Will a saved list still exist on another device? What happens when an anonymous shopper later signs in to an account with existing entries?

For a proposed merge, define whether repeated items are combined and which selected options survive. A sign-in should not silently replace the person's list with an empty one. Conversely, a shared device must not expose the previous customer's private list to the next person.

These are requirements to settle and test, not persistence or security guarantees made by the cited Odoo page. Explain any device-only limitation before a customer relies on returning later. Provide deliberate removal and agree your retention policy rather than keeping forgotten lists indefinitely by accident.

Treat returning to the cart as a fresh decision

A saved product is a reference to a possible purchase. Require the agreed current checks when it moves to the cart: whether the product can still be purchased, which options remain valid and what current price applies. Do not silently substitute a different finish when the original is no longer sold.

Show a useful unavailable state with a route back to the catalogue. If an old displayed price is retained for context, distinguish it from the amount now offered. This article does not determine contractual price commitments; obtain appropriate advice for your actual offer.

Also decide whether adding to the cart keeps the wishlist entry. “Move” and “copy” produce different results. A failed cart action should not erase the only saved reference. These are proposed acceptance outcomes, not claims about Odoo's failure handling.

Do not turn a save into marketing permission

Keeping a product in a personal list is not the same interface action as asking for reminder messages. If reminders are in scope, define a separate preference, the communication channel and how people stop them. Have the applicable privacy and marketing requirements reviewed; a heart click alone should not be described as proven legal permission.

Start without reminders if the real requirement is simply finding a product again. You can evaluate the shortlist as a navigation aid without promising a conversion increase or inventing evidence that every save signals an imminent purchase.

Demonstrate the return visit

Use harmless sample products in the acceptance criteria: save a variant, leave and return, sign in with an existing list, remove an entry, and try a product whose price or availability changed. Include a shared-device sign-out and a cart transfer that fails.

For each case, the shopper should understand what remains saved and what, if anything, has been purchased. Bring those outcomes to a shop or web-app project discussion. The deliverable is a reliable route back to a considered product, not just a heart icon.