Im getting restock false instead of return shopify api

I am returning an order, then restock and then refunded. but after restocking when I am retrieving refund using API, I am getting Restock= false, but is should be return

3 Likes

What If a line item is already fulfilled and then we create a return and restock the product? Then in the refund API, it should be Restock=true. but in the API response I am getting restock false.

2 Likes

We are seeing the same issue since restock has been a separate action in the UI, the API is returning restock=false when we believe it should be true.

1 Like

Then how we will get the Location ID where the Product is Restock?

1 Like

Also how we will get to know this product is restock again.

1 Like

We are having the same issue. Is this a bug?

If you look at the API docs it says the “restock” function is deprecated, so that’s why it’s not working. However I can’t find anything online about what replaced it, or how to receive this info back from Shopify via the API.

1 Like

I’m also facing a similar issue, this is so frustrating.

1 Like

Same issue here. We use Apparel Magic as an integration with Shopify and for the last several weeks whenever we initiate a return and check the box for the item to be re-stocked, it does not actually get re-stocked. Instead in Apparel Magic it is designated as “damaged”. But we see the same restock: false in the backend of the Shopify order. Tried to reach out to Shopify support and got nowhere- they said they were unaware of a problem and that it was most likely an issue with Apparel Magic since it is a 3rd party app. But it is super frustrating to have to go in to every item returned and update the inventory manually.

1 Like

Same issue here. After new returns feature was introduced restock is not a reliable field anymore. I got a explanation from Shopify here: https://community.shopify.com/c/shopify-apps/is-restock-type-field-reliable-for-handling-refunds/m-p/2527595#M76997 . It’s very annoying.

3 Likes

Thanks for sharing this. I agree that this is very frustrating. The existing api is not deprecated and no warning was given that it would cease to function.

1 Like

I’m trying to resolve this. I tested doing a restock in the new way and there is not location_id even following the graphql path of ReverseFulfillmentOrder->ReverseDeliveries->Dispositions… Support didn’t provide any useful answer for this either.

Thanks for the update. Please do let us know if you find a working solution…!

1 Like