> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-sales/plu-sales-summary-by-division.md).
# PLU Sales Summary by Division
Maitre'D PLU sales summary by division report shows PLU information by division for the date or the period of time requested. From the report filter window, select the appropriate dates, PLUs, and divisions to be included in the report.
The following is a sample of the PLU sales summary by division report:
This report is divided in two sections. For each division, the first two columns of the first section provide you with:
**PLU**
Code of the PLU.
**Description**
Description of the PLU.
For each division, the next eight columns of the first section provide you with:
**Qty.**
Quantity of PLU sold in each mode, by PLU and total for all PLUs.
**Amt.**
Value of PLU sold in each mode, by PLU and total for all PLUs.
For each division, the last two columns of the first section provide you with:
**Qty.**
Quantity of PLU sold in all modes, by PLU and total for all PLUs.
**Amt.**
Value of PLU sold in all modes, by PLU and total for all PLUs.
For each division, the first column of the second section provides you with:
**Division**
Description of the division.
For each division, the next eight columns of the second section provide you with:
**Qty.**
Quantity of PLU sold in each mode, by division and total for all divisions.
**Amt.**
Value of PLU sold in each mode, by division and total for all divisions.
For each division, the last two columns of the second section provide you with:
**Qty.**
Quantity of PLU sold in all modes, by division and total for all divisions.
**Amt.**
Value of PLU sold in all modes, by division and total for all divisions.
---
# 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.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-sales/plu-sales-summary-by-division.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.