Saving, lists, and private sharing

With quick save enabled, a shopper with one list saves directly from the catalog or product page. The confirmation offers Undo for a newly saved item. Saving the same selection again does not create a duplicate. Undo will refuse to delete an item that has changed since it was saved.

Shoppers with multiple lists choose a destination. Free supports one list; Pro supports up to 50. Each list supports up to 1,000 distinct selections.

Saved selections include product options, quantity, and a private note. Products requiring a choice must have that choice supplied; the plugin does not guess an “Any” variation. Cart validation still runs through WooCommerce. Unsupported custom product add-ons need a dedicated integration.

Guests can begin without an account. Their session lifetime is set by the merchant. Account lists persist across devices. When guest and account selections have conflicting quantities or notes, both are retained for review rather than silently overwritten.

Lists start private. Unlisted sharing creates a secret, revocable link. Updating sharing invalidates the previous secret link. Public lists appear only if the merchant enables the public directory and the shopper publishes the list.

Shared views exclude private notes and account details. Anyone holding an unlisted link can open that shared view; share it intentionally. CSV exports and the owner’s print view can include private notes.

Pro includes cart save-for-later and public wishlist discovery. Free keeps a personal wishlist, direct sharing and wishlist-to-cart actions. Earlier Free beta users can retain the two moved features with the no-cost Beta Features companion. Public discovery requires the merchant to enable it and the shopper to make a list public.

Pro provides adapters for standard Product Add-Ons choices without uploads, complete Product Bundles and Composite Products parents, ordinary new simple or selected-variable Subscriptions, and standard Bookings date/time/resource/person/duration fields. The relevant vendor APIs must be installed. Prices and availability are rechecked in the cart; saving a booking does not reserve it.

Uploads, arbitrary metadata, renewal/switch/resubscribe operations and custom configurator input schemas are excluded. Cart save-for-later retains extra configuration only when the integration captured and signed it; otherwise it keeps the cart item and asks the shopper to reconfigure. Confirm your exact paid extensions on staging before use.