> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/day-to-day-operations/reports/sales-reports/quick-totals.md).
# Quick totals
**The quick totals report provides a clear and concise overview of store performance — including turnover (revenue), profit, and total number of sales.**
By default, the report shows data for today, but you can adjust the date range to compare any two days.
Each store is summarized individually, with a total across all stores displayed at the bottom. You can also drill down per store, viewing performance broken down by product group, all the way down to individual orders.
The report is available both in the Flow Retail Client and in Flow Retail Admin.
{% hint style="success" %}
Quick Totals is the most frequently used report in the system — a go-to tool for tracking daily sales performance.
{% endhint %}
### Explanation of the various columns in the report
Column
Explanation
Shop
Name of the store
Turnover
Total sale including VAT
Profit
Total profit excluding VAT
CM
Margin
Discount given
Total discount given
Cost
Total cost price excluding VAT
Quantity
Total number of sales
---
# 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.flowretail.com/docs/day-to-day-operations/reports/sales-reports/quick-totals.md?ask=&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.
