Since last week we are getting following warning when we process the return with 0 refund amount.
Please help
How are you processing the return? If you’re not using the API to process the return your best option would be to connect with direct support at help.shopify.com
I am using GraphQL Process Return API to restock item when there is not refund to issue. In case of refund I call refundCreate api to refund and restock & than calling closeReturn api.
But even if I refund 0 amount directly from shopify it gives alert warning of Refund owned. I have attached screenshot for your reference. Due to this alert our merchants are getting confused when they have exchanged the item by creating new order in shopify and processing return order with 0 refund.
For your exchange workflow, here are a couple of approaches to clear that warning:
- Issue a $0 refund — After restocking via the return, call
refundCreatewith the return’s line items but a $0 amount. This signals to Shopify that the refund step has been explicitly handled (even though no money moved), and should clear the warning. - Close the return — Make sure you’re calling the
returnClosemutation after processing. This marks the return as fully resolved. Combined with the above, it should give a clean order state.
The key insight is that Shopify tracks returns and refunds as separate concerns — restocking items creates an expectation of a corresponding refund action, even if that action is $0. Explicitly completing that refund step resolves the warning.
Let me know if the $0 refund approach works for your use case!
Okay. I understand but even if I process return with 0 refund from shopify control panel. it gives return owned warning. The problem is that the way shopify display’s this Refund owned warning, makes merchant furious when merchant exchange same item but by creating new order and later when they visit original order they get warning about refund owned so they can’t keep track about it.
There should be setting to enable or disable this warning. As even if I use RefundCreate api and pass 0 as refund value it gives the same warning.
