> 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/order-reports/pending-sale-orders-size-wise.md). # Pending Sale Orders Size Wise Logic ERP has corrected the stock figures in the **Pending Sale Orders Size Wise**. The report no longer shows an error with extra item groups, and **% ORDERED** is faster. *** ### **Step 1: Open the Report** * Navigate to **Reports/Queries** and select **Order Reports**. * Open the **Pending Sale Orders Size Wise**. *** ### **What's corrected** * The report no longer shows an error when **Extra Item Groups** are used together with **Closing Stock Unit**, **Closing Stock Weight** or **UnReserved Stock**. * With an item group selection where not every **Explode Group Level** is ticked (the report shows groups instead of items), **Closing Stock Unit**, **Closing Stock Weight** and **UnReserved Stock** are no longer overstated. These figures and their totals will fall. This is intended. * **% ORDERED** and **ORDERS FOR THIS ITEM** now follow the **Extra Item Groups** and **Extra Party Group** selections made for the report, when no extra item groups are shown as columns. * **% ORDERED** is faster when **Extra Item Groups** are used. --- # 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/order-reports/pending-sale-orders-size-wise.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.