When WooCommerce Product Variations Stop Working: A Cookie Consent Plugin Case

Product variation issues can be especially dangerous for an online store because they are not always immediately visible. The product page may appear to work correctly, customers may still be able to place orders, and payments may continue to be processed.

Meanwhile, the store can quietly lose money with every purchase.

This is exactly what happened on one of the WooCommerce projects we support.

The Problem: Customers Selected One Variation, but WooCommerce Ordered Another

The issue appeared unexpectedly.

Customers could open a variable product, select the option they wanted, add it to the cart, and complete the payment. However, when the order appeared in the WooCommerce admin panel, it contained the first available product variation instead of the variation selected by the customer.

This was not simply a visual error on the product page. The incorrect variation was also used when calculating the order price.

In many cases, customers selected a more expensive product option but paid the price of the cheapest variation. As a result, the website started losing money.

At the same time, some customers reported a different problem: they could not add variable products to the cart at all.

The issue was inconsistent, which made it particularly difficult to diagnose. Some orders were placed successfully but contained the wrong variation, while other customers were unable to complete the purchase process.

Searching for the Cause

The website used a complex combination of WooCommerce extensions, FunnelKit functionality, and custom development.

Naturally, these components became the first suspects.

We checked the custom code responsible for product and checkout behavior. We investigated FunnelKit settings and tested whether other WooCommerce plugins could be changing variation data during the add-to-cart or checkout process.

However, none of these components turned out to be the source of the problem.

The selected variation was already being lost before the order reached the checkout stage. This suggested that the issue was happening directly on the product page, most likely while WooCommerce was processing the customer’s selection.

The Unexpected Cause: Cookiebot

Eventually, we discovered that the problem was caused by Cookiebot, a cookie consent solution that had previously been installed on the website.

Cookiebot was blocking or delaying certain WooCommerce JavaScript files.

WooCommerce relies heavily on JavaScript to manage variable products. These scripts detect selected attributes, find the corresponding variation, update the displayed price and availability, and send the correct variation ID when a customer adds the product to the cart.

Because some of these scripts were being blocked, WooCommerce could not reliably identify the selected product variation.

Depending on the situation, this produced two different results:

• WooCommerce used the first available variation instead of the option selected by the customer.
• The variation was not recognized at all, preventing the product from being added to the cart.

The cookie consent plugin was working as intended from a privacy perspective, but its configuration was not compatible with the website’s specific combination of WooCommerce, third-party plugins, and custom functionality.

How Cookie Plugins Can Affect WooCommerce

Cookie consent platforms often control when scripts are allowed to run. Scripts may be blocked until a visitor accepts a particular cookie category or until the consent platform classifies them as necessary.

This can create serious problems when an essential e-commerce script is incorrectly categorized as optional.

On a simple website, an incorrectly blocked script may affect analytics, embedded videos, or marketing tools. On a WooCommerce store, it can interfere with critical functionality such as:

• Product variation selection
• Dynamic price updates
• Add-to-cart requests
• Cart fragments
• Checkout validation
• Payment gateway initialization
• Address autocomplete
• Shipping calculations
• Custom product options

The more plugins and custom scripts a website uses, the more carefully the cookie consent system must be configured.

The Solution

Once Cookiebot was identified as the source of the issue, the necessary WooCommerce scripts and related functionality could be excluded from automatic blocking.

After correcting the cookie plugin configuration, product variations were selected properly again. Customers could add the intended options to the cart, and WooCommerce orders contained the correct variation IDs and prices.

It was also important to test the complete purchase process rather than checking only the product page.

We verified:

1. Variation selection on the product page.
2. Price changes after selecting different options.
3. Add-to-cart behavior.
4. Variation information in the cart.
5. Variation information during checkout.
6. The final product and price recorded in the WooCommerce order.
7. Behavior before and after accepting cookies.

Testing both consent states is essential. A store may work correctly after a visitor accepts all cookies but fail for new visitors who have not yet provided consent.

Cookiebot Is Useful, but Configuration Matters

Cookiebot and similar consent platforms can be valuable tools for privacy compliance. The lesson from this case is not that cookie consent plugins should be avoided.

The lesson is that they must be configured carefully.

Automatic script blocking can be convenient, but it should never be enabled on a complex e-commerce website without thorough testing. WooCommerce extensions, page builders, checkout plugins, custom JavaScript, and third-party integrations may all depend on scripts that a cookie platform could block or delay.

For stores with a complex technical setup, it is important to:

• Review which scripts are classified as necessary.
• Add exclusions for essential WooCommerce functionality.
• Test variable products before and after cookie consent.
• Check the cart, checkout, payment, and order data.
• Repeat testing after cookie plugin updates or configuration changes.
• Monitor orders for unexpected variation or pricing discrepancies.

Experiencing a Similar WooCommerce Problem?

When WooCommerce variations stop working, developers often begin by disabling product plugins, checkout extensions, or custom code. Those are reasonable places to investigate, but they are not the only possible causes.

When a problem affects product selection, dynamic pricing, or add-to-cart behavior, the cookie consent configuration should also be checked.

A misconfigured cookie plugin may block the scripts WooCommerce needs to recognize product variations correctly.

In some cases, the solution is not to remove the cookie consent system, but to configure the correct exceptions and ensure that essential e-commerce scripts are always allowed to run.

This case was a useful reminder that even a tool installed for compliance and security can affect core store functionality. Careful configuration and complete checkout testing are essential whenever a cookie management platform is added to a WooCommerce website.