in_transit after scanning.
However, some merchants prefer greater control over the process by inspecting returned goods before completing the return. In this scenario, automatic processing is disabled, and Loop instead waits for Process or Flag events from the merchant’s warehouse system to complete or flag the return.
To implement this functionality, use the Process and Flag endpoints in our Returns API. This approach ensures alignment with your warehouse inspection workflow while maintaining manual control over the return inspection process.
A Process Return 200 with body true is an acknowledgement that Loop queued the work.
Confirm completion with return.closed.
Confirm a background failure with
return.processing.failed.
A 200 response with an errors body is a synchronous refusal. That case does not send the
failure webhook.
If you are flagging a return for manual review, we recommend also using the
Return Note
endpoint to document the reason for the flag within the return object in Loop.