> 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/january-2026/billing/lot-code-search-option-added-in-lot-search.md).
# Lot Code Search Option Added in Lot Search
Logic ERP has introduced a new enhancement that allows users to search Items using the Lot Code during the Lot Search process in Sales Billing. This feature simplifies lot identification, improves billing accuracy, and speeds up the sales transaction by enabling precise lot selection based on Lot Code instead of only the Lot Number.
***
### Using Lot Code Search in Sales Bill
* First, open the **Sales Bill** module.
* Select the **Account Name** and **Item Name**.
* Once the **Lot Search window** opens, you will see a **search dropdown**.
* Using this dropdown, you can now search items **by Lot Code**.
* This option makes lot selection faster and more accurate during billing.
**Benefits:**
* Accurate lot-wise billing
* Faster lot selection
* Precise sales reporting
This feature helps ensure accurate stock tracking and reporting in Logic ERP.
---
# 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/january-2026/billing/lot-code-search-option-added-in-lot-search.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.
