If your WooCommerce cart is not updating, customers may see the wrong quantity, an empty cart, old prices, a mini-cart that does not change, or products that disappear after they were added.
These problems are frustrating because the store can look fine. The product page loads. The Add to Cart button may even work. The problem appears only when WooCommerce tries to remember what is in the customer’s basket.
The safest way to diagnose it is to work from the visible symptom backwards.
WooCommerce cart not updating: symptom guide
| What the customer sees | Check first |
|---|---|
| Cart stays empty after adding | Cache, cookies, session |
| Mini-cart count is wrong | Classic cart fragments or block state, cache, theme |
| Quantity changes but total does not | AJAX/script issue, pricing plugin |
| Cart empties at checkout | Domain/HTTPS/session mismatch |
| Works for admin but not customers | Guest cache or security rules |
| Only some products behave wrongly | Product type, add-ons, stock, pricing rules |
If the problem starts one step earlier and products cannot be added at all, use the Add to Cart troubleshooting guide.
1. Test in a private browser window
Always test as a normal customer.
Open an incognito/private window and try this exact journey:
- Open a product.
- Add one item.
- Open the cart.
- Change quantity.
- Remove the item.
- Add it again.
- Go to checkout.
Write down the first step that behaves incorrectly.
2. Check relevant cache layers
WooCommerce uses customer-specific cart data. A stale cache can show old content even when the store has already changed the cart correctly.
Identify which layers are active, record their settings and clear the relevant cached content in a controlled test:
- browser cache;
- WordPress cache;
- hosting/server cache;
- CDN cache;
- object cache where your host recommends it.
Then test again in a fresh private window. Page cache and object cache are different systems; do not disable a shared object cache or purge customer sessions as a generic repair. Ask the host which cache exclusions and targeted purge apply to this store.
3. Make sure Cart and Checkout are not fully cached
Cart and checkout pages are dynamic. They should not be served as one fixed page to every customer.
If your cache or CDN treats them like normal pages, you can see:
- empty carts;
- stale totals;
- wrong shipping;
- old coupon state;
- quantity changes that disappear.
Most WooCommerce-aware caching plugins exclude these pages automatically. Problems often appear after custom cache rules or aggressive CDN changes.
4. Check whether the mini-cart is wrong or the real cart is wrong
Sometimes the main cart is correct but the little cart icon in the header is stale.
Test both.
If the cart page shows the right product but the mini-cart shows zero, the problem may be the mini-cart refresh rather than the customer session itself.
That is useful because it narrows the problem.
Check which cart your store actually uses
A classic cart widget and the Mini-Cart block do not use the same update mechanism. WooCommerce’s official cart fragments guidance explains that the Mini-Cart block does not use the cart fragments API. Since WooCommerce 7.8, the classic fragment script is no longer loaded on every page by default.
First identify whether the failing area is a classic widget, a block or a custom plugin component. Do not force a cart-fragments script onto every page as a universal fix. A block-based cart needs checks of its own requests, returned cart state and extension compatibility.
Ask for the failing request, not just an error screenshot
On staging, reproduce one quantity change and record the request, response body and resulting basket. A response marked 200 can still contain an error page or invalid data. HTML returned where cart data was expected is a clue to investigate, not proof of one particular plugin or firewall fault. Keep logs private and remove customer details before sharing them.
Custom options can create separate cart lines
With product configurators or add-ons, changing an option can intentionally create a different cart item. Compare the selected attributes, add-on data and cart line identity before calling it a session failure. Do not merge all items using only the product ID: that can combine genuinely different configurations and lose the customer’s choices.
Agree what a completed repair includes
Give the repair provider the affected URL, product and options, browser/device, guest or account state, first failed step, approximate time and recent changes. Ask them to record the cause, controlled change and rollback plan. Acceptance should include independent customer baskets, quantity changes, removal, coupons, variations, account login where relevant and a controlled checkout test with the correct order, totals and stock. A moving mini-cart icon alone is not enough evidence.
5. Check cookies and consent tools
WooCommerce needs a way to remember the customer’s basket.
If a cookie banner, privacy plugin or browser setting blocks the necessary WooCommerce session cookies, the cart may disappear between pages.
Test:
- before accepting optional cookies;
- after accepting them;
- in a different browser;
- on mobile;
- while logged out.
Essential shopping-cart cookies should not depend on marketing consent.
6. Check for www, non-www and HTTPS mismatches
If the site sends the customer from one version of the domain to another, the session can break.
Examples:
example.co.uktowww.example.co.uk;http://tohttps://;- shop subdomain to main domain.
Use one consistent canonical version throughout the store.
7. If quantity changes do nothing, check scripts and AJAX
Cart quantity updates often depend on browser scripts or background requests.
A JavaScript error can stop the button or spinner from completing.
Common causes include:
- script optimisation;
- theme conflicts;
- checkout/cart customisation plugins;
- dynamic pricing tools;
- security software;
- outdated templates.
8. Check for pricing and currency plugins
If quantity updates but the total is wrong, look at anything that changes price.
This may include:
- bulk discount plugins;
- dynamic pricing;
- currency switchers;
- membership pricing;
- product add-ons;
- subscription extensions.
Test the problem on staging with those extensions disabled one at a time.
9. Check WooCommerce Status for template warnings
Go to WooCommerce → Status.
Look for outdated template overrides.
A theme may contain its own copy of a cart template. After WooCommerce changes, that old copy can behave incorrectly.
10. Check whether a recent update caused the problem
If the cart was fine yesterday, ask what changed.
Check:
- WooCommerce;
- theme;
- payment plugin;
- cache plugin;
- security plugin;
- cart/checkout block;
- custom code;
- CDN settings.
Use a staging site for conflict testing if the live shop is taking orders.
11. Check whether the issue affects only guests
If administrators see a working cart but normal customers do not, this is a strong clue.
Logged-in users often bypass page cache. Guest visitors do not.
That makes caching, cookies and CDN rules the first place to investigate.
12. Check whether the cart fails only on mobile
A mobile-only cart problem may come from:
- mobile menu overlays;
- sticky bars;
- JavaScript loaded differently on mobile;
- mobile optimisation plugins;
- browser cookie settings;
- theme-specific mobile templates.
Test on a real phone, not only responsive preview.
13. Check whether products are actually staying in stock
If a product is added and then disappears, inventory rules may be involved.
Check:
- stock quantity;
- backorders;
- variation stock;
- hold-stock settings;
- external stock sync.
The dedicated WooCommerce stock guide covers inventory problems in more detail.
14. Test coupons separately
If the cart only behaves wrongly when a coupon is applied, do not treat it as a general cart issue.
Test the same basket:
- without a coupon;
- with the coupon;
- with a different coupon.
This can expose discount-rule conflicts quickly.
15. Re-test the full checkout after fixing the cart
A correct cart is only one step.
Complete a test order and confirm:
- totals remain correct;
- shipping updates;
- payment method appears;
- order is created once;
- stock changes correctly;
- confirmation email sends.
Our WooCommerce checkout guide covers the next stage if the cart works but checkout fails.
WooCommerce cart troubleshooting order
- Test as a logged-out customer.
- Find the first step where the cart becomes wrong.
- Check the relevant cache layers and test a targeted purge.
- Check cart/checkout cache exclusions.
- Check cookies and domain consistency.
- Check scripts and recent changes.
- Review template warnings.
- Conflict-test on staging.
- Complete a full test purchase.
When the cart problem is urgent
If customers cannot keep products in their basket, the shop may be losing sales without showing a visible site error.
Core Web UK provides urgent WooCommerce repair for broken live stores.
Cart problems can come from three different layers
| Layer | What it controls | Typical symptom |
|---|---|---|
| Browser | Cookies, scripts, local/session storage | One browser fails, another works |
| Cache/CDN | What page version the customer receives | Guest users see stale cart |
| WooCommerce/server | Session and cart calculations | Cart fails across devices |
Knowing the layer helps you avoid replacing themes when the real problem is a cache rule.
Test two customers separately
Use different browser profiles, different browsers or independent devices. Two private windows in the same browser can share cookies and a session, so they are not a reliable two-customer test. Add different products in each independent session. Each should keep its own basket.
If independent sessions receive another customer’s basket, investigate customer-specific cache and session handling immediately. The same empty or stale display in both sessions is a useful clue, but does not by itself prove a cache fault.
Check the cart after leaving and returning
Add a product, visit another page and return to the cart. Then close and reopen the browser if your store is expected to keep the session. This helps reveal cookie and session-lifetime issues.
What not to do
- Do not cache Cart and Checkout just to improve a speed score.
- Do not clear customer sessions on a busy store unless you understand the effect.
- Do not manually edit order/cart database records as a first fix.
- Do not test only while logged in as admin.
Check cart behaviour after login and logout
If your store allows customer accounts, test what happens when a shopper adds an item as a guest and then logs in. The basket should follow the behaviour your store is designed to support.
If the cart empties only during login, focus on session handling and any membership or account plugin rather than general page caching.
Check browser extensions only after the store itself is tested
An ad blocker or privacy extension can occasionally interfere with scripts, but do not blame the customer’s browser first. If several customers report the same problem, reproduce it in a clean browser and fix the store-side cause where possible.
Watch for cart problems after domain or hosting migrations
Migrations can change HTTPS settings, cookie domains, cache layers and CDN behaviour. A store may look correct visually while cart sessions fail.
After any migration, run a complete anonymous purchase journey before sending marketing traffic to the site.
Customer support clues are useful evidence
Messages such as “my basket keeps disappearing”, “quantity resets to one” or “I added it but checkout is empty” are not vague complaints. Record the wording and device/browser when possible. Repeated patterns often point to one layer of the cart system.
Run a cart test after any cache or CDN change
Store owners often change caching to improve speed and only later discover that baskets no longer behave normally. After changing LiteSpeed, Cloudflare, server cache or another optimisation layer, run a logged-out cart test before calling the work finished.
Check at least two products, quantity changes, removal, coupon use and checkout. Keep the test short and repeatable so you can use it every time performance settings change.
Record whether the cart problem is consistent or intermittent
A cart that fails every time usually has a clear configuration or script fault. A cart that fails only occasionally can point to cache variation, session storage, overloaded hosting or a race condition between plugins.
Ask affected customers for the approximate time, product and device. That information can be matched against logs and server load.
WooCommerce cart FAQs
Why is my WooCommerce cart not updating?
Common causes are caching, session cookies, JavaScript errors, outdated templates or plugins that change pricing and cart behaviour.
Why does my WooCommerce cart empty at checkout?
Check for caching, cookie problems and inconsistent domain or HTTPS settings. The customer may be losing the session between cart and checkout.
Why is the mini-cart count wrong?
The real cart may be correct while the mini-cart refresh is stale or blocked. Compare both before changing store settings.
Why does the cart work for me but not customers?
Administrators can bypass caching. Test while logged out in a private browser because customers may be receiving different cached content.
Should cart and checkout pages be cached?
They should not be fully page-cached like static content because they contain customer-specific information.
Want someone to keep your shop working? See our website maintenance services, with basket and checkout checks included in the WooCommerce plan.
