> For the complete documentation index, see [llms.txt](https://docs.cwsuite.com/pos/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cwsuite.com/pos/product-guides/reports/sales-by-payment-mode-report.md).

# Sales By Payment Mode Report

The Sales By Payment Mode Report in CW POS shows the distribution of sales by different payment modes across stores. The report typically includes the following columns:

* Store: The name or code of the store where the transaction was made.
* Customer: The name or ID of the customer who made the transaction.
* Order Date: The date on which the transaction was made.
* Document Number: The unique identifier of the transaction.
* Transaction Count: The total number of transactions made by the customer.
* Cash: The total amount of sales made by cash payment.
* Card: The total amount of sales made by card payment.
* Credit: The total amount of sales made by credit payment.
* Cash On Delivery: The total amount of sales made using the Cash on Delivery payment mode.
* UPI: The total amount of sales made using the UPI payment mode.
* NEFT: The total amount of sales made using the NEFT payment mode.
* Loyalty: The total amount of sales made using the Loyalty points.
* Gift Card: The total amount of sales made using the Gift Card payment mode.
* Sodexo: The total amount of sales made using the Sodexo payment mode.

<figure><img src="/files/Y6Ko7agGRFEmhnBU97T1" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cwsuite.com/pos/product-guides/reports/sales-by-payment-mode-report.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.