--- type: blog title: "What Is a Wish List? Saving Is Not Buying" description: "A wish list keeps products for later without placing an order. Learn how it differs from a cart, what survives sign-in, and what merchants should test." date: "2026-10-13" lastModified: "2026-10-13" authors: "Runner AI Team" tags: ["Customer Experience", "Store Operations", "Wishlists"] featured: false readTime: "5 min read" thumbnail: "https://storage.googleapis.com/runner-blog/blog/what-is-a-wish-list/cover" thumbnailAlt: "Cream product cards with a terracotta heart bookmark sit beside a ceramic mug on a warm cream tabletop." seo: title: "What Is a Wish List? Meaning, Examples, and Cart Differences" description: "Understand what a wish list saves, how it differs from a cart or gift registry, and why account persistence matters. Check these basics before adding one." --- What is a wish list? It is a collection of things someone wants to buy, receive, or consider later. In an online store, it saves products without placing an order. For a merchant, the important distinction is this: a saved item records interest, not payment, reserved stock, or a promise to purchase. A shopper might save a mug while comparing gifts, then return a week later. The useful part is not the heart icon. It is finding the same item again, understanding its current availability, and knowing whether the list belongs to a browser or an account. ## What is a wish list used for? The [Cambridge Dictionary definition](https://dictionary.cambridge.org/us/dictionary/english/wish-list) covers both a general list of desired things and the ecommerce meaning: products a customer would like to buy or receive as presents. Those uses share a purpose, but they do not all need the same features. Consider three illustrative examples: - **A personal shortlist.** A shopper saves two lamps while deciding which fits their room. Nobody else needs access. - **A gift list.** Someone collects birthday ideas and wants to share them with family. Sharing and privacy controls become important. - **A future purchase list.** A customer saves a specific shirt size for later. The store needs to preserve the choice and show whether it is still available. Start with the example your customers actually need. A private shortlist does not automatically need public links, gift reservations, reminders, or a registry. Each extra feature creates a separate promise you must support. ## Wish list vs. cart vs. registry A cart is the collection of items a shopper is preparing to check out. A wish list is a collection they want to keep for later. Neither is proof of a completed purchase. A gift registry adds a gift-giving workflow, which can include sharing and tracking purchases to avoid duplicate gifts. - **Wish list.** The customer wants to remember or compare products. Check whether saved choices persist and remain identifiable. - **Cart.** The customer is preparing a purchase. Check the current price, selected variant, quantity, and checkout eligibility. - **Gift registry.** The customer wants to tell others which gifts they want. Check sharing permissions and how purchases affect the list. [Amazon's own list guide](https://www.aboutamazon.com/news/retail/amazon-wish-list) provides a concrete example of platform-specific behavior. Its lists can be shared, and settings control whether purchased items remain visible. It also describes optional deal notifications. Those are Amazon features, not properties that every wish list inherits. Do not imply that saving holds a price or reserves inventory unless your store explicitly implements that guarantee. When the shopper returns, the product may have changed. Let them inspect the current details before moving it into a purchase. ## Where saved products live A browser-only list depends on that browser's storage. It can disappear when storage is cleared and will not automatically follow the shopper to another device. An account-backed list can associate the saved records with a signed-in customer. A guest list needs a way to identify it before an account exists. Runner's Wishlist implementation uses a store plugin rather than a list of product records kept only in the browser. Its storefront reference keeps a guest list identifier in browser storage while the store holds the saved items. After sign-in, the reference moves or merges the guest list into the customer's account. Guest saving also depends on the store's guest-wishlist setting. That distinction has a practical limit. Losing a guest identifier can make the list inaccessible to that browser, even if its records still exist in the store. Do not promise cross-device recovery to an anonymous shopper just because the data is stored on a server. Runner's source tests cover guest saves, removing one item, merging into an existing account without duplicates, and retaining the guest identifier after a failed transfer so it can be retried. They support the persistence design, not a claim that every deployed storefront already has wish-list controls. The store needs the plugin and compatible backend support; the storefront needs the corresponding integration. For the wider account and store context, start with the [Runner product guide](https://www.runnerai.com/docs/en/guides/product-guide). Keep a wish-list brief separate from checkout or marketing automation requests. ## Test the return visit Before offering a wish list, define what the customer should be able to recover. If a shirt comes in several sizes, decide whether saving means the product as a whole or the selected size. Our [product variations examples](./product-variations-examples) explain why a product and a purchasable variant are different records. Use this acceptance checklist for your store: 1. Save two products, refresh the page, and confirm both remain identifiable. 2. Remove one item and confirm the other stays saved. 3. Save the same choice twice and check that the result is not an accidental duplicate. 4. If guest saving is supported, save before sign-in and check the list afterward, including an account that already has saved items. 5. Use a second customer account and confirm it cannot see the first customer's private list. 6. Check a sold-out, deleted, or changed product. Explain its state rather than silently presenting an old price or an invalid purchase button. A saved item is also not permission to send a marketing email. Treat reminders as a separate consent and messaging decision. The [ecommerce email guide](./email-marketing-for-ecommerce) covers that planning work. Measure whether shoppers can return to the intended product and complete the next step. A larger save count alone does not establish more revenue or a conversion improvement. ## Common questions ### What is a wish list example? A list containing a blue mug, a medium charcoal shirt, and a desk lamp is a simple shopping example. It records desired items without buying them. A birthday list adds a different purpose: helping someone else choose a gift. Make the intended use clear before deciding whether sharing or purchase tracking belongs in the experience. ### Wish list or wishlist? Both forms appear in use. Cambridge uses the two-word form, while [Wikipedia's overview](https://en.wikipedia.org/wiki/Wish_list) lists both. Use one spelling consistently in your store's labels. The spelling does not tell customers whether the list is private, survives sign-in, or supports sharing; those behaviors need their own explanation. ### Does saving an item buy it? No. Saving records interest. The shopper still needs to choose any required options, check current availability and price, and complete checkout. Do not treat a saved item as an order or dispatch it to fulfillment. A purchase needs its own order and payment evidence, separate from the wish-list record. ### Can wish lists be shared? No. Sharing is a separate feature with its own permissions. Amazon documents sharing for its lists, but that is not a universal guarantee. Runner's supported storefront reference does not use the plugin's share routes. For your store, first choose between a private save-for-later list and a supported gift-sharing workflow.