WooCommerce variations not selecting or dropdown not working
When WooCommerce variation dropdowns stop responding, another plugin is usually throwing a JavaScript error that halts WooCommerce’s add-to-cart-variation.js, so the chosen options are never matched to a variation. If the dropdowns work but combinations show as unavailable, check the variation data itself: every variation needs a price, and attribute values must match. The console error on the product page will normally name the plugin to update or roll back.
What you'll see
On a variable product the size or colour dropdowns do not change, every combination is greyed out as unavailable, or the shopper picks everything and still gets the message "Please select some product options before adding this product to your cart." The price and stock text under the dropdowns never appear, and the add to cart button stays disabled.
Why it happens
1. A plugin error stops the variation script
WooCommerce uses add-to-cart-variation.js to match chosen options to a variation and fill in the hidden variation ID. An error from a tracking, payments or theme script earlier on the page can stop it from running.
2. A specific plugin release has a bug
Variation selection has been broken by individual plugin updates before; one WooCommerce Payments release was followed by a changelog entry fixing variation selection. A problem that started right after an update points here.
3. The variation data is incomplete
A variation without a price is treated as unavailable, and attribute values that do not match what the product offers, or "Any" combinations that overlap, can leave valid choices unmatched.
4. Large products load availability on demand
Above a threshold of variations (30 by default, adjustable with the woocommerce_ajax_variation_threshold filter), WooCommerce looks up each combination with a wc-ajax request. If caching or a firewall blocks that request, choices look broken.
How to fix it
- Open the product page with DevTools > Console showing, change each dropdown, and note the first error and the plugin folder named in its file path.
- Update the plugin named in the error, or roll back to its previous version if the problem began with an update, and read its changelog for a variation-related fix.
- In Products > Edit product > Product data > Variations, open each variation and check it has a regular price and a stock status, and that its attribute values match the product’s attributes.
- For products with many variations, watch the Network tab while choosing options. Requests to ?wc-ajax=get_variation should return data, not a cached page or a 403 from a firewall.
- Run a conflict test with Health Check & Troubleshooting Mode using a default theme and WooCommerce only, then reactivate plugins one at a time.
- If you use a swatches plugin, test with it disabled; swatches replace the dropdowns and must stay in sync with WooCommerce’s script.
How to check it's fixed
- Select every combination of options: the price and stock message should update for each, and impossible combinations should be disabled.
- Add two different variations to the cart and check the Cart page lists each with the attributes you chose.
- Reload the product page with the console open and confirm no errors appear before you interact with it.
What a QAlaunch scan shows for this
- JavaScript errors logged on product pages included in a paid report, with the file that caused them.
- Failed network requests, including blocked wc-ajax calls the page makes while loading.
- It does not choose every option combination and cannot tell whether your variation prices and stock are correct, so the data check is yours.
See exactly what a full report contains in the sample report.
Frequently asked questions
What does "Please select some product options" mean when I already did?
WooCommerce did not register your choice, usually because its variation script never ran or could not match the options to a variation. A console error or a variation with no price is the usual reason.
Why do only some products have this problem?
Products above the variation threshold load data differently, and individual products can have incomplete variations. Compare a working product with a broken one: number of variations, prices and attribute setup.
Do I need to rebuild the variations?
Rarely. Filling in missing prices or correcting attribute values is usually enough. Rebuilding is only worth it if the attributes themselves were renamed and the variations no longer reference them.
Rather have a QA engineer test it by hand?
If this is a site you're launching or handing to a client, I'll go through it by hand, including the WooCommerce-specific issues a scan can't reach, like logged-in flows.
- Up to 10 key pages tested by hand, not a scan
- Every flow a customer uses: forms, sign-up, checkout, booking
- Real mobile and desktop browsers
- A written report in plain language, with screenshots
- A 15-minute call to walk you through it
- 10 years of professional QA experience
Tell me about your site and I'll reply personally, usually the same day.
No payment now. I'll confirm scope and price first.
Related fixes
More for WooCommerce: all WooCommerce fixes · WooCommerce testing
Written by Waqas Ahmad, QA engineer with 10 years of professional testing experience. Last checked October 26, 2026.
Sources: WordPress.org support: product variations not selecting · WordPress.org support: cannot add variable product to cart