> 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/physical-stock-verification-of-puv/physical-stock-verification-of-puv-configuration/lot-code-prefix.md).
# Lot Code Prefix
**YouTube:** [How to Configure the Lot Code Prefix in Physical Stock Verification (PUV)?](https://www.youtube.com/watch?v=YkMGW_9hvG0)
## How to Configure the Lot Code Prefix in Physical Stock Verification (PUV)?
In this tutorial, we will learn how to configure the **Lot Code Prefix** feature in the **Physical Stock Verification (Purchase Voucher)** module of Logic ERP. This feature enables the system to identify and validate scanned Lot Codes using a predefined prefix, ensuring accurate barcode scanning during physical stock verification.
***
### Objective of This Feature
* Identify Lot Codes using a predefined prefix.
* Improve barcode scanning accuracy.
* Prevent invalid barcode entries.
* Ensure accurate physical stock verification.
* Support standardized barcode formats.
***
### Access to the Physical Stock Verification Configuration
* Navigate to the **Physical Stock Verification (Purchase Voucher)** module.
* Open the **Configuration** window.
* Locate the option labeled as:
> **"Lot Code Prefix"**
This field allows you to define a prefix that identifies the Lot Code within the scanned barcode.
***
### Review the Default Behavior
Before configuring a Lot Code Prefix, let's observe the default behavior.
* Ensure the **Field List** is set to **Lot Code**.
* Select the required **Voucher Type**.
* Choose **Purchase Voucher** for Physical Stock Verification.
* Scan the Item using its Lot Code.
**Result**
Since no Lot Code Prefix has been configured, the system directly recognizes the scanned Lot Code and automatically updates the **Physical Quantity**.
***
### Configure the Lot Code Prefix
* Return to the **Configuration** window.
* Enter the required **Lot Code Prefix**.
* Save the configuration.
**Scan Without the Configured Prefix**
* Scan the Lot Code **without** the configured prefix.
**Result**
* The system rejects the scanned barcode and displays an error message indicating that the scanned Item Code is invalid.
***
### Scan with the Configured Prefix
* Scan the Lot Code **along with the configured Lot Code Prefix**.
**Result**
The system successfully identifies the Lot Code using the configured prefix and automatically updates the **Physical Quantity**.
***
### Key Benefits
* Improves barcode scanning accuracy.
* Supports customized barcode formats.
* Prevents incorrect barcode recognition.
* Ensures reliable physical stock verification.
* Reduces manual entry errors during stock counting.
***
### Best Practice Tips
* Configure the Lot Code Prefix to match your organization's barcode format.
* Ensure barcode scanners capture the complete code, including the prefix.
* Set the **Field List** to **Lot Code** before scanning.
* Test barcode scanning after changing the configuration to verify correct recognition.
***
### Final Outcome
After configuring the **Lot Code Prefix**, Logic ERP validates scanned Lot Codes using the defined prefix during Physical Stock Verification. Only barcodes containing the configured prefix are accepted, ensuring accurate Lot identification and reliable physical stock updates.
---
# 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/physical-stock-verification-of-puv/physical-stock-verification-of-puv-configuration/lot-code-prefix.md?ask=&goal=
```
`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.