The variant couldn't be stocked at <same place> because the inventory is managed by <same place>

Fulfilment & Inventory
,
1

When attempting to activate an inventoryItem at a legacy location, we get the following error:

“The variant couldn’t be stocked at OUR LOCATION because the inventory is managed by OUR LOCATION.”

We are migrating from the rest API, using the id returned from the locations query, requesting legacy locations. A location was already created through the Rest API.

We are using inventoryActivate()
Our payload is:

{
“locationId”: “gid://shopify/Location/OURLOCATIONID”,
“available”: 10,
“onHand”: 10,
“inventoryItemId”: “gid://shopify/InventoryItem/OURINVENTORYITEMID”,
“stockAtLegacyLocation”: true
}

Likewise, we are unable to update the inventory for the location without manually changing the location in the admin UI. After that, all functions work correctly.

This was an automatic process in the Rest API.

Any help would be super appreciated…

2

Hello there @Geoffrey_Brown ,

I’m trying to reproduce this issue you are talking about and I didn’t receive the same issue as you.
When I ran the mutation with the input you provided, I received this error message:

The product couldn’t be stocked at LOCATION because not allowed to set available and on_hand quantities at the same time.`

When I removed the on_hand and left in the available, the mutation worked for me.

I’m not sure why this isn’t working for you. Sending the stockAtLegacyLocation: true should do the trick.

One thing I’m sure you’re already aware of is that the sku must have a value in order to be stocked at those “legacy” (aka. fulfillment services) locations.

If you could provide the ids of the inventory item and location, I might be able to do some further digging for you.
Or if you can try to run that mutation again and send me the request Id, I can help out.

Now, the other part you mentioned about not being able to update inventory, I’ll need more details. What mutation are you using? The inventoryAdjustQuantities?
What error messages are you getting back?

Let me know! And I hope I can help you out :slight_smile:

1 Like
3

Hi,
Our graphQl client doesn’t provide the requestId, unfortunately.

Is there another way I can provide this request data?

4

Disregard, the mutation was missing the stockAtLegacyLocation parameter, though supplied in the request, it wasn’t being utilized in the mutation query.