Return

The date and time when the return was closed.

The date and time when the return was created.

Additional information about the declined return.

The exchange line items attached to the return.

A globally-unique ID.

The name of the return.

The order that the return belongs to.

The list of refunds associated with the return.

The date and time when the return was approved.

The return line items attached to the return.

The return shipping fees for the return.

The list of reverse fulfillment orders for the return.

The staff member that created the return.

The status of the return.

A suggested financial outcome for the return.

The sum of all return line item quantities for the return.

The order transactions created from the return.

Retrieves a return by its ID. A return represents the intent of a buyer to ship one or more items from an order back to a merchant or a third-party fulfillment location.

Use the return query to retrieve information associated with the following workflows:

• Managing returns
• Processing exchanges
• Tracking reverse fulfillment orders

A return is associated with an order and can include multiple return line items. Each return has a status, which indicates the state of the return.

Removes return and/or exchange lines from a return.

Approves a customer's return request. If this mutation is successful, then the Return.status field of the approved return is set to OPEN.

Cancels a return and restores the items back to being fulfilled. Canceling a return is only available before any work has been done on the return (such as an inspection or refund).

Indicates a return is complete, either when a refund has been made and items restocked, or simply when it has been marked as returned in the system.

Creates a return from an existing order that has at least one fulfilled line item that hasn't yet been refunded. If you create a return on an archived order, then the order is automatically unarchived.

Use the returnCreate mutation when your workflow involves approving or declining requested returns outside of the Shopify platform.

The returnCreate mutation performs the following actions:

• Creates a return in the OPEN state, and assumes that the return request from the customer has already been approved
• Creates a reverse fulfillment order, and enables you to create a reverse delivery for the reverse fulfillment order
• Creates a sales agreement with a RETURN reason, which links to all sales created for the return or exchange
• Generates sales records that reverse the sales records for the items being returned
• Generates sales records for any exchange line items

After you've created a return, use the return query to retrieve the return by its ID. Learn more about providing a return management workflow for merchants.

Declines a return on an order. When a return is declined, each ReturnLineItem.fulfillmentLineItem can be associated to a new return. Use the ReturnCreate or ReturnRequest mutation to initiate a new return.

Processes a return by confirming which items customers return and exchange, handling their disposition, and optionally issuing refunds. This mutation confirms the quantities for ReturnLineItem and ExchangeLineItem objects previously created on the Return.

For returned items, you specify how to handle them through dispositions such as restocking or disposal. The mutation creates FulfillmentOrder objects for exchange items and records all transactions in the merchant's financial reports. You can optionally issue refunds through financial transfers, apply refund duties, and refund shipping costs.

Learn more about processing returns.

Reopens a closed return.

Creates a return request that requires merchant approval before processing. The return has its status set to REQUESTED and the merchant must approve or decline it.

Use this mutation when customers initiate returns that need review. After creating a requested return, use returnApproveRequest to approve it or returnDeclineRequest to decline it.

For returns that should be immediately open for processing, use the returnCreate mutation instead.

Learn more about building return management workflows.