> 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/analytics/hourly-sales-report/accessing-the-hourly-sales-report.md).

# Accessing the Hourly Sales Report

In the [**Admin Portal**](https://admin.gobossit.com/), navigate to **Reports** > **Hourly Sales**.

Users can:

* Switch **data values** from Gross, Food & Drinks, Net
* Select a **date range**.
* Filter by:
  * **Service** — display data only for selected service
  * **Filter time** — display data based on either order creation date or order completion date
  * **Grouping time** — display data based on ETA, Prepare For, or Start Preparing At
  * **Ordering data type** — display data based on either order creation date or completion date
  * **Order Source** — display data only for selected source (pos, online, integrations)
  * **Day of week** — display data only for selected day(s) (e.g., Friday, Saturday, Sunday)
* Click **Today** to show only today's report.
* **Export** the file as XLSX.

<figure><img src="https://1925381409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5cJdZdmiiIn3u107Grmv%2Fuploads%2F4QT7gnbkASyNDxeYzzfX%2FScreenshot%202026-08-13%20at%203.16.34%E2%80%AFPM.png?alt=media&amp;token=51e3f310-73ec-4c65-b998-96f63457aded" 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/analytics/hourly-sales-report/accessing-the-hourly-sales-report.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.
