> For the complete documentation index, see [llms.txt](https://help.hyteno.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hyteno.com/user-manual/readme/processing-orders.md).

# Processing Orders

<details>

<summary>Accepting/Rejecting the Order</summary>

1. Whenever you receive an order, a popup dialogue will appear in your mobile screen, with order details.&#x20;
2. Press on the view details button. On the order detail page, you have the option to accept or reject the order.
3. Proceed accordingly based on your status.

</details>

<details>

<summary>Tracking Past Orders</summary>

1. Go to the third icon on the bottom nav bar.&#x20;
2. You will see orders that are active and have not been settled on the first page.
3. You press "View Past Order" in the bottom center area to view settled orders.&#x20;
4. Alternatively, you can also search for any orders by order id in the top right corner.

</details>

<details>

<summary>Printing Order Receipt</summary>

You can print your order receipt by selecting print icon on the top right corner of order detail page.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.hyteno.com/user-manual/readme/processing-orders.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.