carts/update webhook when a cart operation leaves the cart unchanged. A successful Ajax or Storefront API request is not evidence that a webhook should arrive. Compare the cart before and after the request, and only expect the event when contents or properties really changed.On this page
Why the webhook count suddenly dropped
Older integrations sometimes treated every cart write as a cart activity signal. Repeating the same quantity, submitting an already-present note, or sending identical cart attributes could produce another notification even when the cart stayed the same. Shopify changed that behavior on October 12, 2026: one webhook is sent for an actual change, not for every attempted write.
This matters for abandoned-cart scoring, session activity, analytics, and integrations that use webhook arrival as proof that a cart endpoint ran. A missing event may now be correct behavior rather than a delivery failure.
Separate three questions
Did the request complete? Inspect the Ajax or Storefront API response and any errors. Did the persisted cart change? Compare line IDs, quantities, properties, note, and attributes before and after. Did a change event arrive? Check the subscription, delivery logs, and the webhook consumer separately. Do not collapse these into one boolean.
Practical fix for event-driven integrations
Make the webhook handler idempotent and process the current cart state rather than incrementing a counter for every event. If your application needs to count attempted interactions, instrument those interactions at the storefront or app layer; carts/update is now a change notification, not a request log.
// Pseudocode: test the contract, not a fixed webhook count
const before = await readCart();
await updateCart({quantity: before.quantity}); // no-op
const after = await readCart();
assert(deepEqual(after, before));
// No carts/update event is expected for this operation.
For a real change, set a line to a different valid quantity, fetch the cart again, and correlate its resulting state with webhook deliveries. Preserve retries and deduplication: asynchronous delivery is not a synchronous acknowledgment of a cart API call.
carts/update event. The event represents changed cart data, not simply a successful request.How to test this
- In a development store, subscribe to
carts/updateand record deliveries with timestamps and cart identifiers. - Create a cart, then submit an update that repeats an existing value. Confirm the cart is unchanged; do not treat the absent event as an error.
- Change a quantity or property to a genuinely different value. Verify the new cart state and inspect the webhook delivery.
- Repeat a changed request with the same values and confirm your integration does not depend on a second notification.
- Test handler retries and duplicate deliveries separately; no-op suppression does not remove the need for idempotency.

