> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/readme-1/work-with-work-orders/orders-order-history.md).
# Look up work order history
You can look up all transactions that are part of an open order (such as deposits and partial pick ups).
1. (Optional) Look up the customer. Refer to [**Look up customers**](/readme-1/work-with-customers/customers-looking-up.md) for more information.
2. Tap **Orders** | **Recalls** | **Recall a Work Order**.
3. To select the order, do one of the following:
* Tap the order once and tap **Add**.
* Tap the order twice.
4. Tap **Orders** | **Order Details** | **Order History**.
5. To view the details of a specific transaction listed in the **Order History** screen, do one of the following:
* Tap the transaction once and tap **Select**.
* Tap the transaction twice.
{% hint style="info" %}
The transaction receipt displays in the **Journal**. Tap **Close** to exit the **Journal**.
{% endhint %}
7. Tap **Cancel** to exit the **Order History** screen.
---
# 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://docs.rmhpos.com/readme-1/work-with-work-orders/orders-order-history.md?ask=&goal=
```
`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.