> 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/item-insights-report.md).
# Item Insights Report
The Item Insights report provides an overview of the items returned by your customers.
## Use Case
Using this report, you can get further insight into your customers’ reasons for returning items. From the data, you can observe patterns in the types of items returned and the reasons those items were returned over time. The report can be filtered to display information by product.
## space.vars.Report\_RIItemInsights Report Features
The report can be filtered to display information by product to identify if there are common issues with certain products.
More detailed charts are included in the space.vars.Report\_RIItemInsights report to help you understand issues for returned items.
{% 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/item-insights-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/item-insights-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.
