We are having the same issue. Is this a bug?
Topic summary
Main issue: After creating returns and choosing to restock items, the Refunds API is returning restock=false instead of reflecting the restock action. This behavior appeared after Shopify split “restock” into a separate UI action in the new returns flow.
Recent observations:
- Multiple users confirm restock=false despite restocking; screenshots show the new UI flow. Third‑party integration (Apparel Magic) marks items as “damaged” and inventory isn’t restored, requiring manual fixes.
- Documentation reportedly marks the refund “restock” field/function as deprecated, but there’s confusion: others note the existing API isn’t flagged as deprecated in practice and no migration path was communicated.
Open questions and data gaps:
- How to determine if an item was restocked and retrieve the location_id of the restock.
- Attempts via GraphQL (ReverseFulfillmentOrder → ReverseDeliveries → Dispositions) did not expose location_id or a reliable restock signal.
Status and outcomes:
- No resolution; Shopify support responses have been inconclusive and sometimes attribute issues to third‑party apps.
- Users seek an official replacement field/workflow and guidance to programmatically detect restocks and their location.