If your WooCommerce cart does not reflect an added item, quantity change, or removal, the cause is usually stale cache or session data, a failed AJAX request, a JavaScript or extension conflict, incompatible site settings, or a server-side delay or block. Diagnose the failing action first, then use the browser’s Network and Console tools to narrow down what is going wrong. Avoid testing plugin changes on a live store without a backup or staging site.
Start by identifying what is not updating
Note the exact action that fails: adding an item, changing its quantity, removing it, or loading the cart page. Compare the cart icon count, line items, and subtotal. If those disagree, record which view is stale and whether the problem happens consistently. These details help distinguish a display or cache problem from a request that did not complete.
As an Amazon Associate I earn from qualifying purchases.
WooCommerce cart actions can update through AJAX without a full-page reload. A failed request or a script error can therefore leave the visible cart out of sync with the expected result. WooCommerce’s AJAX troubleshooting guide explains how to inspect these requests.
The five causes to check
1. A cache or session is serving stale cart data
Cart and checkout pages contain dynamic, session-specific content and should typically be excluded from caching, according to WooCommerce’s guidance on WooCommerce pages not displaying. A browser, site, or server cache can show an old cart view. Session problems can also make the cart differ from what a shopper expects.
#1 Best Overall
WooCommerce uses the woocommerce_cart_hash and woocommerce_items_in_cart cookies to help detect cart changes. Its wp_woocommerce_session_ cookie contains a unique code used to locate a customer’s cart data; WooCommerce lists its duration as two days. See the WooCommerce cookie reference.
As a diagnostic, bypass or clear relevant browser and site caches, then repeat the action. Check that cart and checkout URLs are excluded from caching rather than relying on repeated cache clearing as a permanent fix.
2. The AJAX request fails or is blocked
Open your browser’s Developer Tools, select the Network tab, and reproduce the failing action. Inspect the relevant request’s status, headers, and response. WooCommerce’s AJAX guide describes common signals:
Recommended Free Tools
- 404: the requested endpoint or path could not be found.
- 500: a server-side error occurred.
- 403: the request was forbidden, potentially by a permission or security rule.
- Timeout: the request took too long; investigate server-side processing.
- Syntax error: the response may be malformed or not in the format the script expects.
These codes are clues, not a diagnosis by themselves. Save the request details and response so you can compare them after a change or share them with your host or developer.
3. JavaScript, the theme, or an extension interrupts the interaction
Check the browser Console for JavaScript errors while reproducing the issue. WooCommerce notes that JavaScript supports add-to-cart and cart and checkout interactions, and one browser error can interrupt functionality. Caching or script-optimization features, a theme, or another plugin may be involved. See WooCommerce’s JavaScript troubleshooting guide.
To isolate a conflict, test with a default theme and only WooCommerce active, then re-enable extensions one at a time. WooCommerce’s conflict-testing guide recommends making a backup before testing. Use a staging site whenever possible; do not deactivate plugins on a revenue-generating live store without a suitable safeguard.
4. Site URLs or checkout responses are incompatible
WooCommerce documents several AJAX-related problems specifically in its checkout troubleshooting guide. If checkout is affected, mismatched WordPress Address and Site Address settings can cause AJAX calls to fail. Check them in WordPress under Settings > General.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →That guide also describes checkout rendering problems when a request returns HTML where JSON is expected, and cached nonces that can produce a response of -1. These are checkout-specific mechanisms; they should not be assumed to explain every cart-page symptom.
5. A server delay, resource limit, or hosting rule disrupts the request
If the Network tab shows timeouts or server errors, investigate the server-side path rather than treating the symptom as a browser display issue. WooCommerce’s checkout guide identifies transactional email delays and insufficient WordPress memory as possible sources of failed checkout AJAX requests. For that checkout context, it gives a minimum recommended WordPress memory limit of 64 MB; that figure is not a general guarantee that a cart problem will be fixed by increasing memory.
Hosting firewalls, security rules, permissions, or blocked AJAX calls can also interfere with requests. The AJAX status and response are useful evidence when asking your hosting provider to check for a block or slow server process. See WooCommerce’s AJAX troubleshooting guide.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A safe troubleshooting sequence
- Record the failure: note the action, what changed on screen, and whether the cart count, line item, subtotal, or cart page is out of sync.
- Rule out stale data: bypass relevant browser and site caches for a diagnostic test, and verify that cart and checkout pages are excluded from caching. If appropriate, inspect the cart-related cookies described in WooCommerce’s cookie documentation.
- Inspect the request: open Developer Tools > Network, reproduce the action, and note the request status and response. Check the Console for JavaScript errors as well. WooCommerce provides steps in its AJAX guide and JavaScript guide.
- Check site URLs if AJAX fails: confirm WordPress Address and Site Address match under Settings > General, especially if checkout is affected.
- Test for conflicts safely: on staging or after a backup, update extensions and themes, switch to a default theme, and test with only WooCommerce active. Reactivate plugins one at a time until the problem returns. Follow WooCommerce’s conflict-testing guidance.
- Escalate with evidence: if the cause remains unclear, share the reproduction steps and relevant Network request and Console details with your host or a qualified WooCommerce developer.
When to ask for specialist help
Self-diagnosis is most useful when you can reproduce the problem and safely inspect browser tools or test on staging. Consider specialist help if the request returns a server error or timeout, a hosting rule may be blocking it, or the store cannot safely tolerate troubleshooting changes. WooCommerce’s AJAX guide names Codeable and a Woo Agency Partner as options for qualified assistance.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
