> 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/november-2019/billing/auto-pick-lot-number-if-single-lot-or-have-same-mrp.md).

# Auto Pick LOT Number if Single LOT or have Same MRP

A new option added in Sale Voucher Configuration **Lot Selection** setttings i.e., “**Auto Pick if Single Lot(or Same MRP)**.” This option will prevent the ‘LOT search for Item’ window from opening in the Sale Bill if there’s only single LOT allocated to the item or the item has multiple LOTs allocated with same MRP.

For example: Suppose there’s an item who have more than one LOT numbers. In normal case, the LOT search window will always pop-up. But if you set Lot Selection to ‘**Auto Pick if Single Lot(or Same MRP) ‘**, then the LOT search window will not open if the MRP is same for every LOT number of the item.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FIzbJuw4KdhMuKPC7503g%2Fimage.png?alt=media&amp;token=d00ccc2f-d666-4cf8-bd99-c840b09c53e6" 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/november-2019/billing/auto-pick-lot-number-if-single-lot-or-have-same-mrp.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.
