Refund
Requires access scope or access scope.
The record of the line items and transactions that were refunded to a customer, along with restocking instructions for refunded line items.
Anchor to Fields and connectionsFields and connections
- Anchor to createdAtcreated•Date
At Time The date and time when the refund was created.
- Anchor to dutiesduties•[Refund
Duty!] A list of the refunded duties as part of this refund.
- •ID!non-null
A globally-unique ID.
- Anchor to legacyResourceIdlegacy•Unsigned
Resource Id Int64! non-null The ID of the corresponding resource in the REST Admin API.
- Anchor to notenote•String
The optional note associated with the refund.
- Anchor to orderorder•Order!non-null
The order associated with the refund.
- Anchor to refundLineItemsrefund•Refund
Line Items Line Item Connection! non-null The
resources attached to the refund.- Anchor to refundShippingLinesrefund•Refund
Shipping Lines Shipping Line Connection! non-null The
resources attached to the refund.- Anchor to returnreturn•Return
The return associated with the refund.
- Anchor to staffMemberstaff•Staff
Member Member The staff member who created the refund.
- Anchor to totalRefundedSettotal•Money
Refunded Set Bag! non-null The total amount across all transactions for the refund, in shop and presentment currencies.
- Anchor to transactionstransactions•Order
Transaction Connection! non-null The transactions associated with the refund.
- Anchor to updatedAtupdated•Date
At Time! non-null The date and time when the refund was updated.
- Anchor to totalRefundedtotal•Money
Refunded V2! non-nullDeprecated
Anchor to MutationsMutations
- •mutation
Creates a refund for an order, allowing you to process returns and issue payments back to customers.
Use the
mutation to programmatically process refunds in scenarios where you need to return money to customers, such as when handling returns, processing chargebacks, or correcting order errors.The
mutation supports various refund scenarios:- Refunding line items with optional restocking
- Refunding shipping costs
- Refunding duties and import taxes
- Refunding additional fees
- Processing refunds through different payment methods
- Issuing store credit refunds (when enabled)
You can create both full and partial refunds, and optionally allow over-refunding in specific cases. The mutation also supports idempotent requests to safely retry failed refund attempts.
After creating a refund, you can track its status and details through the order's
refundsfield. The refund is associated with the order and can be used for reporting and reconciliation purposes.Learn more about managing returns and refunding duties.
Note- Anchor to inputinput•Refund
Input! required The input fields that are used in the mutation for creating a refund.
Arguments
- Anchor to orderorder•Order
The order associated with the created refund.
- Anchor to refundrefund•Refund
The created refund.
- Anchor to userErrorsuser•[User
Errors Error!]! non-null The list of errors that occurred from executing the mutation.
Fields
- •mutationDeprecated
- Anchor to returnRefundInputreturn•Return
Refund Input Refund Input! required The input fields to refund a return.
Arguments
- Anchor to refundrefund•Refund
The created refund.
- Anchor to userErrorsuser•[Return
Errors User Error!]! non-null The list of errors that occurred from executing the mutation.
Fields