Shopify cart not updating: refresh first

A cart does two things when a shopper changes a quantity: it sends the change to the store, and it redraws the page with the new number and total. Those two can separate. The number can change because the screen updated before the store confirmed anything, or because a second cart script drew its own copy. The total then shows the old price. A refresh returns the store's version, so the shopper sees one number on the screen, another after reload, and cannot tell which one they will pay.

• Change a quantity on a phone, then read the subtotal, not only the number beside the item.
• Refresh the cart page. Does the quantity you set still show?
• Open the browser console on a laptop and watch for errors after a change.
• Compare the cart count in the header with the number on the cart page.
• Try the same change in a private window with nothing saved, to rule out an old cart.

A quantity change moves through three places: the cart on the screen, the request that saves it, and the store's own record that the checkout reads later. If the screen changes and the other two do not, the shopper sees a cart that looks right while the order says something else. If the request saves and the screen never redraws, the shopper sees the old number and assumes the change failed. Both end the same way, with an order that does not match what the shopper expected to buy.

Change the quantity, then read three numbers: the figure beside the item, the subtotal, and the count in the header. Then reload the page and read them again. If the reloaded numbers match the change, the request saved and the screen is the part that failed. If they revert, the request never saved, and the screen was only showing what the shopper typed.

The first is a second cart script. Themes sometimes ship a cart drawer, an app adds another, and each one draws its own cart from the same data. The second is a request that errors, so the change never reaches the store while the page keeps the number the shopper typed. The third is cookies. A cart is tied to a browser cookie, and some in-app browsers, such as the one inside a social app, can limit or reset it, so each change looks like a fresh cart. The fourth is cache, where an old copy of the cart page shows stale numbers until it is fully reloaded.

Each cause has its own look. A second script shows two carts or two totals on one page. A failed request shows a number that reverts after a refresh. A cookie problem shows an empty cart after the change, and a cache problem shows a cart that changes on one device and not on another. Note which look you saw before you touch the theme.

Installing a cart drawer app, updating the theme or adding a discount widget can bring a second script onto the cart page without any visible change on your own screen. Rerun the same simulated visitors through a quantity change after each one, on a phone and a laptop, and reload the page afterward. Keep the steps identical, so the next run compares like with like.