Reviewed October 26, 2026

Shopify Cart Not Updating Quantities: Causes and Fixes

Quantity buttons that spin, ignore clicks, or revert are usually a JavaScript conflict, a drawer app clash, or stale cart code after a theme change. How to isolate the layer at fault.

Reproduce it like a customer first

Add a product, open the cart or drawer, and try changing quantity up, down, and to zero, on desktop and on a phone. Note exactly what happens: nothing at all, a spinner that never resolves, a brief change that reverts, or a page refresh that loses the change. Each symptom points at a different layer. Nothing at all suggests the click handler is dead. A reverting value suggests the update request runs but the response or inventory check pushes back.

Test in a private window to rule out your own browser extensions and cached scripts, and test more than one product, including a variant product. If only subscription or bundled products misbehave, you are looking at the app that manages them rather than the cart itself, and the rest of this guide applies to that apps support queue instead of your theme.

The JavaScript conflict layer

Modern carts update without a page reload by sending a request and redrawing the totals. When the scripts behind that break, through a theme edit, an app injecting conflicting code, or a jQuery version clash in older themes, quantity controls die while everything else on the page looks normal. Open the browser console on the cart page and click a quantity button: red errors appearing at that moment name the broken script more precisely than an hour of guessing.

Recent changes are the prime suspect, as always. A cart that worked last week and fails today after a theme update, an app install, or a tracking script addition has told you its own history. Roll back or disable the newest addition in a duplicate theme and retest. Developers call this bisecting. Store owners call it undoing the last thing, and it resolves a remarkable share of cart bugs.

Drawer, app, and inventory interactions

Cart drawer and upsell apps take over the cart experience and its update logic. Two apps both trying to own the drawer, or a drawer app running on a theme that also ships one, produces exactly the flicker and revert behavior owners report. Pick one owner for the cart experience, remove the other, and retest before deeper debugging. Loyalty, bundle, and subscription widgets that hook into line items are the next ring of suspects.

Do not skip the boring inventory check. A quantity update can legitimately fail when it exceeds available stock with overselling disabled, and some themes communicate that failure by silently reverting the number instead of showing a message. Try the same test on a product with deep stock. If deep stock updates fine, your bug is a messaging problem on low stock items, and the fix is surfacing the stock limit message your theme swallowed.

Fixing and preventing the sequel

Once the layer is identified, fixes are concrete: restore the unmodified cart template in a duplicate theme and reapply customizations one at a time, update or replace the conflicting app, or correct the theme script error the console named. Avoid stacking temporary script patches from forums onto a live theme. They tend to fix the symptom for one browser and move the failure somewhere quieter.

Then protect the fix. Keep a duplicate of the working theme untouched as a reference, note the apps that touch the cart in your store documentation, and after any future app install or theme update, run the sixty second cart circuit: add, increase, decrease, remove, on mobile and desktop. Cart bugs cost revenue by the hour and announce themselves to nobody, so the test habit is the real fix.

Frequently asked questions

Why does the quantity change then revert back?

The update request is failing or being rejected after the interface briefly shows the new number. Common reasons are a script error in the response handling, an app intercepting the update, or an inventory limit refusing the higher quantity without showing its message. The browser console usually names the failing script.

How do I tell if an app is breaking my cart?

Disable or bypass the newest cart related app in a duplicate theme, or preview an unmodified theme, and retest. If quantities work cleanly there, reintroduce apps one at a time. Cart drawers, upsells, bundles, and subscriptions are the usual owners of this bug.

Customers say the cart is broken but it works for me. Why?

Carts differ by browser, device, product type, and cached script versions. Reproduce on a phone and in a private window, test subscription and bundled products separately, and check low stock items, where legitimate inventory refusals can look like a bug when the theme hides the reason.

Is it safe to edit cart code from a forum fix?

Risky on a live theme. Work in a duplicate, keep the original file intact, and prefer identifying the conflicting script or app over layering patches. Forum snippets are written for other peoples theme versions and often move the failure instead of removing it.