> 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-vs-actual-stock-doc-wise-entry/physical-vs-actual-stock-doc-wise-entry-configuration/enable-item-code-prompt-lot-if-barcode-as-lot-code.md).

# Enable Item Code (Prompt Lot) if Barcode as Lot Code

**YouTube:** [How to Enable Lot Selection Popup After Item Code Scanning in Physical vs. Actual Stock Entry?](https://youtu.be/bDRRQtmcmq8?si=uyCGc2UmQ6MfTL2f)

## How to Enable Lot Selection Popup After Item Code Scanning in Physical vs. Actual Stock Entry?

In this tutorial, we’ll learn how to use the **“Enable Item Code (Prompt Lot) if Barcode as Lot Code”** feature in the **Physical Versus Actual Stock – Document Wise Entry** module. This feature allows users to scan an item code and select the required lot from a prompt window, making it easier to update the physical stock of a specific lot.

***

### Access to the Configuration

* Navigate to the **Physical Versus Actual Stock – Document Wise Entry** module.
* Open the configuration settings. (The **Configuration** button is available only to the Admin user or a supervisor user.)
* Locate the option labeled as:

> **“Enable Item Code (Prompt Lot) if Barcode as Lot Code”**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FFltVjcPLjzepsEz5QDPf%2FCNF%20-%20Default.png?alt=media&#x26;token=3ad16a6e-d247-4581-bd92-f75c9eebbcb4" alt=""><figcaption></figcaption></figure>

* This feature allows users to scan an item code and select the required lot when the **Barcode As** field is set to **Lot Code**.

**Let’s first check how the system behaves when this feature is disabled.**

***

### Verify the Functionality When the Feature Is Disabled

* Proceed with the verification process.
* Confirm that the **Barcode As** field is set to **Lot Code**.
* Scan the product using its **Lot Code**.
  * The system successfully scans the lot and updates the physical stock.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FDvDSeeF8sBwyMOZ37D6D%2FScan%20Lot%20Code.png?alt=media&#x26;token=389ccf4d-4bce-4887-a5fe-fdaa5f4f78d1" alt=""><figcaption></figcaption></figure>

* Next, scan the product using its **Item Code**.
  * The system rejects the scan with the message **"Invalid BarCode"**, because the feature is disabled and scanning is restricted to the lot code.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F69aGAIfTbGyBSreDxHdp%2FError%20Prompt.png?alt=media&#x26;token=a7beeafa-9824-453b-aac5-59a305f8faa9" alt=""><figcaption></figcaption></figure>

**This confirms that item code scanning is not allowed when the feature is disabled.**

***

### Enable the Configuration

* Return to the configuration settings.
* Enable **“Enable Item Code (Prompt Lot) if Barcode as Lot Code.”**
* Save or apply the configuration, if required.
* Proceed to verify the scanning behavior with the feature enabled.
* While this feature is enabled, the **Barcode As** field is set to **Lot Code** automatically and cannot be changed.

**The feature is now enabled. Let’s check how it affects the scanning process.**

***

### Verify the Functionality When the Feature Is Enabled

* First, try scanning the product using its **Lot Code**.
  * The system rejects the scan because, with this feature enabled, the expected scanning method is to use the item code and select the lot from the prompt window.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F6aETYVJs0R9ZKUyeGGIY%2Fn.png?alt=media&#x26;token=7a54796a-8aa6-4009-8812-f29946a19f8d" alt=""><figcaption></figcaption></figure>

* Next, scan the product using its **Item Code**.
  * If the item has lots at **different MRPs**, the system opens the **Select Lot** window.
  * If the item has only one lot, or all its lots have the same MRP, the lot is picked automatically and no window opens.
* Select the required lot from the list.
* The list shows only lots that have stock in the current branch and the selected godown, and that are not expired or damaged.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FJZmsAE76yEoUnHHrb3wW%2FLot%20Code%20Prompt.png?alt=media&#x26;token=a072010e-a446-4348-bb9a-e525c6366e56" alt=""><figcaption></figcaption></figure>

* After selecting the lot, the system updates the physical stock in the **Physical Stock** column for the selected lot.

**This confirms that scanning an item code prompts lot selection and updates the physical stock of the chosen lot.**

***

### Conclusion / Result

* **Feature Disabled:** The system accepts the lot code for scanning but rejects the item code.
* **Feature Enabled:** The lot code is no longer accepted. When an item code is scanned, the system prompts the user to select a lot (if the item has lots at different MRPs), and the physical stock of the selected lot is updated.
* **Key Benefit:** This feature enables users to select the required lot directly during item code scanning, ensuring that physical stock is updated against the correct lot.

**By enabling this feature, users can scan an item code, select the appropriate lot, and update its physical stock efficiently.**


---

# 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-learning-hub-tutorials-and-best-practices/inventory/physical-vs-actual-stock-doc-wise-entry/physical-vs-actual-stock-doc-wise-entry-configuration/enable-item-code-prompt-lot-if-barcode-as-lot-code.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.
