> 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/audit-bin-stock-report.md). # Audit Bin Stock Report Logic ERP has corrected the sorting and the bin totals in the **Audit Bin Stock Report**. The report also no longer shows an error for some saved configurations. *** ### **Step 1: Open the Report** * Navigate to **Reports/Queries** and select **Stock Reports**. * Open the **Audit Bin Stock Report**. *** ### **What's corrected** * With **Extra Item Groups** selected and **Item** ticked under **Report Consolidation**, the report is now sorted by those groups when nothing else sorts it, that is when **Bin Name**, **Picker Name** and **Date** are not ticked under **Report Consolidation** and nothing is ticked under **Item Consolidation**. Earlier the rows came out unsorted, so the same group could appear in several places. * With **Bin Total** ticked under **Report Totals** but **Bin Name** not ticked under **Report Consolidation**, the report no longer prints **Bin Wise Totals** rows. The rows are not arranged by bin in this setting, so these totals were incomplete. You will see fewer total rows. This is intended. The **Grand Total** does not change. * The report no longer shows an error for a saved configuration that has no **Item Order** saved. * When the report is created by the **LOGIC Auto Report Mailer**, an error no longer opens a message on screen that waits for someone to close it. --- # 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/audit-bin-stock-report.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.