> 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/tagged-orders.md).

# Tagged Orders

The **Tagged Orders** section of the End of Day Report records all orders that have been marked as Void or Comp. This allows for tracking and accountability of adjusted orders. Each tagged order displays the following details:

* **Order Number** — Unique identifier of the order.
* **Created at** — Date and time the order was created.
* **Service Type** — The mode of service.
* **Total Amount** — The total value of the order.
* **Tag** — Whether the order was voided or comped.
* **Reason** — Explanation for tagging the order.
* **Tagged By** — The staff member who applied the tag.

<figure><img src="/files/Z6IeNl3geozhs3KCzGt5" 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 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/end-of-day-report/end-of-day-report-contents/tagged-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.
