> 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/end-of-day-report/end-of-day-report-contents/open-orders.md).

# Open Orders

{% hint style="info" %}
Orders appear in the report based on their ETA, not the creation time.
{% endhint %}

The **Open Orders** section of the End of Day Report lists all unpaid and incomplete orders that require follow-up. When action is needed, this section is **highlighted in red** to draw attention. For each open order, the following details are displayed:

* **Order Number** — Unique identifier of the order.
* **Created at (timestamp)** — Date and time the order was created.
* **Service Type** — The mode of service.
* **Total Amount** — The total value of the order.
* **Paid?** — Indicates whether payment has been made.
* **Status** — The current progress of the order.
* **Actions**
  * Mark as Paid
  * Update Status
  * Comp
  * Void

{% hint style="info" %}
Comp and Void actions are only available on the same day. Tags cannot be applied retroactively.
{% endhint %}

<figure><img src="https://1925381409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5cJdZdmiiIn3u107Grmv%2Fuploads%2FdPvyUc3PIW7CCX99yXSN%2Fimage.png?alt=media&amp;token=77295e42-f6d7-4aa2-ae04-998d82b152ae" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1925381409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5cJdZdmiiIn3u107Grmv%2Fuploads%2F6e1RNm4hOA3jxLbWEtSh%2FIMAGE%202025-09-15%2016_43_19.jpg?alt=media&amp;token=ec506cf3-091a-4f55-bcb4-eb33bb5f429d" alt=""><figcaption></figcaption></figure>


---

# 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/end-of-day-report/end-of-day-report-contents/open-orders.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.