> 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/stock-transfer-godown-wise/stock-transfer-godown-wise-configuration/barcode-and-quantity-separator.md).

# Barcode and Quantity Separator

**YouTube:** [How to Set Up Barcode and Quantity Separator in Godown-Wise Stock Transfers?](https://youtu.be/e7NKShC7pkM)

## How to Set Up Barcode and Quantity Separator in Godown- Wise Stock Transfers?

In this tutorial, we will learn **how to configure and use the Barcode and Quantity Separator in godown-wise stock transfer entries in Logic ERP**.

***

### Default Behavior

By default, when an item barcode is scanned during a stock transfer, **only the item code is captured**, and the **quantity must be entered manually** afterward.

***

### Configure Barcode + Quantity Separator

Logic ERP provides an option that allows you to **define the quantity at the time of barcode scanning itself**, so the quantity is picked automatically.

To enable this feature:

* Open the **Configuration** window.
* Go to **Other Settings**.
* Locate the **“Barcode and Quantity Separator”** option.
* Define the required separator.
  * In this example, we are using a **hyphen (-)**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FjmOIdqDb531BkEYQPcgb%2FConfiguartion.png?alt=media&amp;token=972090c3-2653-4263-b81a-00c4e379a20f" alt=""><figcaption></figcaption></figure>

* Save the configuration.

***

### Use Barcode with Quantity During Stock Transfer

* Create a **new godown-wise stock transfer voucher**.
* Select **Godown From** and **Godown To**.
* Scan the barcode followed by the **separator and quantity**
  * Example format:\
    `ITEMCODE-5`

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FQCATkAMaYShSGGG7BaHH%2FItem%20Code.png?alt=media&amp;token=eca42cde-af75-42fe-b64d-9b3911f0843f" alt=""><figcaption></figcaption></figure>

* Press **Enter** and select the lot if applicable.

***

### Result

* The **quantity is automatically picked** based on the scanned value
* Manual quantity entry is no longer required
* Faster and more accurate stock transfer process

***

### Benefit

* Ideal for barcode-based operations
* Reduces manual errors
* Improves data entry speed

***

This is how you can **configure and use the Barcode and Quantity Separator in godown-wise stock transfer entries in Logic ERP**.


---

# 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/stock-transfer-godown-wise/stock-transfer-godown-wise-configuration/barcode-and-quantity-separator.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.
