> 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/item-code-column-as.md).
# Item Code Column as
**YouTube:** [How to Configure Toggle Scanning for Item Code , Lot Code and Lot Number in Issue Register?](https://www.youtube.com/watch?v=tPF-YN0EMu0)
## How to Configure Toggle Scanning for Item Code , Lot Code and Lot Number in Issue Register?
In this tutorial, we will learn how to configure the **Item Code Column As** option in the Issue Register module. This feature allows you to define whether items are scanned using the **Item Code**, **Lot Code**, or **Lot Number**, making the scanning process flexible according to your business requirements.
***
### Objective of This Feature
* Configure the preferred scanning method.
* Support Item Code, Lot Code, and Lot Number scanning.
* Speed up Issue Register entries.
* Improve scanning accuracy.
* Adapt the scanning process to different inventory practices.
***
### Open Issue Register Configuration
* Go to the **Issue Register Module**.
* Open the **Configuration** window.
* Navigate to the **Other Settings** section.
* Locate the option labeled as:
> **"Item Code Column As"**
This option provides three scanning methods:
* **Item Code**
* **Lot Code**
* **Lot Number**
***
### Option 1: Item Code (Default)
**Configuration**
* By default, the option is set to **Item Code**.
**Observe the Functionality**
* Initiate a **New Issue Register** entry.
* Scan or enter the **Item Barcode** or **Item Code**.
**Result**
The system automatically identifies the item and populates the relevant details, allowing you to proceed with the transaction.
***
### Option 2: Lot Code
**Configuration**
* Return to the **Configuration** window.
* Change **Item Code Column As** to **Lot Code**.
* Save the configuration.
**Observe the Functionality**
* Initiate a new Issue Register entry.
* Scan the **Lot Code**.
**Result**
The system identifies the item based on the scanned **Lot Code** and automatically adds it to the transaction.
***
### Option 3: Lot Number
**Configuration**
* Return to the **Configuration** window.
* Change **Item Code Column As** to **Lot Number**.
* Save the configuration.
**Observe the Functionality**
* Initiate a new Issue Register entry.
* Scan the **Lot Number**.
**Result**
The system identifies the item using the scanned **Lot Number** and automatically adds it to the Issue Register entry.
***
### Key Benefits
* Supports multiple scanning methods.
* Reduces manual item selection.
* Improves speed and accuracy of Issue Register entries.
* Provides flexibility for businesses using different inventory identification methods.
* Simplifies warehouse and inventory operations.
***
### Best Practice Tips
* Select the scanning method that matches your barcode or labeling system.
* Ensure Item Codes, Lot Codes, and Lot Numbers are correctly maintained in the Item Master.
* Verify scanner compatibility with the selected identification method.
* Test the configuration after making changes to ensure the correct item is retrieved.
***
### Final Outcome
The **Item Code Column As** feature in the Issue Register module allows Logic ERP to identify items based on **Item Code**, **Lot Code**, or **Lot Number**. By selecting the appropriate option, businesses can streamline the scanning process, improve transaction accuracy, and enhance overall inventory management.
---
# 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/item-code-column-as.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.