> 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/frontend-guides/customer-account/dashboard-overview/returns-and-claims.md).
# Returns and Claims
Create and track returns or claims for purchased items, from request to resolution.
The **Returns & Claims** section allows customers to manage returns and post-purchase claims. They can submit a return request for eligible orders, provide a reason, and track its progress - such as pending review, approved, or completed.
Returns are initiated from **Order Management** → **Order History**. The order list includes key details such as order number, status, value, customer, dates, delivery address, shipping cost, and payment method. You can use **Search** orders or **Show all orders** to find specific entries.
In the **Action** column, the **Return** option is available only for orders with a `COMPLETED` status. For other statuses, such as `CREATED`, the option remains disabled until the order meets the eligibility criteria defined in your configuration. If a return has already been requested for a completed order, the customer receives a notification that the request was already sent – it's not possible to send it again.
Order History — My Orders with return actions for eligible completed orders
The **Returns & Claims** view lists all the initiated returns.
Returns and Claims view
The customer can open each return entry to check its details.
Return details view
---
# 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/frontend-guides/customer-account/dashboard-overview/returns-and-claims.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.
