> 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/customer-+-item-sale-analysis/item-+-day-range-wise-sale-purchase-analysis.md).

# Item + Day Range Wise Sale/Purchase Analysis

Logic ERP has corrected the **Item + Day Range Wise Sale/Purchase Analysis** report. Each branch and item is now kept together instead of being split over many rows, **ITEM DESCRIPTION** is filled when extra item groups are used, the day range columns follow the report settings, and the report now works for an as-on date in any financial year.

***

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

* Navigate to **Reports/Queries** and select **Customer + Item Sale Analysis**.
* Open the **Item + Day Range Wise Sale/Purchase Analysis** report.

***

### **What's corrected**

* **Branch and item kept together.** When **Branch**, **Item** or both are ticked under **Report Consolidation**, every entry of the **Report Order** is now followed. Earlier, once the settings were saved again, the last entry of the **Report Order** was ignored, so one item at a branch could be split over many rows. The figures were right but spread out. The grand total does not change. In rare cases, where two different items have the same name, such an item can still appear on more than one row.
* **ITEM DESCRIPTION** and **ITEM NAME W/O SHADE** are now filled when **Extra Item Groups** are selected. Earlier these two columns were blank (or, with one extra group, **ITEM DESCRIPTION** showed the item name). The extra item group columns still show their group names.
* **Show Transacted Item Only** now also hides subtotal and grand total rows whose **TOTAL** is zero. Earlier these rows were shown even with the option ticked, and setting **Item Order** to **Item Name Wise** hid them even with the option not ticked.
* **Days Range** with a single range now shows that range, for example a **30 Days** column covering the last 30 days. Earlier a single range was replaced by **10 Days**.
* Older settings that have no day range stored now open the report with a **10 Days** column instead of giving an error.
* The report now reads the sales and purchases of the financial year (or years) covered by the day range up to the as-on date. Earlier, when the as-on date was in a different year from the one you were logged into, the report could show no rows or the wrong year's figures.
* The day range **ST(%)** figures on subtotal and grand total rows are now shown whenever both the sale and the purchase quantity are not zero. Earlier they could be left blank on items sold by weight or length when the purchase quantity in that range was half a unit or less.


---

# 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/customer-+-item-sale-analysis/item-+-day-range-wise-sale-purchase-analysis.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.
