A variable product is not saving as expected

How variation-aware saving works

GoScript Advanced Wishlist WordPress Plugin for WooCommerce reads the current WooCommerce variation selection when a signed-in shopper uses the wishlist button on a variable product. It stores the parent product, the selected variation where available, and the chosen attributes together.

1. Choose the options before saving

For the most precise result, select the product options first and allow WooCommerce to resolve the variation before choosing Add to Wishlist.

1. Open a published variable product while signed in as a test customer.
2. Select every required attribute, such as size and colour.
3. Wait for the product page to update with the selected variation’s price, availability, or other variation details.
4. Choose the wishlist button after the variation is resolved.
5. Open My Account → Wishlists and confirm that the saved item shows the selected product option.

2. What the plugin keeps with the saved item

The variation-aware model gives the customer’s wishlist more context than a general product bookmark. Each saved selection can keep the information needed to recognise the right product option later.

Parent productThe main WooCommerce product remains the foundation of the saved wishlist item.

Selected variationWhen WooCommerce resolves a valid variation, its variation ID is stored with the saved item.

Chosen attributesSelected variation attributes are normalised and kept with the item, such as the chosen size or colour.

Selection-specific identityThe saved selection uses a stable attribute fingerprint, so distinct choices can be recognised as distinct wishlist items.

3. Understand what a second click means

The wishlist button is a toggle for the same exact saved selection. That can look unexpected if you are testing quickly, but it keeps the customer interface simple.

• Clicking the button for the same parent product, variation, and selected attributes again removes that exact wishlist item.
• Choosing a different variation or a different set of selected attributes creates a different saved selection.
• Two distinct variations of the same parent product can therefore be kept separately when their selections differ.
• The customer’s overall product-interest reporting remains customer-product aware, so multiple selections do not artificially inflate Current Wishlisters for the parent product.

4. Check the theme variation form

The front-end button reads the standard WooCommerce variation form closest to it. Highly customised product templates can affect that connection if they replace the normal form structure or place the button outside it.

• Test the same product with a standard WooCommerce product template if your active theme or builder uses a custom variation interface.
• Confirm that the product options use WooCommerce’s standard variation fields and that a valid variation_id is set after options are chosen.
• If you use manual placement, place the Wishlist Button block or shortcode within the product’s variation-form context where possible.
• Clear page and browser caches after template or JavaScript changes, then test again in a fresh signed-in session.
• Check the browser console for JavaScript errors from theme or page-builder scripts that could interrupt product-option updates.

5. A quick end-to-end check

A clean test confirms whether the store is saving the correct option or whether the variation form needs attention.

1. Choose one variable product with clear attributes, such as colour and size.
2. Select a valid combination and note the displayed option.
3. Save it to the wishlist, then inspect the item in My Wishlist.
4. Remove that exact selection, choose a different variation, and save again.
5. Confirm that the second saved item reflects the new option and can return the customer to the appropriate WooCommerce purchase flow.