> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/vip-naxml/reporting-vip-naxml/plu-report.md).

# PLU Report

The PLU Report uses the indicator "M" for NAXML Promotions in the RC (Reason code) field of the report. The "PRICE TOT-SALES" field contains the discounted price.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/dXzibapWtHbeH3y7Hga0/images/image40.jpeg)

## Report Details:

* TITLE: PLU REPORT
* PLU NUMBER: Identifies the product as it appears in the PLU File.
* DESCRIPTION: Description of the product as it appears in the PLU File.
* CUST: Number of customers who purchased the item (individual transactions).
* ITEMS: Quantity of the items sold.
* PRICE: Price of the item.
* TOT-SALES: Total amount collected for item sales.
* RC: Reason code identifies the method used to change the price of an item.
* % SALES: Percent of total sales that the items represent.
* TOTAL ITEMS SOLD: Total number of items sold.
* TOTAL SALES: Total amount of item sales.
* % OF TOTAL SALES: Percent of total item 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://commanderhelp.verifone.com/feature-references/features-and-products-references/vip-naxml/reporting-vip-naxml/plu-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.
