> 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/deal-report.md).

# Deal Report

The Deal Flash Report calculates all the Combo and Mix\&Match sales that occur from the beginning of the current period up to the time the Flash Report prints.

This report shows Combo and Mix\&Match sales for each NAXML promotion.

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

## Report Details:

* TITLE: DEAL REPORT

**COMBO DEALS:**

* C#: Combo number as it appears in the Deal File.
* DESCRIPTION: Name of the Combo Deal as it appears in the Deal File.
* \#CUST: Number of customers who purchased the item deals (individual transactions).
* \#COMBOS: Number of Combos Deals sold.
* TOTAL SALES: Combo Deal total sales in dollars.

**MIX-N-MATCH DEALS:**

* M#: Match number as it appears in the Match File.
* DESCRIPTION: Name of the match as it appears in the Match File.
* \#CUST: Number of customers who purchased the deals (individual transactions).
* \#MATCHES: Number of matches sold.
* TOTAL SALES: Mix\&Match Deals total sales in dollars.


---

# 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/deal-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.
