> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/orders/order-history.md).
# Order History
The **Order History Page** provides a complete record of all previous orders. Users can view order details, including the order date, items purchased, quantities, payment status, and order status.
## Accessing Order History
In the [**Admin Portal**](https://admin.gobossit.com/)**,** navigate to **Orders > History.**
On this page, you can manually select the desired date range and enter the Order Number in the Search bar.
{% hint style="info" %}
You can also search using Just Eat's order number.
{% endhint %}
To further narrow your search, click the Filter icon located to the right of the Calendar selection button. Use the available filter options to help locate the order.
{% hint style="info" %}
Once you click the search icon next to **Order #**, an additional search bar will appear. You can use it to further narrow down your search.
{% endhint %}
\- Export to export file of all order you selected
### Filtering Order History
* **Service** — How the order was fulfilled (Delivery, Collection, Seating, Takeaway, etc.)
* Order Status — Order's current status ([Order Status](/web-app/order-creation/order-status.md))
* **Order Source** — POS, Online, Deliveroo, Just Eat, Uber, All
* **Client —** POS, Kiosk, Call centre, Web, IOS, Integration, Android
* **Payment Method** — Card, Cash, Online Cash, Anyexcuse, Just Eat, Deliveroo, Uber ([Payment Tenders](/payment-tenders.md))
* **Contains Payment Type —** Credit or Debit (Debit refers to refunds during checkout)
* **Tag —** Comp/Void tags
* **Order Type** — Sale or Refund (Refund refers to [Retroactive Refund](/refunds/types-of-refunds/retroactive-refund.md))
* **Paid —** whether the order is paid or not
---
# 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.bossithq.com/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.
