> 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/item-report/company-group-wise-item-count-analysis.md).

# Company / Group Wise Item Count Analysis

Logic ERP has improved the **Company / Group Wise Item Count Analysis**. The report is now much faster, **TOTAL ITEM COUNT** now follows the same filters, branches and selections as the rest of the report, and the report no longer stops with an error on older or incomplete saved configurations.

***

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

* Navigate to **Reports/Queries** and select **Item Reports**.
* Open the **Company / Group Wise Item Count Analysis**.

***

### **Step 2: Faster report**

* The item counts are now worked out once for the whole report instead of separately for every row and every **Rate Range** column.
* The report is much faster, especially on large reports and when several **Rate Range** bands are set.
* The counts themselves are worked out the same way as before, apart from the corrections below.

***

### **What's corrected**

* With **Item Count As** set to **Items which Sale Exist**, **TOTAL ITEM COUNT** and the **Rate Range** columns now follow the **Stock Transfer Filter** and **Report On** options, the same way **SALE QUANTITY** and **SALE VALUE** do. Earlier, for example, items sold only through stock transfers were counted even when **Stock Transfer Filter** was set to **Non-Stock Transfer**.
* With **Item Count As** set to **Items which Sale Exist** or **Items Which Stock Exist**, the item count now covers only the branches the report covers: the branches chosen in the branch selection, the current branch when **Show Data For Current Branch Only** is ticked, and the branches the user is allowed to see.
* In every **Item Count As** choice, the item count now follows the item, company and extra item group selections made for the report, and the user's item access rights.
* **TOTAL ITEM COUNT** and the **Rate Range** columns will **fall** on reports that use these filters or selections. This is intended.
* **GROUP NAME** is now left blank when **Extra Item Groups** are selected. Such a row can be made up of items from several groups, and earlier it showed the name of only one of them.
* The report no longer shows an error when a saved configuration has no choice in some of its options, or when no **Rate Range** is set.
* The report no longer shows an error when **Rate Range Filter** is set to the last, open-ended band.
* The report no longer shows an error in some set-ups with **Extra Item Groups** selected and **Company** and **Group** not ticked under **Report Consolidation**.


---

# 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/item-report/company-group-wise-item-count-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.
