Home›Extensions›Setting up Wishlist+

Setting up Wishlist+

Wishlist+ upgrades the wishlist your store already has into a full save-for-later and re-engagement tool. Shoppers can keep several named lists, save items without logging in, run a gift registry, share a list by link or email, and get an email when a saved item drops in price or comes back in stock. This guide takes about fifteen minutes.

Included with TitanCart Pro. Wishlist+ is part of your Pro subscription — there is no separate purchase and no extension license key to enter. Under Extensions → Installed Extensions it shows an Included in Pro pill instead of a key field. If it isn’t installed yet, install it from Extensions → Extensions Marketplace.

1. Turn Wishlist+ on

  1. Go to Growth → Wishlists.
  2. Under General, switch Enable Wishlist+ on.
  3. Click Save settings.

The master switch ships off, so this is a required step even on a fully installed store. Until it is on, your storefront keeps the basic built-in wishlist and no alert scanning runs. Turning it back off later pauses every Wishlist+ surface and stops the alert scan — saved wishlists are never deleted.

The Price & Stock Alerts and Share Anywhere sections on this page start collapsed. Click a section heading to open it.

2. Choose which list features to offer

In the Smart Wishlists section:

  • Multiple lists — on by default. Lets a customer keep more than one named list, such as “Birthday” and “Home office”. With it off, each customer keeps a single default list and attempts to create another are refused.
  • Guest wishlists — on by default. Lets visitors who aren’t logged in save items. Guest items are held against a browser cookie rather than an account.
  • Gift registries — on by default. Adds a List type choice when a customer creates or renames a list, with an event date and a description for registry lists, and a Registry badge on the list.

Know this about guest lists before you promise it. A guest’s saved items are folded into their account when they log in with email and password. They are not folded in at the moment a guest registers a new account, and not when someone signs in with Google or Facebook — those routes sign the shopper in by a different mechanism that the merge does not see. The items are not destroyed; they stay against the browser cookie and merge on a later ordinary login from that same browser. But a shopper who registers and immediately opens their wishlist will find it empty, and if they clear cookies first the items are gone. If you advertise “save now, keep it forever”, tell shoppers to sign in rather than to register.

The Gift registries field note mentions purchased-item tracking. That half is not built in this version — a registry is a public, shareable list with an event date, and nothing marks an item as already bought. Gift-givers can add registry items to their cart from the shared page, but the owner and other givers won’t see that it happened.

3. Set up price and stock alerts

In the Price & Stock Alerts section, choose which kinds of email a customer can receive about items they have saved:

  • Price-drop alerts — on by default. Sends when a saved item’s price falls below the price it was at when they saved it. After each send the baseline moves down to the new price, so the same item only emails again on a further drop.
  • Back-in-stock alerts — on by default. Sends when an item that was out of stock when they saved it becomes available again.
  • Low-stock alerts — off by default, because it is the noisiest of the four.
  • Deal alerts — off by default. Sends when a saved item goes on sale, meaning its list price rises above its selling price. A catalog promotion counts.

Two numbers sit underneath:

  • Low-stock threshold — the quantity at or below which a low-stock alert triggers. The default is 5.
  • Alert throttle — the minimum hours between repeat alerts for the same item and the same alert type. The default is 24.

These toggles are read once, when an item is saved — not when the email is sent. The moment a shopper adds a product to a wishlist, Wishlist+ records a baseline for each alert type that is switched on at that moment, and the alert scan works only from those recorded baselines. Two consequences, both silent:

Switching an alert type on does not reach backwards. Items already sitting on wishlists were recorded without it and will never trigger that alert. Only items saved after the change are covered.

Switching an alert type off does not reach backwards either. Items already recorded keep sending that alert. To stop them entirely, turn the master Enable Wishlist+ switch off, which pauses all scanning.

The same is true of Low-stock threshold: each saved item keeps the figure that was in force when it was saved. Changing it affects future saves only. Set these four toggles and the threshold the way you want them before you promote the feature, not after.

Beyond that, an alert only ever sends when all of the following are true:

  • The shopper is a logged-in customer. Alerts are never armed for guest lists, because there is no address to send to. A guest’s items become eligible only once they merge into an account.
  • The product is Active. Disabled and hidden products are skipped.
  • Your store can send email. Check this first under Settings → E-mails; the email test there is the fastest way to prove the transport works.
  • WordPress cron has run. The scan runs hourly, so an alert is never instant, and on a quiet site with little traffic WordPress cron can lag well behind the clock. If alerts matter to you, set up a real server cron job.

Low-stock alerts have two extra conditions that catch people out: the product must have inventory tracking switched on, and its quantity must be above zero. A product that has sold out completely never sends a low-stock alert — it is a back-in-stock candidate from that point on.

4. Set up sharing

In the Share Anywhere section, tick the share options you want to appear on public lists and registries: Facebook, X / Twitter, Pinterest, WhatsApp, Email and Copy link. Everything except WhatsApp is ticked to begin with.

New lists are private, and sharing is hidden until a customer makes one public. This is the single most common reason sharing appears not to work. A list is created private with no share link at all. The customer opens the list and clicks the padlock button, which reads 🔒 Private, to flip it to 🔓 Public. Only then does the share block appear — the share link box, the social buttons and the Email this list button are all inside it. There is no way for you to publish a customer’s list on their behalf.

A share link is your wishlist page with a code on the end, in the form ?tc_wishlist= followed by a 32-character key. Opening it shows a read-only view of that one list, with the owner’s name, any registry date and description, and an Add to Cart button on each available item.

You don’t need to build the page. Wishlist+ creates a published Wishlist page carrying the [titancart_wishlist] shortcode when it is activated, and it appears in Storefront → Pages as Shared Wishlist so you can reassign or recreate it. The share links follow that page’s real address, so renaming its slug is safe.

Alongside the social buttons, a customer can use Email this list to send it directly. That form accepts up to 10 recipients at a time and an optional note of up to 500 characters, and each customer is limited to 5 sends per hour. The email is sent from your store, so the same email-transport requirement as section 3 applies.

Switching a list back to private destroys its share key. Every link already handed out stops working permanently, and making the list public again mints a brand-new key rather than restoring the old one. Worth warning a registry owner about before their event.

5. What your customers see

  • On product pages and product cards — the heart button. With guest wishlists on, a visitor who isn’t logged in gets a working heart that saves the item, instead of a prompt to log in.
  • On the wishlist page — a logged-in customer sees My Wishlists, with a tab per list showing its item count and a star on the default one, and a + New list button when multiple lists are on.
  • Per list — Rename, Make default, the Private / Public toggle, and Delete. Delete only appears once there is more than one list, because a customer must always keep one.
  • Per item — Add to Cart (or a greyed Currently unavailable), a bell for alerts, Move and Copy to shift it between lists, and Remove.
  • The alerts bell — shown on each item whenever at least one alert type is enabled store-wide. Items are opted in automatically when saved; the bell is how a customer opts a single product out and back in. Alerts are product-wide, so opting out covers that product across all of their lists.
  • In the account area — the existing wishlist section at /my-account/wishlist/ is upgraded in place to the same multi-list manager.
  • A guest’s wishlist page — the saved items plus a prompt to sign in to keep them.

6. Test it end to end

  1. Prove email works first, under Settings → E-mails. Every alert and every shared-list email depends on it, and a silent mail failure looks exactly like a broken feature.
  2. Save an item while logged in, then create a second named list and use Move to shift the item across.
  3. Make the list public, copy the share link, and open it in a private browsing window. You should see the read-only view with your name on it.
  4. Send the list to yourself with Email this list, and check it arrives.
  5. Test an alert properly. Confirm Back-in-stock alerts is on, then save an out-of-stock product after that — an item saved earlier will not be armed. Restock the product, then wait for the hourly scan rather than expecting an immediate email.
  6. Test the guest path in a private window — save an item without logging in, then sign in with an existing account and confirm the item appears on the default list.

Limits worth knowing

  • There is no admin reporting. Growth → Wishlists is a settings page only. There is no list of customers’ wishlists, no most-wishlisted-products report and no log of alerts sent. If you need that data it has to come out of the database directly.
  • Registry purchases are not tracked, as described in section 2.
  • Alerts are for account holders only — guests are never armed.
  • Product names come from the English translation. Wishlist pages, shared lists and alert emails all read the product’s English name. On a store whose products are translated into another language and not into English, product names come through blank. Keep an English product name on file even if your storefront is in another language.

Troubleshooting

  • The Enable Wishlist+ toggle won’t switch on — this needs an active Pro subscription. On a Pro store the switch is not locked and there is no amber banner; if you see License required above the settings, the store isn’t currently reading as Pro. Check Extensions → Installed Extensions shows the Included in Pro pill.
  • The upgraded wishlist doesn’t appear on the storefront — the master toggle ships off. Confirm Enable Wishlist+ is on under Growth → Wishlists; until it is, customers see only the basic built-in wishlist.
  • Guests can’t save items — turn Guest wishlists on.
  • A guest registered an account and their saved items vanished — expected, and explained in section 2. The items merge on an ordinary email-and-password login from the same browser, not on registration and not on a Google or Facebook sign-in.
  • A customer says there are no share buttons — their list is still private. The whole share block, including Email this list, only appears once the list is switched to Public.
  • A share link that used to work now shows “This wishlist is private or no longer exists” — the list was switched back to private, which destroys the key. Making it public again produces a different link; the old one cannot be revived.
  • Alerts aren’t arriving — work through these in order: was the alert type switched on before the customer saved the item; is the product Active; is the customer logged in rather than a guest; can the store send email at all; has the hourly scan run; and has the throttle window passed since the last alert for that item.
  • Low-stock alerts never fire — the product needs inventory tracking switched on and a quantity above zero. A sold-out product is out of scope for low stock by design.
  • An alert type is still sending after you switched it off — expected. Items recorded while it was on keep their baselines. Turning the master Enable Wishlist+ switch off stops all scanning.
  • Product names show blank on wishlists or in alert emails — the product has no English translation. See Limits above.

See also

Previous
Setting up SMS Notifications
Next
Setting up Tips & Donations