> 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/barcode-and-quantity-separator.md).
# Barcode and Quantity Separator
**YouTube:** [How to Configure the Item code and Quantity Separator in Barcodes in the Issue Register?](https://www.youtube.com/watch?v=5LJwc4Lhr14)
## How to Configure the Item code and Quantity Separator in Barcodes in the Issue Register?
In this tutorial, we will learn how to configure the **Barcode and Quantity Separator** feature in the Issue Register module of Logic ERP. This feature enables the system to capture both the item barcode and quantity in a single scan, eliminating the need to enter the quantity manually.
***
### Objective of This Feature
* Capture item barcode and quantity in a single scan.
* Eliminate manual quantity entry.
* Speed up Issue Register transactions.
* Improve scanning accuracy.
* Reduce data entry time and errors.
***
### Review the Default Behavior
Before enabling the feature, let's understand the default behavior.
* Open the **Issue Register** module.
* Initiate a **New Issue Register** entry.
* Scan an Item barcode.
By default:
* The system captures only the **Item Code**.
* The **Quantity** must be entered manually after scanning.
***
### Let's Configure the Barcode and Quantity Separator
* Open the **Configuration** window.
* Navigate to the **Other Settings** section.
* Locate the option labeled as:
> **"Barcode and Quantity Sep"**
* Define the required separator.
* For example, use a **hyphen (-)** as the separator.
* Save the configuration.
***
### Create a New Issue Register Entry
* Initiate a **New Issue Register** entry.
* Scan the barcode in the following format:
**Barcode - Quantity**
* For example: **399993430-10**
After scanning:
* Press **Enter**.
* Select the required Lot, if applicable.
**Result**
The system automatically:
* Identifies the Item from the scanned barcode.
* Reads the quantity entered after the separator.
* Populates the **Quantity** column automatically.
No manual quantity entry is required.
***
### Key Benefits
* Captures barcode and quantity in a single scan.
* Speeds up Issue Register transactions.
* Reduces manual data entry.
* Minimizes quantity entry errors.
* Improves warehouse and inventory efficiency.
***
### Best Practice Tips
* Use a separator that does not conflict with your barcode format.
* Ensure barcode scanners transmit the separator character correctly.
* Train users to scan the barcode in the configured format.
* Test the configuration with sample barcodes before implementing it in daily operations.
***
### Final Outcome
After configuring the **Barcode and Quantity Separator**, Logic ERP allows users to scan both the **Item Barcode** and **Quantity** in a single input. The system automatically captures the quantity during scanning, making Issue Register transactions faster, more accurate, and more efficient.
---
# 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/barcode-and-quantity-separator.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.