Good afternoon,
The GraphQL mutation inventorySetQuantities
returns the ITEM_NOT_STOCKED_AT_LOCATION
error if the inventory item is not stocked at the location.
This works differently to the /inventory_levels/set.json
REST endpoint, which actually succeeds in this scenario, “silently” activating the location for the inventory item.
I understand that I need to call the inventoryActivate
GraphQL mutation to make it work, but I’m interested to find out why the behaviour was changed? Was there a genuine business case to support the change, or was it more about keeping the individual GraphQL mutations more focused?
Thank you!
Piotr