Demfilz Wishlist for WooCommerce

No. The wishlist is stored in the visitor's browser and works for guests. Logged-in customers additionally get their list mirrored to their account so it follows them across devices.

One is created for you at activation ("Wishlist"). Add it to your menu, or pick a different page at WooCommerce > Wishlist - any page containing the [dwlw_wishlist] shortcode works. Logged-in customers can also use the Wishlist tab in My Account.

Additions follow a logged-in customer everywhere: each device merges the account list into its own on page load. Removing an item removes it on the device where it happens and on the account; another device that still holds the item locally can re-add it on its next visit. In short: additions always win. Guests are per-browser only.

Yes. Saving and viewing the wishlist uses no nonces for guests, so cached pages keep working. The list itself lives in the browser, never in the page HTML.

Yes. Hearts on variation rows in a product table save the parent product.

Use this plugin - it covers more surfaces (shop archives, My Account, count badges, account sync). If the table plugin's built-in wishlist is switched on, this plugin pauses its own buttons to avoid showing two wishlists at once, and the settings page tells you so. Anything customers saved with the built-in wishlist is picked up automatically the first time this plugin runs in their browser.

For guests: nothing on the server - the list of saved product IDs stays in the visitor's browser (localStorage). For logged-in customers: the same list of product IDs is saved to their user profile so it can sync across devices. No personal data, no tracking, no external requests.

Yes. Use the [dwlw_count] shortcode, or add the CSS class dwlw-count to any element (for example a menu badge) and the number is kept up to date.