

Customers can manage saved products, stock status and wishlist sharing from My Account.
Not every shopper is ready to buy on the first visit. When products are difficult to find again, purchase interest can disappear with them.
IPS Wishlist for WooCommerce gives shoppers a simple way to save products for later, manage favorites from My Account and share wishlists with friends or family. This creates more reasons to return to your store and gives saved products another opportunity to become purchases.
Instead of searching for the same products again, customers can keep their favorites in one convenient wishlist.
A wishlist does more than store favorites. It helps shop managers understand which products attract interest before customers are ready to buy.
The free Core edition includes guest and registered-customer wishlists, My Account management, sharing, back-in-stock notifications, basic reports and flexible storefront styling. It works as a standalone WordPress.org plugin and does not contact IPS license or update services.
IPS Wishlist Pro for WooCommerce extends the Core experience with multiple wishlists, individual visibility settings, drag-and-drop organization, estimate requests, advanced product-interest reports and targeted promotional emails.
The plugin stores wishlist records, saved product references, list names, visibility settings and dates needed to provide the wishlist feature. Logged-in customer data is connected to the WordPress user account.
When guest wishlists are enabled, an HTTP-only ipscmi_order_wishlist_session_<site-hash> cookie contains a random, signed session identifier and expiry data. Its default lifetime is 30 days and can be changed by site code through a WordPress filter. The corresponding database records remain until they expire or are deleted. The cookie is marked secure when the shop is served securely.
The optional back-in-stock email is disabled by default. When a shop manager enables it, its delivery queue can temporarily store the recipient user ID and email address, locale, referenced products and wishlists, and delivery metadata. Acknowledged payloads are cleared. Acknowledged notifications and permanently stale queued or expired-delivery jobs are removed after 30 days in bounded batches of no more than 100 records; active delivery leases are not removed by maintenance.
Email unsubscribe links use hashed, expiring verification challenges in WordPress user metadata. The plugin also stores the time at which a customer unsubscribed so that the preference remains effective. For registered customers, the WordPress personal-data exporter and eraser cover wishlist records, queued notifications and these email preferences. It exports only active and consumed unsubscribe-link counts, not verification-challenge values or hashes. Guest wishlists instead follow their expiry or explicit uninstall cleanup.
Deactivation does not delete plugin data. Uninstall also retains data by default. A shop manager can explicitly enable Delete plugin data on uninstall in the base Wishlist settings before uninstalling; that choice permanently removes wishlist records, queued notifications, email preferences and plugin settings. The currently configured Wishlist page is removed only when the plugin created it. An existing page selected by the shop manager is retained.
If a shop manager configures a custom icon hosted on another domain, visitors’ browsers request that icon from the selected host. The host’s own privacy policy then applies to that request.
The plugin does not send telemetry to IPS, and this WordPress.org package does not contact IPS update or license services.
This package includes the human-readable React source files, package metadata and build configuration needed to reproduce the distributed JavaScript assets. The production assets are built from the included ips-admin-react and ips-react source files. Core frontend integration and styling are implemented in the readable IPS presentation source under includes/classes/Wishlist/Presentation/Frontend/.
Development build overview:
npm ci --prefix ips-admin-react and npm ci --prefix ips-react.npm run build:wordpress-org-assets from the plugin root to build the WordPress.org Core assets.The exact third-party components and their licenses are documented in THIRD-PARTY-NOTICES.txt. Complete license texts are included in the package at the paths listed there.
THIRD-PARTY-NOTICES.txt. React, ReactDOM and the admin API client are supplied by WordPress and are not embedded in the plugin bundles.THIRD-PARTY-NOTICES.txt.