Hi Shopify team,
I’m working with the Shopify Admin GraphQL API and noticed an issue with the dateCreated field on InventoryTransfer.
I manually created an inventory transfer from the Shopify Admin and queried it using the following GraphQL query:
query MyQuery {
inventoryTransfer(id: "gid://shopify/InventoryTransfer/7610990767") {
dateCreated
id
name
events(first: 10) {
edges {
node {
createdAt
message
}
}
}
}
}
The API returned:
{
"data": {
"inventoryTransfer": {
"dateCreated": "2026-09-15T00:00:00Z",
"id": "gid://shopify/InventoryTransfer/7610990767",
"name": "#T0005",
"events": {
"edges": [
{
"node": {
"createdAt": "2026-09-15T02:01:59Z",
"message": "Estore Dayspring created this draft inventory transfer."
}
}
]
}
}
}
}
The concern is that dateCreated returns:
2026-09-15T00:00:00Z
while the corresponding event records the actual creation timestamp:
2026-09-15T02:01:59Z
This suggests that dateCreated is currently representing only the calendar date, with the time portion set to midnight UTC.
Why this is important
For applications that need to accurately determine when an inventory transfer was created, relying on events.createdAt is not ideal. The events connection is a separate data source and may not always be suitable or reliable for applications that need a dedicated creation timestamp.
It would be much more useful if InventoryTransfer.dateCreated returned the actual date and time when the transfer was created, similar to other Shopify resources that expose creation timestamps.
Expected behavior
For example:
dateCreated: "2026-09-15T02:01:59Z"
instead of:
dateCreated: "2026-09-15T00:00:00Z"
when the transfer was actually created at 02:01:59 UTC.
Could the Shopify team confirm whether this is the intended behavior of InventoryTransfer.dateCreated?
If so, could the field be updated in the future to preserve and return the actual creation timestamp?
This would be particularly helpful for applications that synchronize inventory transfers and need to accurately determine their creation time.
Thank you!
