> 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/december-2018/billing/new-update-in-sale-return-for-managing-item-quantity.md).

# New Update In Sale Return For Managing Item Quantity

**YouTube:** [New Update In Sale Return For Managing Item Quantity](https://youtu.be/91VVRYDOci8)

### Updation in Customer + Item Wise Sale History Form

In the Sale Return Window, a new update implemented for “**Customer + Item Wise Sale History**.” There are two columns to keep the items quantity level in check:

**1.** Adjust Quantity

**2.** Balance Quantity

One key feature in this update is that you can’t increase the item quantity than it’s actual quantity. Whenever you will insert the quantity more than its total quantity, a prompt window will appear warning you about the exceeding quantity. It will prevent you from inserting the wrong input.

For Example, the Sale quantity for NGST-89 in the given image is 30 and Return is 20. Here:

**->** 20 is your Adjust Quantity

**->** 10 is your Balanced Quantity

You can’t increase the actual quantity of the item more than 30.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F36lkYN75jjv4CcGxX1rg%2Fimage.png?alt=media&amp;token=be29882f-2052-460a-95c3-0a0316dc7986" alt=""><figcaption></figcaption></figure>


---

# 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/december-2018/billing/new-update-in-sale-return-for-managing-item-quantity.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.
