GraphQL productVariant inventoryLevel committed quantity is incorrect

Retired Boards Appdev Graphql Basics And Troubleshooting
,
1

The “committed” stock quantity reported in Shopify Admin and that returned by GrapghQL do not match.

Store: mascaralatex.myshopify.com

VariantID: 40935211597872

Title: BLUE TIGER - M

“Adjustment history” on the Shopify admin website reports committed stock as 2

40935211597872.png
40935211597872.png2438×762 77.3 KB

Graphql reports committed stock as 1

{“data”:{“productVariant”:{“id”:“gid://shopify/ProductVariant/40935211597872”,“displayName”:“BLUE TIGER - M”,“sku”:“16906-M”,“barcode”:“728633793938”,“inventoryItem”:{“id”:“gid://shopify/InventoryItem/43030224961584”,“inventoryLevel”:{“id”:“gid://shopify/InventoryLevel/4787372080?inventory_item_id=43030224961584”,“quantities”:[{“name”:“incoming”,“quantity”:0},{“name”:“on_hand”,“quantity”:58},{“name”:“available”,“quantity”:57},{“name”:“committed”,“quantity”:1},{“name”:“reserved”,“quantity”:0},{“name”:“damaged”,“quantity”:0},{“name”:“safety_stock”,“quantity”:0},{“name”:“quality_control”,“quantity”:0}]}}}},“extensions”:{“cost”:{“requestedQueryCost”:4,“actualQueryCost”:4,“throttleStatus”:{“maximumAvailable”:10000.0,“currentlyAvailable”:9996,“restoreRate”:500.0}}}}

Here’s my GraphQL query:

curl -X POST https://mascaralatex.myshopify.com/admin/api/2023-07/graphql.json
-H ‘Content-Type: application/json’
-H ‘X-Shopify-Access-Token: xxxxxxx’
-d ’ { “query”: “{ productVariant(id:"gid://shopify/ProductVariant/40935211597872") { id displayName sku barcode inventoryItem { id inventoryLevel(locationId:"gid://shopify/Location/4796547120") { id quantities(names:["incoming", "on_hand", "available", "committed", "reserved", "damaged", "safety_stock", "quality_control"]) { name quantity } } } } }” }’

I thought there may be a delay in the quantity updating, but there have been no changes to the stock for the past 12 hours and the GraphQL query is still different from the Shopify Admin inventory page.

Please help.

2

Hey @brdata , thanks for sharing this.

In this case, the first thing I would do is to double check that the location ID (4796547120), matches the location you’re looking at in the admin (01 Cuauhtemoc 105). If so, reach out to our support teams so we can take a look in to the store specific details to find out the reason for the discrepancy in the data returned.

When you reach out, make sure to also share the x-request-id and timestamp from your query. It will help us more quickly find this in our logs if needed.

Hope that helps

  • Kyle G.