Returns are linked to one specific order. They get created in "draft" status and become "pending" when a customer requests to return SKUs from an order. Pending returns can be "approved" or "rejected". An approved return becomes "shipped" once it leaves the customer address. Returns are marked "received" once they reach the available return location, where they can be restocked to an inventory location.
A return object is returned as part of the response body of each successful list, retrieve, create or update API call.
The return unique identifier
The return endpoint URL
Unique identifier for the return
The return status, one of 'draft', 'requested', 'approved', 'cancelled', 'shipped', 'rejected' or 'received'
The email address of the associated customer.
The total number of skus in the return's line items. This can be useful to display a preview of the return content.
Time at which the return was approved.
Time at which the return was cancelled.
Time at which the return was shipped.
Time at which the return was rejected.
Time at which the return was received.
Time at which the resource has been archived.
Send this attribute if you want to activate this return.
Send this attribute if you want to mark this return as approved.
Send this attribute if you want to mark this return as cancelled.
Send this attribute if you want to mark this return as shipped.
Send this attribute if you want to mark this return as rejected.
Send this attribute if you want to mark this return as received.
Send this attribute if you want to restock all of the return line items.
Send this attribute if you want to archive the return.
Send this attribute if you want to unarchive the return.
Time at which the resource was created.
Time at which the resource was last updated.
A string that you can use to add any external identifier to the resource. This can be useful for integrating the resource to an external system, like an ERP, a marketing tool, a CRM, or whatever.
Any identifier of the third party system that defines the reference code
Set of key-value pairs that you can attach to the resource. This can be useful for storing additional information about the resource in a structured format.
The associated order.
The associated customer.
The stock location to which the return will be shipped.
The customer shipping address.
The associated stock location address.
The order line items associated to the return.
The associated attachments.
The resource environment (can be one of