> 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/delivery-stats.md).

# Delivery Stats

The **Delivery Stats** section of the End of Day Report offers a comprehensive overview of delivery performance. This section includes:

* **Cooking Time** — The preparation time for the order before it is ready for delivery.
* **Waiting in Venue** — The time orders remain in the venue before being collected.
* **Wait to Tracked Delivery** — The average time between order completion and the start of delivery tracking.
* **Tracked Delivery Time** — The time taken by the driver from tracked delivery to arrival.
* **Waiting on Customer** — Any additional time waiting at the customer’s location.
* **Delivery Time —** Total delivery duration.
* **Order Completion Time** — Total time from order creation to delivery completion.

This section also includes:

* **Number of Orders** — The total delivery orders processed during the day.
* **Number of Drivers** — Total drivers who completed deliveries.
* **Distance (km)** — Total and average distance covered by all drivers.
* **Significant Items** — Significant products as defined by the system.

  [Significant Products](/menu/menu-structure/significant-products.md)
* **Delivery Legs** — The total number of delivery trips and the average per order.

<figure><img src="https://1925381409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5cJdZdmiiIn3u107Grmv%2Fuploads%2FCI9BgA7vgkIaBv97QJnV%2Fimage.png?alt=media&amp;token=0dcf538b-65b7-4bfb-8408-e9aed3755e38" 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/delivery-stats.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.