> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/user-guides/management-dashboard/orders-module/returns.md).
# Returns
Manage returns.
The **Returns** dashboard is where you can check all the returns that were created for the orders.
### Returns list view
In the returns list view, you can check and filter the results by the available columns.
You can also change the default view by using the options available under the orchestration icon.
{% hint style="info" %}
With the table orchestration, you can add custom columns to the list view, by adding **mixin** fields as columns.\
If you have already defined mixin schema for the entity, you'd be able to select the defined mixin fields to display them in the main view.
See example how to do it in the [Displaying mixins in entity list view](/user-guides/management-dashboard/settings/mixin-schemas.md#displaying-mixins-in-entity-list-view) documentation.
{% endhint %}
### Returns details
When you open a specific return view, you can check the details of a submitted return request.
For each return, you can check the reason code with return details, created date, return expiry date, status of the return and the name of the person who submitted the return.
Whenever you work on the return, you can change the status to:
* **Pending**
* **Approved**
* **Rejected**
* **Closed**
* **Reviewed**
---
# 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://developer.emporix.io/user-guides/management-dashboard/orders-module/returns.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.
.png?alt=media)
