> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-version-release-notes/october-2026/reports-queries/scheme-reports/scheme-wise-lot-stock-and-sales.md).

# Scheme Wise Lot Stock and Sales

Logic ERP has introduced a new **Scheme Wise Lot Stock and Sales** report. For the schemes made in [**Setup Schemes**](/logic-erp-learning-hub-tutorials-and-best-practices/setups/configurations/setup-schemes.md), it shows one row for each branch, scheme and lot — quantity and value sold, TD, CD, free quantity, closing stock and its value — so you can see which offers are running, which lots are moving and which are lying unsold.

***

### **Step 1: Open the Report**

* Navigate to **Reports/Queries** and select **Scheme Reports**.
* Open the **Scheme Wise Lot Stock and Sales**.
* Enter the **From** and **To** dates, and select **Scheme Group**, **Item**, **Branch** or **Extra Item Groups** if needed.

***

### **Step 2: Choose which sales are counted**

* Go to [**Configuration > Sales Options > Sales To Count**](/logic-erp-learning-hub-tutorials-and-best-practices/reports-queries/scheme-reports/scheme-wise-lot-stock-and-sales/scheme-wise-lot-stock-and-sales-configuration.md).
* **Bills Where Scheme Was Given** counts only the bill lines recorded with the scheme. It needs [**Record Group Wise Schemes**](/logic-erp-learning-hub-tutorials-and-best-practices/setups/configurations/sale-voucher-configuration/other-settings-1/record-group-wise-schemes.md) ticked in [**Setup\Configurations\Sale Voucher Configuration**](/logic-erp-learning-hub-tutorials-and-best-practices/setups/configurations/sale-voucher-configuration.md) (**Other Settings-1**) for the sale series; bills made while it was not ticked are not counted.
* **All Sales of Scheme Lots** counts every sale of the scheme's lots at the branch within the scheme dates. Use it when **Record Group Wise Schemes** has not been ticked.

***

### **Step 3: Read the report**

* **LOT NUMBER** and **LOT CODE**, **BRAND**, **PRODUCT**, **SHADE**, **ITEM NAME**, **PACK / SIZE** and **ITEM CODE** identify the lot.
* **SALE QTY**, **SALE VALUE**, **TD (%)**, **TD**, **FREE QTY**, **CD (%)** and **CD** show the sales in the period.
* **CLOSING STOCK** and **CLOSING VALUE** show what is left. The closing value rate is chosen in the configuration — the lot's MRP by default.
* **MOVEMENT** marks each lot **Fast**, **Slow** or **Non-Moving**.
* Columns such as **OTHER BRANCHES STOCK**, **OTHER BRANCHES SALE QTY** and **BEST SELLING BRANCH** can be switched on to see where the same lot sells better. On totals lines they count each lot once — the stock and sales at the branches outside that total.
* Scheme columns can be switched on to see each lot's scheme: **SLAB QTY / VALUE**, **SCHEME / UNIT**, **SCHEME RS**, **FREE ITEM** and **SCHEME FREE QTY** from the scheme slab, **SCHEME / UNIT AMT** and **SCHEME RS AMT** from the bills, and **SP CD (%)** and **SP CD** shown the same way as TD and CD. **FREE ITEM** shows **Multiple Free Items** when the slab has a list of free items.

***

For more detailed information, [Click Here](/logic-erp-learning-hub-tutorials-and-best-practices/reports-queries/scheme-reports/scheme-wise-lot-stock-and-sales.md)


---

# 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://kb.logicerp.com/logic-erp-version-release-notes/october-2026/reports-queries/scheme-reports/scheme-wise-lot-stock-and-sales.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.
