Rune
← All guides
WooCommerceJuly 30, 2026

WooCommerce Cart Not Updating Quantity? Here's What's Going On

WooCommerce cart not updating quantity? Learn what causes it, what fixing it involves, and the faster path to getting your store back to normal.

You notice something's off. A customer tries to change the quantity of an item in their cart — bumping it from 1 to 3, or removing one product before adding another — and nothing happens. The page just sits there. Or maybe it refreshes but shows the same number as before. Either way, the cart isn't updating, and that's a problem you can't afford to leave alone.

When the WooCommerce cart not updating quantity issue hits your store, it doesn't just frustrate shoppers — it costs you sales. Customers who can't adjust their order don't call you to sort it out. They leave. They find another store. And unless someone tells you, you might not even realize it's happening until you notice a dip in completed orders.

The good news is this is a known, fixable problem. The bad news is the cause isn't always obvious, and tracking it down usually involves poking around in areas most business owners aren't comfortable with — plugin settings, theme files, JavaScript errors, and caching layers. Here's what you need to know.

What Causes WooCommerce Cart Not Updating Quantity

The cart quantity update feature in WooCommerce relies on JavaScript running correctly in the browser. When a customer clicks "Update Cart" (or when the cart is set to update automatically), a script fires in the background that recalculates totals and refreshes the page. If anything interrupts that process, the cart appears to freeze.

The most common culprits are:

JavaScript conflicts. This is the big one. WooCommerce depends on a JavaScript library called jQuery to handle cart interactions. If another plugin or your theme loads a conflicting version of jQuery — or breaks JavaScript in some other way — the update function quietly stops working. The page looks fine on the surface, but underneath, the cart logic has hit a wall.

Caching problems. Caching plugins (like WP Rocket, W3 Total Cache, or LiteSpeed Cache) are great for speed, but they can serve outdated versions of pages to visitors. If the cart page is cached, customers might be looking at a stale snapshot of their cart rather than a live one. This is one of the more maddening causes because everything looks normal — it just doesn't work.

Theme compatibility issues. Some WordPress themes — especially heavily customized ones or page-builder themes — modify how WooCommerce scripts load. If your theme has been updated recently, or if you recently switched themes, that could be exactly what broke the cart. This is closely related to why you'll sometimes see website broke after update issues show up in WooCommerce stores specifically.

Plugin conflicts. Beyond JavaScript clashes, some plugins directly interfere with WooCommerce's cart logic — particularly optimization plugins, minification tools, or anything that modifies how scripts are loaded on the page.

Outdated WooCommerce or WordPress version. Running an old version of WooCommerce can introduce bugs that were already fixed in newer releases. The same goes for WordPress itself. Compatibility between WooCommerce, your theme, and your plugins gets trickier the further behind you fall on updates.

What Fixing WooCommerce Cart Not Updating Actually Involves

Fixing this issue isn't a single-button solution — it requires a systematic process of elimination. Here's what someone who knows what they're doing will actually do:

First, they'll check the browser console for JavaScript errors. This is the fastest way to spot a broken script. Even if the error message looks like gibberish to you, it tells a developer exactly where things went wrong.

Next, they'll test with all plugins deactivated (except WooCommerce) to see if the cart updates. Then plugins are re-enabled one at a time until the problem reappears — that's the conflict. It's tedious, but it's the right way to find the source.

Caching will be cleared at multiple levels — the plugin cache, server-side cache, and sometimes the CDN cache if one is in use. If a caching plugin is the culprit, it may need to be configured to exclude cart, checkout, and account pages from caching entirely.

If a plugin conflict is found, the fix might involve updating that plugin, replacing it with an alternative, or adjusting how scripts load across the site. In some cases, a small code adjustment is needed to ensure WooCommerce's own scripts load in the right order.

If it turns out to be a theme issue, the fix might involve updating the theme, switching to a WooCommerce-compatible theme temporarily to test, or making targeted changes to theme files.

This process touches multiple parts of your site — which is why it's worth having someone who does this regularly handle it. If you're already dealing with WooCommerce checkout errors on top of the cart issue, there's a good chance the same underlying conflict is responsible for both.

Signs This Is Your Issue

Not sure if what you're experiencing matches this problem? Here are the telltale signs:

If your store stopped behaving normally around the same time you made a change to your site, that's almost always the starting point worth investigating.

Should You Try to Fix It Yourself?

That depends on your comfort level — but for most business owners, the honest answer is: probably not.

The fix isn't dangerous if you know what you're doing, but it's also not intuitive. Disabling plugins one by one sounds straightforward until you realize you have 20 plugins active and your test environment doesn't match what real customers see. Clearing the cache sounds easy until you realize there are three or four different cache layers involved. And touching theme files or JavaScript loading order without knowing what you're doing can break other things on your site.

If you're technically inclined and comfortable working in your WordPress dashboard, you can try disabling plugins one at a time and testing the cart after each change. But if you're running a store that depends on working correctly, the risk of accidentally breaking something else during the diagnosis process usually outweighs the time saved.

It's also worth reading how to find someone to fix my website before you hand this off to just anyone — knowing what to look for in a repair service saves you from paying twice.

Common Questions About WooCommerce Cart Not Updating Quantity

Why does my WooCommerce cart not update when I click the update button? The most likely reason is a JavaScript conflict — something on your site is preventing the cart update script from running correctly. This is often caused by a plugin or theme that interferes with how WooCommerce's scripts load. Clearing your cache and testing with plugins disabled one at a time is the standard way to track it down.

Can a caching plugin cause the WooCommerce cart to stop updating? Yes, absolutely. Caching plugins can serve a saved version of your cart page instead of a live one, which means quantity changes appear to be ignored. Cart, checkout, and account pages should always be excluded from caching — this is a common misconfiguration that's easy to fix once identified.

Why does my WooCommerce cart work in Chrome but not Safari (or Firefox)? When cart behavior differs between browsers, it usually points to a JavaScript compatibility issue. Different browsers handle certain scripts differently, and a conflict that one browser tolerates might break another entirely. This is a useful clue for whoever is diagnosing the problem.

Did a recent plugin or WordPress update break my WooCommerce cart? It's very possible. Updates to WooCommerce, WordPress, your theme, or any plugin can introduce new conflicts. If the cart stopped working shortly after an update, that's almost certainly where to start looking. Rolling back the most recent update (carefully) is a common first diagnostic step.

How long does it take to fix a WooCommerce cart not updating issue? In straightforward cases — a single plugin conflict or a caching misconfiguration — it can be resolved in an hour or two. More complex conflicts involving custom themes or multiple interacting plugins can take longer to diagnose. Either way, it's not a multi-day project for someone who knows WooCommerce well.

The Faster Path

If your WooCommerce cart isn't updating and you'd rather spend your time running your business than debugging plugin conflicts, Rune was built for exactly this situation. It's a flat-rate website repair service — you describe the problem, and a real developer figures out what's broken and fixes it. No hourly billing, no retainer, no waiting a week to get on someone's calendar.

For store owners, cart and checkout issues are some of the most urgent problems there are. Every hour your cart doesn't work is an hour customers are quietly leaving without buying. If you've been sitting on this problem for a few days already, it's worth reading what a broken store is actually costing your business — the numbers add up faster than most people expect.

You can get started at runeintel.com. Describe what's happening with your cart, and Rune will take it from there — no technical knowledge required on your end.

More Fix Guides

Rather have someone else handle it?

Rune fixes website problems flat-rate. Most jobs done in 24–48 hours. No hourly billing, no surprises.

Get It Fixed →