Hi everyone,
I’m using the GraphQL Admin API version 2026-10 to create an in-transit inventory shipment with inventoryShipmentCreateInTransit.
The shipment is created successfully, but the barcode supplied in InventoryShipmentCreateInput isn’t saved.
My input includes:
{
"barcode": "1234567891",
"movementId": "gid://shopify/InventoryTransfer/4688740533",
"lineItems": [
{
"inventoryItemId": "gid://shopify/InventoryItem/54862915436725",
"quantity": 1
}
]
}
The example above is shortened. The actual request contains five line items and uses the @idempotent directive.
The response from the actual request is:
{
"data": {
"inventoryShipmentCreateInTransit": {
"inventoryShipment": {
"id": "gid://shopify/InventoryShipment/1743749301",
"name": "#T0185-1",
"barcode": null,
"lineItemsCount": {
"count": 5
}
},
"userErrors": []
}
}
}
Expected behavior: The shipment’s barcode is saved as "1234567891".
Actual behavior: The shipment is created, but barcode is null, with no user errors. A separate read of the shipment also returns barcode: null. I reproduced this using a fresh idempotency key.
Thanks.
Hi @Michael_Cheng this matches a known issue where inventoryShipmentCreateInTransit accepts the barcode but doesn’t persist it. Your use of barcode in InventoryShipmentCreateInput is correct. You’ve also already checked the shipment separately and reproduced the issue with a fresh idempotency key.
As a workaround, set the barcode on the existing shipment using inventoryShipmentSetBarcode:
mutation SetShipmentBarcode($id: ID!, $barcode: String!) {
inventoryShipmentSetBarcode(id: $id, barcode: $barcode) {
inventoryShipment {
id
barcode
}
userErrors {
field
message
}
}
}
Using the values from your example, provided the barcode is unique:
{
"id": "gid://shopify/InventoryShipment/1743749301",
"barcode": "1234567891"
}
This updates the shipment you’ve already created, so there’s no need to recreate it.
Let me know whether this saves the barcode successfully. If it doesn’t, please share the mutation response, including any userErrors.
Hi Yoni:
Is there a target date for this bug to be fixed, or do we have to wait for the next version?
I would appreciate it if you could leave a message in this thread once it is fixed.
Thanks.
I don’t have a fix timeline to share, and I can’t confirm yet whether an API version change will be needed. The workaround above is available in 2026-10.
I’ll share any updates here.
Hi Michael, I’ve confirmed that the fix will apply to 2026-10, so you won’t need to change API versions. I’ll update this thread once it’s available.
I just retested in the Development Store today, and the barcode appears to be fixed.
In Production, I suspect the response includes the barcode value, but the system does not actually save it to the shipment. I cannot provide the response payload right now, but here are the details for the API call:
-
Date: Oct 27, 2026, 22:46:44 GMT-04:00
-
Correlation ID: 8a06273f-5774-4dc3-85c5-e3e682e5b768
-
Shipment GID: gid://shopify/InventoryShipment/2816377032
-
Shipment ID: #T0292-1
Thanks for retesting. Glad to hear it appears to be working in your development store.
For production shipment 2816377032, could you share the result of a separate API query for its barcode, along with the store’s .myshopify.com domain? That will help confirm whether the value is missing from the saved shipment or only from the admin. We can start with those details while the creation response is unavailable.
I couldn’t find a matching request using the correlation ID you shared. Was that ID taken from Shopify’s X-Request-ID response header?
Forum thread
Hi Yoni,
I suspect in Production, inventoryTransfer return the barcode wihtout save it into the shipment, but it is hard for me to prove it since it will null as the barcode value today.
Will wait for your update when the fix move to PROD.
Thanks.
Hi @Michael_Cheng the fix is now available in production.
When you next create a shipment with inventoryShipmentCreateInTransit, could you query that shipment separately and let me know whether the barcode is saved?
Hi Yoni:
Confirm barcode saved to the shipment, thanks.