Why does my wishlist app only save the individual products from a bundle, not the bundle itself?
A shopper clicks add to wishlist on a bundle page and later finds three separate products saved instead of the bundle they actually wanted. Here's why that happens and how to fix it.
What's going on
A merchant sells a bundle, say a skincare starter kit made up of a cleanser, toner, and moisturizer, and adds a wishlist app so shoppers can save favorites for later. The problem: when a customer clicks add to wishlist on the bundle's product page, the wishlist doesn't save the bundle as one item. Instead it saves the individual components, or saves nothing usable at all, so the customer comes back later to a wishlist full of loose products at their individual prices rather than the bundle they actually wanted at the bundle price.
This isn't a one-off glitch. It comes up repeatedly wherever store owners run bundles alongside a wishlist app, because the two features weren't necessarily built with each other in mind. A wishlist app's save button typically records a product ID and sometimes a variant ID. Whether a bundle has a stable product ID of its own, one the wishlist app can grab, depends entirely on how the bundle was built, which is the root of the confusion.
Why it happens
Since 2024, Shopify has offered a native, free Bundles app that creates a fixed bundle as its own real product: it gets a product ID, its own price and image, and Shopify tracks each component's inventory automatically when the bundle sells. When a bundle is built this way, a wishlist app that saves by product ID should save it correctly as one item, so if it isn't, the wishlist app is likely misconfigured to grab component IDs instead of the bundle's own ID, often because its add to wishlist button was placed or coded to reference line items on the page rather than the page's primary product.
The harder case is mix-and-match or build-your-own bundles, which are usually powered by third-party bundle apps rather than the native Bundles app. In that model, the customer's specific combination of items often isn't a standalone product until it becomes a cart line at checkout, so there's no persistent bundle ID sitting in the catalog for a wishlist app to reference beforehand. That's a structural mismatch, not a bug either app can fix alone, which is why merchants run into it repeatedly with no clean out-of-the-box answer.
5 ways to fix it
Rebuild the bundle with Shopify's native Bundles app
If your bundle is a fixed, pre-defined set rather than something the customer assembles, switch it to Shopify's own Bundles app, which is free and available on every plan. It turns the bundle into a real catalog product with its own product ID, price, and image, and it tracks each component's inventory automatically. Once the bundle is a genuine product, most wishlist apps that save by product ID will save it correctly as one line, with no bundle-specific configuration needed. This is the free, native fix and the first thing to try.
Check your wishlist app for bundle or grouped-product settings
Before assuming your wishlist app can't handle bundles, check its settings and help docs for terms like bundle support, grouped products, or component products. Established wishlist apps let you control which product ID or block the wishlist button targets on a given page template. If your bundle page is currently wired to save components instead of the bundle, this is often a template or app-block setting your theme developer can correct without custom code.
For build-your-own bundles, save a snapshot instead of relying on a product ID
If your bundles are assembled by the customer through a mix-and-match app, there may be no single product ID to save until the items reach checkout. The practical workaround is custom: capture the chosen component list of product and variant IDs and quantities, plus a snapshot of each component's price and stock at the moment of saving, then re-validate that snapshot when the customer returns, since prices or availability may have changed. There's no native Shopify setting for this, so budget it as a small development project rather than an app toggle.
Have your theme developer confirm the wishlist button targets the bundle product
Even with the native Bundles app in place, some themes render bundle pages with extra blocks showing what's inside the kit, which can confuse a generically placed wishlist button. Confirm with your theme or app developer that the wishlist button is scoped to the bundle's own product object, not to the individual component blocks used for display. This is typically a quick fix once identified.
If the problem persists, compare wishlist apps on bundle support specifically
If the native Bundles app is set up correctly and your current wishlist app still can't be pointed at the bundle product, it may simply lack bundle-aware configuration. Compare wishlist apps on how they handle bundle and grouped-product pages before switching, rather than assuming all wishlist apps behave the same way.
Bottom line
Most of the time this is fixable for free: move fixed bundles onto Shopify's native Bundles app so they become real products with real IDs, then confirm your wishlist app's save button points at that product rather than its components. Build-your-own bundles are the genuine edge case, since there's no stable bundle ID to save until checkout, so getting a wishlist to remember a custom combination realistically needs some custom development to store the component list and a price and stock snapshot. If you're evaluating wishlist apps for a store that leans heavily on bundles, factor bundle support into that decision rather than assuming it will just work.
Browse the rest of the problem library, run a free storefront scan to catch issues like this automatically, or email us and we'll work out a custom solution for it.