> 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/stock-reports/branch-wise-free-stock-against-reserve-do-allocation.md). # Branch Wise Free Stock Against Reserve/DO Allocation Logic ERP has corrected the **Branch Wise Free Stock Against Reserve/DO Allocation** so that the pending sale order quantity shows on the same row as the item's stock again, instead of on extra rows of its own. *** ### **Step 1: Open the Report** * Navigate to **Reports/Queries** and select **Stock Reports**. * Open the **Branch Wise Free Stock Against Reserve/DO Allocation**. *** ### **What's corrected** * The fix applies when the **SET NAME** or **SET CODE(UD)** column is shown, **Do Not Show Rows with Closing Stock not Exists** is not ticked, and, under **Item Consolidation**, either **Pack / Size** and **Item Name** are both ticked or **Item Code** is ticked. * In this setting the **PENDING SALE ORDER QTY** now appears on the same row as the item's stock. Earlier the report listed all the stock rows first and then a second set of rows carrying only the pending sale order quantity. * The rows again follow the order set in the report's configuration. * The same applies to the **UN-ASSIGNED DO STOCK** column. * You will see fewer rows. This is intended. Each branch now shows one complete total instead of several partial ones, and the grand total does not change. * Opening a row's details by double-clicking it no longer picks up the order from the previous run. --- # 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/stock-reports/branch-wise-free-stock-against-reserve-do-allocation.md?ask=&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.