> 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-learning-hub-tutorials-and-best-practices/inventory/issue-register/issue-register-configuration/lot-code-prefix.md).

# Lot Code Prefix

**YouTube:** [How to Configure the Lot Code Prefix in the Issue Register?](https://www.youtube.com/watch?v=xV7PNFrnfnI)

## How to Configure the Lot Code Prefix in the Issue Register?

In this tutorial, we will learn how to define a **Lot Code Prefix** for scanning items in the **Issue Register** module. This feature enables the system to recognize and identify items by scanning a Lot Code with a predefined prefix, making item entry faster and more accurate.

***

### Objective of This Feature

* Enable Lot Code Prefix-based item scanning.
* Improve the accuracy of barcode or Lot Code scanning.
* Speed up item entry in the Issue Register.
* Reduce manual item selection.
* Ensure seamless identification of items through Lot Codes.

***

### Access to the Issue Register Configuration

* Go to the **Issue Register** module.
* Open the **Configuration** window.
* Navigate to the **Other Settings** section.
* Locate the option labeled as:

> **"Lot Code Prefix"**

<figure><img src="/files/VZExzvukYb2xY1CFkv9I" alt=""><figcaption></figcaption></figure>

* By default, this option is set to **Nil**.
* Select the required **Lot Code Prefix** from the dropdown list.

<figure><img src="/files/OMdzHCRVqaFQLqYLWeIT" alt=""><figcaption></figcaption></figure>

***

### Configure Related Settings

Since both options work together, configure the following settings as well:

* Set **Item Code As Field** to **Lot Code**.

<figure><img src="/files/6aDW4Alho3bFs9LBoIvT" alt=""><figcaption></figcaption></figure>

* Enable the option: **"Do Not Show Item Code List While Entering the Item Code"**

<figure><img src="/files/QPvhVbsFBcGPMFTjxO42" alt=""><figcaption></figcaption></figure>

* These settings ensure that the system recognizes scanned Lot Codes correctly.
* Save the configuration changes.

***

### Scan the Item in **Issue Register**

* Initiate a **New Issue Register** entry.
* Scan the **Lot Code** along with the configured prefix.

<figure><img src="/files/alPK5L0PYCi8I1uxtnDf" alt=""><figcaption></figcaption></figure>

**Result**

The system automatically recognizes the scanned Lot Code, identifies the corresponding item, and populates the item details without requiring manual selection.

***

### Key Benefits

* Faster item scanning during Issue Register entry.
* Improves barcode and Lot Code recognition.
* Reduces manual item selection.
* Minimizes data entry errors.
* Enhances operational efficiency during inventory transactions.

***

### Best Practice Tips

* Always configure the **Item Code As Field** option as **Lot Code** when using a Lot Code Prefix.
* Enable **Do Not Show Item Code List While Entering the Item Code** for smooth scanning.
* Ensure that the scanned Lot Code includes the configured prefix.
* Verify that Lot Codes and prefixes are correctly defined in the system before use.

***

### Final Outcome

After configuring the **Lot Code Prefix** and the required related settings, Logic ERP automatically identifies items by scanning the **Lot Code with the defined prefix** during Issue Register entry. This streamlines the scanning process, improves accuracy, and reduces manual effort while recording inventory issues.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/inventory/issue-register/issue-register-configuration/lot-code-prefix.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.