SaveTo Wishlist Lite – WooCommerce Wishlist

We aim to create the easy-to-use wishlist experience for WooCommerce — one that helps store owners grow. It's a feature-rich wishlist plugin that comes with everything you need to give your customers a great experience saving products to lists.

No, you and your customers can create as many wishlists as you like.

Yes, it does.

Open the page in UX Builder, click to add an element, and choose "Save to Wishlist" from the Content category. The element has two optional settings: a Wishlist ID, to pin the element to one specific wishlist, and a "Show the default wishlist only" toggle. Leave both alone and the element behaves exactly like the [saveto_wishlist] shortcode. This matters because a UX Builder page stores its own layout. If you rebuild your wishlist page in UX Builder without adding this element, the page has no wishlist on it to show. Adding the element puts it back. One limit worth knowing: place the element on the page itself. If you put it inside a reusable UX Block and then pull that block into a footer, a menu, or a custom product layout, the wishlist still appears but its scripts and styles will not load with it.

Yes, they can! Your users can create and name as many wishlists as they like to help them organize their shopping on your store.

Yes! With a single click, shoppers can bookmark items and curate a list of their favorite products to save for later.

Yes! Guests can save products without logging in. When they eventually create an account, all of their saved items are automatically merged, so they don't lose anything.

Yes, and SaveTo Wishlist adds a native "Save to Wishlist" module to the Divi Builder so you can place the wishlist exactly where you want it. Divi builds pages with its own layout system rather than the WordPress page content, so a page you have built with the Divi Builder — or a page covered by a Divi Theme Builder template — may no longer run the [saveto_wishlist] shortcode that the plugin's Wishlist page normally uses. (A Theme Builder template that includes Divi's own Post Content module still runs it.) If your Wishlist page looks empty under Divi, that is why. To fix it, open the page in the Divi Builder, add the "Save to Wishlist" module wherever you want the wishlist to appear, and save. The module also works inside Divi Theme Builder templates, so you can build one wishlist layout and reuse it across your site. Leave the module's "Wishlist ID" field empty and it shows each visitor their own wishlist. The module needs Divi 4, either the theme or the Divi Builder plugin. It appears in the builder's module list under its own name, alongside Divi's other modules. Divi 5 uses a new module system and is not supported yet.

Yes. The wishlist button works out of the box with Woostify, and the plugin ships Woostify-specific styling so the button looks native on Woostify's shop, archive and single-product templates — no custom CSS needed. Because Woostify rebuilds the WooCommerce product loop and uses its own product gallery, a couple of button placements are best avoided on Woostify. You'll find these options under SaveTo Wishlist → Settings → Button. Shop page — "Button Placement":

• Recommended: "Top Right of the Product Image" (the plugin default), "Top Left of the Product Image", "Above the Product Title", "Below the Product Title", or "Above the Add to Cart Button".
• Avoid "Below the Add to Cart Button". Woostify renders that row inside a fixed-height, animated area on desktop, so the button is clipped from view. If your shop is set to this placement, switch to one of the recommended options above for Woostify.

• Recommended: "Above the Add to Cart Button", "Below the Add to Cart Button", "Above the Product Title", or "Below the Product Title".
• Avoid "Top Right of the Product Image" (the plugin default) and "Top Left of the Product Image". Woostify's custom product gallery does not display the on-image button reliably, so Woostify stores should switch away from the default to one of the recommended options above.

Yes. The wishlist button works out of the box with Blocksy, and the plugin ships Blocksy-specific styling so the button looks native on Blocksy's shop, archive and single-product templates — no custom CSS needed. Every placement shows the button on Blocksy; the notes below tell you what to expect from each one. You'll find these options under SaveTo Wishlist → Settings → Button. Shop page — "Button Placement":

• All six placements show the button, but two of them sit in a different spot than their name suggests (see below). "Top Right of the Product Image" (the plugin default) is the best fit, because Blocksy keeps the card's top-left corner for its own Sale badge.
• "Top Left of the Product Image" shares that corner, so on a product that shows a badge there — Sale, out of stock, or a custom Blocksy badge — the wishlist button is moved down to sit under the badge instead of covering it. If your badge is unusually large, or you show more than one badge in that corner, use "Top Right of the Product Image".
• "Above the Product Title" and "Below the Product Title" both show the button between the product image and the title, because Blocksy renders its own title. "Above the Add to Cart Button" shows it directly below the title. "Below the Add to Cart Button" shows it after the Add to Cart button. All four follow your Blocksy card alignment, whether your cards are set to left, centre or right.

• All seven placements work. "Inline with the Add to Cart Button" sits beside the Add to Cart button on desktop and moves under it on narrow screens, where Blocksy's own button already fills the row.
• "Top Left of the Product Image" is moved down on a product that shows a badge in that corner, for the same reason as on the shop page.

On a block theme, WooCommerce builds the shop and category pages out of blocks, and SaveTo Wishlist attaches the button to the block that matches your chosen placement. Each placement uses a different block:

• "Top Right of the Product Image", "Top Left of the Product Image" and "Above the Product Title" attach to the Product Image block.
• "Below the Product Title" attaches to the Product Price block.
• "Above the Add to Cart Button" and "Below the Add to Cart Button" attach to the Add to Cart Button block.

• Pick a placement whose block is still in your template. For example, if you removed the Add to Cart Button block, switch from "Below the Add to Cart Button" to "Below the Product Title".
• Or add the missing block back to the Product Catalog template in Appearance > Editor > Templates.

Yes, and you do not need to write any code. With Popup Maker active, SaveTo adds four things to Popup Maker's own screens:

• A trigger called Product Added to Wishlist (SaveTo Wishlist). Add it to any popup and the popup opens the moment a customer saves a product, with an optional delay. It works for guests and logged-in customers alike.
• A targeting condition called Customer Has Wishlisted Products, under the SaveTo Wishlist group. Use it to show a popup only to shoppers who already have something on their list — perfect for exit-intent reminders. Logged-in customers are matched from their saved wishlists, and guests from the wishlist cookie described below.
• The SaveTo Wishlist shortcode in Popup Maker's shortcode picker, so you can show a customer's wishlist inside the popup itself.
• A View Wishlist (SaveTo Wishlist) call to action, which sends the shopper straight to your wishlist page and records the click as a Popup Maker conversion.

On every successful add, SaveTo emits two generic browser-side signals — for both guests and logged-in customers, and whether or not Popup Maker is installed. Use these if you want to build your own behaviour on top of a wishlist save:

• A DOM event on document named stwlite_added_to_wishlist, carrying event.detail = { productId, collectionId }. Use it for instant triggers. productId is the variation ID for variable products, and 0 when several products were saved at once (the "save cart to wishlist" button). collectionId is 0 for guests, whose items are stored in the browser rather than in a wishlist.
• A cookie named stwlite_wishlist_added, whose value is the URL-encoded product ID — run it through decodeURIComponent() before using it. Use the cookie for cross-page-load targeting such as exit-intent. It lasts 30 days and is cleared once the customer removes their last wishlisted product.