Place the block
Add the save button to your product card and product page from the theme editor. It picks up your theme tokens, so it matches on the first load.
We are a Shopify Plus Agency specializing in custom development, B2B, checkout extensibility, ERP/CRM integrations, and retained support for scaling brands.
Book a Free Consultation →A wishlist that works without an account
Most wishlist apps ask a browsing customer to create an account before they can save anything, which is why most wishlists are empty. Wishlist+ saves first and asks later, then tells people when the thing they wanted is back or cheaper.
A customer who is browsing has not decided to buy, and asking them to register before they can save an item is asking for commitment at the exact moment they have least of it.
The list starts in the browser. If the customer later gives an email — for a back-in-stock alert, at checkout, or because they want the list on another device — the list follows them.
Saving is the easy half. The value is in what happens weeks later.
A save button on the product card and the product page that works immediately, with no login and no modal.
An app block you place in the theme editor, styled from your theme tokens rather than configured separately in a second dashboard.
The saved item is a stated intent with a timestamp. Telling that customer the moment it returns or drops in price is the highest-intent message a store can send, and it costs nothing to know who to send it to.
A wishlist is a demand signal that arrives before the sale. Which variants are saved and never bought, and which sizes are saved while out of stock, tells you what to reorder before the reorder is obvious.
A link, not an account. Which is how a wishlist actually gets used for birthdays and weddings.
Saves, alert sends, and revenue attributed to an alert rather than to the channel it happened to arrive on.
Add the save button to your product card and product page from the theme editor. It picks up your theme tokens, so it matches on the first load.
The list lives in the browser first. Nothing is asked for until there is a reason to ask.
Wanting a back-in-stock alert is a reason to give an address, which is why asking at that moment works and asking up front does not.
Back in stock, price drop, low stock. One message per event, on the channel they chose.
When to ask for an email, and what the list is worth to you rather than to the customer.
An email requested up front is a tax on browsing. The same email requested in exchange for "tell me when this is back" is a fair trade, and the opt-in rate reflects that.
Every save is a customer telling you what they want, dated, at variant level. That is better intent data than most analytics produce, and it is sitting unused in most stores.
Priced on saved-item volume and alert sends. The wishlist itself is on every tier.
Free
$0 / month
No usage charges
Starter
$4.99 / month
Growth
$14.99 / month
Scale
$24.99 / month
Charged through Shopify billing, so it appears on your Shopify invoice rather than as a separate subscription. Usage limits and any per-order charges are confirmed before you install.
Wishlist+ is a Shopify wishlist and back-in-stock app that turns a sold-out product into your next sale. Shoppers save what they love without creating an account, subscribe to be told the moment you restock, and you get demand data showing which products people are waiting for before you commit to a reorder.
No, and that is the point. The list starts in the browser the instant they tap the heart, with no login and no signup modal. An email is only requested when the customer wants something in return, such as a restock alert, which is what keeps the opt-in rate reasonable.
A guest list held only in the browser is lost, which is honest rather than ideal. Once a customer has given an email for an alert or checked out, the list is attached to their customer record and survives a cleared browser or a new device.
A shopper on a sold-out product enters their email under “Email me when it’s back”, and the moment inventory returns the alert sends automatically — no manual send, no export, no campaign to build. One shopper can watch several products at once and each is covered by the same subscription.
Yes. The product page can display the number of shoppers already waiting on that item, which is genuine social proof rather than an invented urgency timer — the count is the real subscriber list. It also tells you at a glance how much demand is sitting behind an out-of-stock line.
Yes. Shoppers can keep multiple named lists and organise saved products into collections rather than dropping everything into a single pile, which is how wishlists actually get used once a shopper is saving for more than one occasion.
Yes, by link straight from the wishlist page. That is what makes a wishlist useful for birthdays, weddings and gift lists — the recipient does not need an account or the app to open it, they just need the link.
Yes. Each saved product shows its current price with an add-to-cart button on the wishlist page itself, so a shopper coming back from a restock alert can buy without hunting for the product again.
Yes. The wishlist page and the save button are theme app blocks styled from your own theme tokens, so they match your type, colour and spacing on the first load. There is no second dashboard to restyle and no iframe that never quite fits.
Wishlist activity across the store — total saved products, total lists and total customers saving — alongside restock demand: how many subscribers are waiting, how many products have been requested, and how many restock alerts have gone out. It is demand data that arrives before the sale rather than after it.
Yes. Every subscriber is listed with the product they are waiting on and the status of their alert — pending, sent or opened — and the list is searchable by email or product with filters and sorting on top. You can also add a subscriber by hand when someone asks in a DM or in store.
Yes, both. Subscriber and wishlist data exports for a buying conversation, a supplier discussion or your email platform, and you can import an existing waiting list when you migrate from another app so nobody loses their place.
No. The save button is a theme app block rendered with the page rather than a script that mounts afterwards, so there is no layout shift and nothing blocking first paint.
Where an email platform is connected, alerts go through it so they follow your templates, your sending domain and your consent rules. Where one is not connected, the app sends them itself with editable templates.
Add the save button and the wishlist page from the theme editor and it is live — no code and no developer. The blocks work on any Online Store 2.0 theme; an older theme needs a small manual install, which we will do for you.
The saves themselves do not. The alerts do, because a back-in-stock message to someone who already saved the item is about as high-intent as ecommerce email gets. If you rarely sell out and never discount, the honest answer is that this app will do less for you.
Plans are not published on this page yet. Ask on a demo call and we will quote against your traffic, catalogue size and how much of it goes out of stock.
Book a demo and we will show you the save flow with and without the account step, on your own product page.
Tell us what you are building and we will come back with a straight read on scope — including when the answer is that you do not need us.