> 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/branch-customer-wise-top-bottom-items-analysis.md).

# Branch/Customer Wise Top/Bottom Items Analysis

Logic ERP has corrected the **Branch/Customer Wise Top/Bottom Items Analysis** report so that the items of each branch and party stay together in one block, whatever **Report Order** is saved in the settings.

***

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

* Navigate to **Reports/Queries** and select **Customer + Item Sale Analysis**.
* Open the **Branch/Customer Wise Top/Bottom Items Analysis** report.

***

### **What's corrected**

* When **Branch**, **Party** 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 the items of one branch or party could be split over several blocks, each showing its own top or bottom items. In rare cases, where two different parties have the same name, a party can still appear in more than one block.
* Settings that were not saved again since the earlier version show the same result as before.
* Where a branch or party was split, it now shows only its own top or bottom items once, so the items listed can differ and the grand total can **fall**. This is intended.


---

# 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/branch-customer-wise-top-bottom-items-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.
