> For the complete documentation index, see [llms.txt](https://docs.parcellab.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parcellab.com/docs/retain/returns-insights/shopify-returns-report.md).
# Shopify Returns Report
The Shopify Returns report provides an overview of returns performance for Shopify retailers.
## Use Case
The first section of Shopify returns analytics is the space.vars.Report\_RIShopifyReturns report, which focuses on overall return performance, offering a detailed view of return trends, refunds, and customer loyalty.
The top-level row shows the core metrics of this report and the available filters to refine the data.
The date the report was last refreshed is shown above the metrics. These metrics give you an overview of the performance of your returns operation, including the return rate, refund methods, the number of loyal customers (that is: customers that return to make another purchase after making a return), and revenue retention.
You can switch between comparing between defined dates and relative periods of time by selecting **Range** or **Relative** on the left-hand side of the Time range filter.
You can click the tabs to switch between insights for return trends and patterns, how returns are compensated, and customer retention.
More detailed charts are included in the space.vars.Report\_RIShopifyReturns report to help you gain key analytic insights into overall returns performance.
{% hint style="info" icon="book" %}
**Check out the parcelLab guides**
For further information on using the report and metrics, see our [user guide documentation](https://docs.parcellab.com/guides/returns/returns-insights/shopify-returns-report).
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.parcellab.com/docs/retain/returns-insights/shopify-returns-report.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
