Skip to main content

Making changeFromQuantity field required (with explicit opt-out)

This changelog relates to concurrency protection features.

Starting in 2026-04, the changeFromQuantity field will be required for the following mutations:

This is a breaking change. Note that even though the changeFromQuantity field doesn't show up as mandatory at the schema level, calling these mutations without passing in null or passing in the current actual quantity will result in an error at runtime.

What you need to do

Before migrating to version 2026-04, update your application logic to include the changeFromQuantity argument:

  • To enable concurrency checks (Recommended): Pass the expected current quantity.
  • To opt-out (skip checks): Explicitly pass changeFromQuantity: null

How to use the field

The changeFromQuantity field is useful to keep inventory data accurate, even if multiple updates are happening at the same time. If the actual quantity doesn't match the value you provide, the mutation will fail with a CHANGE_FROM_QUANTITY_STALE error, preventing unintended overwrites.

In the following example, the adjustment will only succeed if the current available quantity is 50. If another process has modified the quantity in the meantime, you'll receive an error and can retry with the updated value.

For more information on compare and swap, and when you should opt out of comparison checks, refer to our docs. We encourage users to avoid opting-out unless it's justified by their use-case.

  mutation {
    inventoryAdjustQuantities(
      input: {
        reason: "correction"
        name: "available"
        changes: [{
          delta: 10
          changeFromQuantity: 50
          inventoryItemId: "gid://shopify/InventoryItem/123"
          locationId: "gid://shopify/Location/456"
        }]
      }
    ) {
      inventoryAdjustmentGroup {
        id
      }
      userErrors {
        code
        message
      }
    }
  }
Was this section helpful?