> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/tutorials/omnitron/orders/how-to-manage-cancellation-and-return-requests-in-omnitron.md).
# How to Manage Cancellation and Return Requests in Omnitron?
This tutorial provides step-by-step instructions for managing Cancellation/Return Requests in Omnitron.
## Step 1: Access to Omnitron
* Get access to the Omnitron panel.
* Enter your Username and Password, and then click the **Sign In** button.\
## Step 2: Navigate to Cancellation/Return Requests Page
* Follow the **Orders** sidebar and click the **Cancellation/Return Requests** page.
* On the Cancellation/Return Requests page, the filter panel and the list of existing cancellation or return request lists are displayed.
* Users have the option to select the specific orders and perform the **Export to Excel with Selected Items** and **Export to CSV with Selected Items** actions.
* Cancellation/refund request list can be downloaded in XLS format through the **Download** button.
* To navigate to the Order Detail page, click on one of the selected Cancellation/Return Requests.
---
# 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.akinon.com/tutorials/omnitron/orders/how-to-manage-cancellation-and-return-requests-in-omnitron.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.
