> 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/pos/order-modification/accessing-the-order.md).

# Accessing the Order

1. In the POS, navigate to **Order History**.
2. Locate the **order** using any of the available **search and filter** tools:
   1. **Table Number** — for table service orders
   2. **Order Number**
   3. **Date** — filter by order date
   4. **Search field** — search based on customer information
      1. **Customer Name**
      2. **Delivery Address** — for delivery service orders
   5. **Status** — filter by order status (e.g., open orders, active orders, in progress, etc.)
   6. **Service** — filter by service type (Table, Takeaway, Collection, Delivery)
   7. **Brand**
   8. **Paid or Unpaid** — filter based on payment status

<figure><img src="https://1925381409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5cJdZdmiiIn3u107Grmv%2Fuploads%2FdEyGJ4dTVdTIiKdmEvk2%2Fimage.png?alt=media&amp;token=59e11bd6-e4d7-48f9-ae59-575c2ee539f8" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}

#### Order Visibility in the POS

The system automatically limits what orders different staff can see based on their role. Lower-level staff (like drivers and regular staff) can only see orders for the current shift, while managers and supervisors can see orders for the current shift plus future orders. Owners and senior managers can see everything, including past orders.&#x20;
{% endhint %}


---

# 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.bossithq.com/pos/order-modification/accessing-the-order.md?ask=<question>&goal=<user_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.
