Shipment barcode not saved when created through API

GraphQL Admin API Troubleshooting
1

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.

3

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.

4

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.

5

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.