Wishlist / favorites implementation

Wishlist (a wish list, “favorites”) implementation is the ability to save products for later: the client clicks “add to favorites”, the product goes into a personal list they return to. Not everyone is ready to buy right away — a wishlist keeps the interest: a person sets aside what they liked and then comes and places the order, instead of searching again or forgetting. We do it for logged-in users (the list is tied to the account, visible on all devices) and for guests (storage in the browser — works without logging in, but is lost on clearing cookies, in incognito mode or on another device, and on mobile this happens more often; we account for this honestly and suggest an account for reliability). Optionally — notifications about a price drop or a restock for saved products: a strong reason to return (it needs integration with prices and stock). Unlike a cart, which is about “buy now”, favorites are about “save and think”: a cart pushes toward checkout, while favorites calmly keep the choice while the client compares models and thinks. Importantly and honestly: a wishlist pays off where the product is chosen not right away and is compared (clothes, furniture, electronics, jewelry); for a simple single-purchase product it is almost unnecessary, and we will say so. And honestly about ready modules: most CMSs have a basic “favorites”, but often without transferring the guest into the account, without notifications and without tidy work on mobile — we bring it to a working tool; if a standard module is enough for you, we will say so. Picture this: a buyer has eyed three models but decides later — puts them into favorites, comes back a week later and takes one, without starting the search from scratch. The base price starts from 15,000 ₽: it includes favorites for the guest and the account with a transfer on login; notifications about price and availability and complex integrations are estimated separately.

• The buyer is not ready to buy now — leaves and forgets what they were eyeing.
• To get back to a product, you have to search for it again — many do not return.
• There is no reason to bring the client back — you do not know what interested them.
• There is no one to show a price drop or a restock to — the interested do not find out.

• An “add to favorites” button on the card and in the catalog
• A personal favorites list, returning to the saved items
• For logged-in users — the list on all devices; for guests — browser storage (with an honest caveat about losses)
• A counter and quick access to favorites from the header
• Transfer of the guest favorites to the account on login
• Responsive, saving in one tap on a phone
• Optionally (separately) — notifications about a price drop and a restock (needs stock and price integration)

• It is easier for the client to return to the saved items — a higher chance of a repeat visit and purchase
• You do not lose the interest — what was eyed is not forgotten and not searched again
• A reason to bring the client back appears — notifications about price and availability
• Choosing is more convenient — you can compare the saved items, a higher chance of buying

• You leave a request and describe the catalog, guest/account, whether notifications are needed
• We implement favorites, the list, the guest-to-account transfer, and notifications if needed
• We test and launch

• How are favorites different from a cart?

  A cart is about “buy now”: products a person is going to check out, it pushes toward payment. Favorites are about “save and think”: what was eyed for the future, without the intention to buy right now; it calmly keeps the choice while the client hesitates between models. They often work together: from favorites a product is easily moved to the cart when the client has decided.

• Will favorites be saved without registration?

  For guests we store favorites in the browser — it works without logging in, but is lost on clearing cookies, in incognito or on another device (more often on mobile). For reliability and access from any device an account is better; on login we transfer the guest favorites into the profile so nothing is lost. We will decide based on your audience.

• What if I have a simple single-purchase product?

  Then you probably do not need a wishlist. For example: a one-off gift purchase — the person is unlikely to come back for the same thing, and favorites will not work. It pays off where the product is chosen not right away and is compared (clothes, furniture, electronics). For a simple one-off purchase it is better to invest in something else (quick ordering, reviews), and we will say so honestly.