> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-online-help-contents-by-module/report-center/report/report-sales/sales-by-table.md). # sales by table Maitre'D sales by table report shows sales items information by table for the date or the period of time requested. From the report filter window, select the appropriate dates, amounts, invoice numbers, tables, employees, items, Revenu Centers and modes to be included in the report. The following is a sample of the sales by table report: ![Sample - Sales by Table](https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/ReportCenter/Sample-SalesByTable.jpg) The report is divided in two sections. For each table, the first section provides you with: **Table #** Table number. **Item #** Individual item numbers. **Item Description** Individual item descriptions. **Quantity** Total and individual item quantities. **Total** Total and individual item values. **Number of Check** Total number of checks. **Check Average** Total item value divided by total number of checks. For all tables, the second section provides you with: **Item #** Individual item numbers. **Description** Individual item descriptions. **Quantity** Individual and total item quantities. **Total** Individual and total item values. --- # 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.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-online-help-contents-by-module/report-center/report/report-sales/sales-by-table.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.