A wish list feature is a saved, shareable collection of products stored within a user account that lets shoppers bookmark items for future purchase, price monitoring, or gifting. According to We Are ROAST, 55% of British consumers use wish lists to track items while researching and comparing prices, and 39% save products specifically to consider a future purchase, which for UK merchants represents a measurable intent signal, not passive browsing.
Core capabilities across standard implementations include:
- Save items to a named list from any product page
- Create multiple lists organised by event, project, or priority
- Share lists via link or email with friends, family, or colleagues
- Receive price and stock alerts when saved items change
- Purchase directly from the list, with purchased items removed or retained depending on store settings
Oracle’s wish list documentation confirms these as the standard feature set across enterprise and mid-market platforms alike.
Key takeaways
A wish list feature converts passive browsing into measurable purchase intent, giving merchants a remarketing asset and shoppers a structured tool for planning and gifting.
| Point | Details |
|---|---|
| Definition | A wish list is a saved, shareable product collection tied to a user account for future purchase or gifting. |
| Merchant revenue impact | Wish list users place orders 50% larger and spend 30% more than non-list users, per We Are ROAST. |
| UK consumer behaviour | 55% of British shoppers use wish lists for price research; 39% save items to consider a future purchase. |
| GDPR compliance | Wish list data is personal data under UK GDPR; merchants need a lawful basis, a privacy notice, and deletion controls. |
| MedwayWebDesign | MedwayWebDesign builds and integrates wish list features for UK merchants, connecting notifications, analytics, and mobile UX. |
Table of Contents
- How does a wish list feature work?
- How do shoppers create, share, and edit a wish list?
- Why do wish lists benefit shoppers?
- Why do wish lists help e-commerce merchants?
- How do you add a wish list to your store?
- Wish lists as product-roadmap signals: the strategic view
- Legal and privacy considerations for wishlists
- How wishlists interact with inventory management
- The case for starting with apps and knowing when to go custom
- MedwayWebDesign builds wish list features that actually convert
- Sources and further reading
How does a wish list feature work?
The typical user flow is straightforward: a shopper adds a product to a named list, the platform stores that association against their account, and the merchant’s system begins tracking that item’s status for notification and remarketing purposes.
Lists are stored against authenticated user accounts in most implementations, which means the data persists across devices and sessions. Some platforms support anonymous wish lists via browser cookies, but these are fragile: they disappear when cookies are cleared and cannot be used for email re-engagement. Account-based storage is the standard recommended by BigCommerce, precisely because it enables the downstream marketing workflows that generate merchant value.
Each saved item carries metadata: product ID, variant (size, colour), quantity, any shopper notes, and a priority flag where the platform supports it. That metadata feeds notification triggers. When a product’s price drops or stock falls below a threshold, the platform fires an alert to every shopper who has saved it. On the merchant side, the same event can trigger an analytics tag, a CRM update, or a segmentation flag for paid remarketing.
Sharing and privacy controls vary by platform. Amazon Lists, for example, keeps lists private by default and offers a “Don’t spoil my surprises” setting that hides purchased items from the list owner, preserving the gift-giving experience. When a purchase is made from a shared list, the item is typically marked as bought so other buyers avoid duplicating the gift.
Common integration gaps worth noting: anonymous lists rarely feed email workflows; wish list add events are frequently missing from Google Analytics 4 event schemas unless explicitly configured; and inventory sync between wish list data and warehouse management systems requires custom middleware in most plugin-based setups.
Pro Tip: Configure a custom GA4 event for add_to_wishlist from day one. Retroactively adding it after launch means losing weeks of intent data that could have informed your first remarketing campaign.
How do shoppers create, share, and edit a wish list?
The steps below reflect the standard flow across major platforms, with Amazon’s implementation used as the reference example throughout.
- Create a list — Log in to your account, navigate to your lists section, and select “Create a list.” Name it by occasion or project (for example, “Birthday 2026” or “Home Office Upgrade”).
- Edit item details — Open the list, select the item, and add a note (preferred colour, size, or a comment for gift-givers) and a priority level where the platform supports it.
- Share the list — Select “Share list” and copy the link, or send it directly via email. On Amazon, you can set the list to public, shared, or private before distributing the URL.
Amazon’s mobile app adds a layer of convenience here: Alexa voice commands can add items to a list hands-free, and push notifications surface price-drop alerts without requiring the shopper to return to the site. The Amazon help documentation notes platform exceptions, including certain pharmacy and out-of-print items that cannot be added to lists, which is a useful reminder for merchants in regulated categories.
Why do wish lists benefit shoppers?
The most direct benefit is deferred decision-making without losing the product. A shopper who is not ready to buy can save an item and return to it when budget, timing, or a gift occasion aligns, rather than relying on browser history or a screenshot.
Three practical use cases illustrate the range of value. A shopper building a birthday list shares it with family members, who can see what has already been purchased and avoid duplicates. Someone redecorating a room saves furniture and accessories across multiple retailers, using the list as a planning board before committing. A deal-conscious buyer saves high-ticket items ahead of Black Friday or Amazon Prime Day, then receives an alert the moment the price drops.
Privacy controls matter more than most merchants acknowledge. The ability to keep a list private until deliberately shared, or to hide purchased items from the list owner, addresses a genuine friction point in gift-giving. Shoppers who trust that their list behaves predictably are more likely to use it consistently, which in turn produces richer data for the merchant.
Why do wish lists help e-commerce merchants?
Wish lists are purchase-intent signals that arrive before a transaction, which makes them more valuable for merchandising and marketing than post-purchase data alone. BigCommerce notes that wish lists reduce cart abandonment by giving shoppers an intermediate save point, and they encourage account creation, which deepens the merchant’s data relationship with that customer.
The commercial upside is measurable. We Are ROAST’s research reports that wish list users place orders 50% larger and spend 30% more on average than non-list users, and that price-drop alert campaigns can yield substantial profit gains.
| Merchant benefit | Mechanism | Reported impact |
|---|---|---|
| Higher average order value | List users buy more items per session | Orders 50% larger |
| Increased spend per customer | Repeat visits driven by alerts | Spend 30% higher |
| Price-drop campaign revenue | Targeted alerts to list savers | Substantial profit gains |
A practical merchant actions checklist:
- Capture
add_to_wishlistevents in your analytics platform - Enable automated price and stock alert emails for list items
- Allow direct add-to-basket from the wish list view
- Use list data to build remarketing audiences in Google Ads and Meta
- Feed high-wish-list-volume products into inventory planning and bundle creation
How do you add a wish list to your store?
The right approach depends on your platform and the depth of integration you need. Built-in features offer the fastest path to launch; apps and plugins add richer functionality; custom builds are justified when you need deep inventory, CRM, or analytics integration.
- Shopify: no native wish list is included in the core platform, so merchants use apps such as those available via the Shopify app marketplace. The Swym Wishlist Plus app is widely used and supports email alerts, analytics events, and multiple lists. Free tiers exist; paid plans unlock advanced segmentation and automation.
- WooCommerce: several plugins provide wish list functionality, ranging from free options with basic add/remove behaviour to paid extensions that include email triggers and REST API access for headless builds.
- Magento (Adobe Commerce): native wish list functionality is included, with multiple lists and sharing built in. Extension marketplaces offer enhanced notification and analytics modules.
Integration checklist for any platform:
- Authentication: confirm lists persist across devices for logged-in users
- Analytics: fire
add_to_wishlist,remove_from_wishlist, andpurchase_from_wishlistevents - Notification channels: configure transactional email and, where applicable, SMS and push
- Inventory sync: connect list data to stock management so alerts fire accurately
- GDPR data handling: document the lawful basis for storing list data and provide deletion controls
- Mobile UX: test on iOS and Android before launch, including the share flow and notification opt-in
Pricing ranges from free basic plugins to SaaS add-ons at £10–£50 per month, with custom development costs varying by scope. For a detailed look at how platform choice affects overall store architecture, the e-commerce website design guide from MedwayWebDesign covers the decision framework for small UK merchants.
Wish lists as product-roadmap signals: the strategic view
Wish lists function as a personal catalogue that customers maintain across sessions, and that catalogue is a direct expression of purchase intent and product preference. For merchants and product teams, aggregated wish list data answers a question that surveys and focus groups rarely can: which products do customers want but are not yet buying, and why?
We Are ROAST’s research supports this framing: the gap between a product being saved and purchased is itself informative, indicating price sensitivity, seasonal intent, or a wait-for-stock behaviour that merchandising teams can act on. Large retailers use wish list volume data to prioritise restocking, negotiate supplier terms, and time promotional events such as Black Friday or Prime Day sales around items with the highest saved counts.
For product managers at SaaS companies or digital platforms, the same logic applies. A SaaS product roadmap informed by feature wish lists from users reflects actual demand rather than internal assumptions.
Pro Tip: Export your top-50 most-wishlisted products monthly and cross-reference them with your current stock levels and margin data. The overlap between high wish list volume and low stock is your highest-priority restock decision.
Legal and privacy considerations for wishlists
Wish list data is personal data under the UK GDPR, because it is linked to an identifiable user account and reveals purchasing intent and preferences. Merchants must document a lawful basis for collecting and processing this data, with legitimate interests or contract performance being the most commonly applicable grounds.
Practically, this means several obligations. The privacy notice must describe what wish list data is collected, how long it is retained, and whether it is shared with third-party marketing platforms. Shoppers must be able to delete their lists and have that deletion reflected in any downstream systems, including email marketing platforms and remarketing audiences. If wish list data is used to build advertising audiences, that use must be disclosed and, where consent is the lawful basis, explicitly opted into.
Shared lists introduce an additional consideration: when a shopper shares a list with a third party, the merchant’s platform may process the recipient’s email address. That processing requires a clear disclosure in the sharing flow. Retention periods for wish list data should be defined and enforced; indefinitely retaining the wish list of a customer who has not logged in for three years is difficult to justify under a proportionality test.
For merchants using third-party wish list apps or plugins, data processing agreements with those vendors are required under UK GDPR Article 28.
How wishlists interact with inventory management
A wish list is only as useful as the stock data behind it. When a product saved to a wish list goes out of stock, the platform should fire a back-in-stock alert the moment inventory is replenished, but that requires a live connection between the wish list system and the inventory management layer.
In plugin-based setups, this connection is often indirect: the wish list app polls product availability via the platform’s API at intervals, rather than receiving a real-time push event from the warehouse system. The result is notification delays, sometimes of several hours, which can mean a shopper receives a back-in-stock alert after the item has already sold out again. For high-demand products, that lag is commercially significant.
Merchants with more complex inventory needs, including multi-location stock, pre-order management, or third-party logistics providers, typically need custom middleware to ensure wish list alerts fire accurately and promptly. The checkout optimisation checklist from MedwayWebDesign addresses the downstream friction that occurs when stock data is inconsistent between the wish list view and the basket, a common source of abandoned purchases.
Real-time inventory sync also enables a more sophisticated merchandising tactic: when stock of a high-wishlisted product falls below a defined threshold, an automated campaign can alert all savers simultaneously, creating urgency without requiring manual intervention.
The case for starting with apps and knowing when to go custom
Most small UK merchants do not need a custom-built wish list on day one. A well-configured app or plugin, properly integrated with GA4 and an email platform, will capture the intent data and drive the re-engagement campaigns that generate measurable revenue. The marginal benefit of a bespoke build rarely justifies the cost until the business hits a volume or complexity threshold where the plugin’s limitations become a genuine constraint.
The decision to move to a custom implementation is usually triggered by one of four conditions: wish list events are not firing reliably in analytics; inventory alerts are delayed because the plugin cannot connect directly to the warehouse system; the brand experience on the list page is materially weaker than the rest of the site; or the business needs wish list data to feed a CRM or loyalty programme that the app does not support natively.
At that point, a custom build with proper API integration, event schema design, and mobile UX attention pays for itself quickly. The key is not to build custom prematurely, but to instrument the plugin correctly from the start so you have the data to make that decision with confidence rather than assumption.
MedwayWebDesign builds wish list features that actually convert
For UK merchants who want wish list functionality that goes beyond a basic plugin, MedwayWebDesign delivers end-to-end implementation: from selecting the right platform approach and configuring analytics event tracking, to designing a mobile-first list experience that fits your brand and connecting price and stock alerts to your email platform.
The difference between a wish list that sits unused and one that drives measurable re-engagement is almost always in the integration detail: GA4 events firing correctly, email sequences triggered by list behaviour, and a share flow that works on every device. MedwayWebDesign handles that detail as part of a broader e-commerce build or redesign, so the wish list feature is connected to your wider conversion architecture from day one. To discuss your store’s requirements, get in touch with the MedwayWebDesign team for a scoped proposal.
Sources and further reading
The sources below underpin the claims and figures in this article. Platform documentation is most useful for merchants evaluating specific implementations; the consumer research is most relevant for building the business case internally.
- Understand wish list features
- From dreaming to deciding: the role of wish lists in online purchase journeys | We Are ROAST
- What are wish lists and why are they important? | BigCommerce
- How to create and share Amazon Wish Lists
- Create and manage lists (Amazon help)
- 5 reasons why you need a wishlist feature on your e‑commerce store and how to choose one | Swym
- How do I use the Wish List feature? (3dcart support)