> 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/order-processing/sale-order/so-configuration/scan-all-types-of-bar-codes.md).

# Scan All Types Of Bar Codes

**YouTube:** [How to Enable Scanning of All Barcode Types in Sales Orders?](https://www.youtube.com/watch?v=_xlOBgAemV4)

## How to Enable Scanning of All Barcode Types in Sales Orders ?

This tutorial explains how to use the **“Scan All Types of Barcodes”** feature in the Sales Order module in Logic ERP. This functionality allows users to scan different barcode types such as **Item Code, Set Code, and Set Name**, making item entry faster and more efficient.

***

### **Objective of This Feature**

* Enable barcode-based item entry
* Support multiple barcode types (Item, Set, Name)
* Speed up Sales Order processing
* Reduce manual entry errors

***

### **Open Sales Order Configuration**

* Navigate to **Sales Order Module**
* Click on **Configuration**
* Select the relevant **Sales Order Configuration**
* Locate the feature labeled as:

> **Scan All Types Of Bar Codes**

<figure><img src="/files/bRVs9iCg9ztEUl58a0fD" alt=""><figcaption></figcaption></figure>

**Available Parameters**

* **Item Code**
* **Set Code**
* **Set Name Barcode**

**Action**

* Enable the required parameters (or all)
* Arrange field priority using **arrow keys**

**Note**

* Field order defines the **search priority** during barcode scanning

***

### **Scan Using Item Code**

* Click on **New Order**
* This ensures updated configuration is applied

**Process**

* Scan barcode in **Item Code Field**

<div><figure><img src="/files/pJecYeuoHVZr5nqZmawu" alt=""><figcaption></figcaption></figure> <figure><img src="/files/jdIwSQz9MdufapDX5lu0" alt=""><figcaption></figcaption></figure></div>

**System Behavior**

* Item is **instantly identified and added** to Sales Order

***

### **Scan Using Set Code**

**Process**

* Scan barcode based on **Set Code**

<div><figure><img src="/files/9uCsY79qubj0LZlGMZVi" alt=""><figcaption></figcaption></figure> <figure><img src="/files/Njp4XxyFFKwjzkVgAOqn" alt=""><figcaption></figcaption></figure></div>

**System Behavior**

* All items linked to that Set are **automatically added**

***

### **Enter/Scan Set Name**

**Process**

* Enter or scan **Set Name Barcode**

<div><figure><img src="/files/p2ee1WxmgtIXZw4LudGR" alt=""><figcaption></figcaption></figure> <figure><img src="/files/0KNFhbqDoJHlGQScnbJw" alt=""><figcaption></figcaption></figure></div>

**System Behavior**

* System identifies the **Set Name**

***

### **Key Benefits**

* Faster billing with barcode scanning
* Supports multiple barcode formats
* Reduces manual effort and errors
* Improves efficiency in bulk item entry

***

### **Best Practice Tips**

* Set correct field priority for better results
* Ensure barcodes are properly configured in system
* Use high-quality barcode scanners for accuracy
* Test all barcode types before live usage

***

### **Final Outcome**

* Items can be added using multiple barcode types
* Sales Order entry becomes faster and smoother
* Reduced dependency on manual item search
* Improved accuracy and productivity


---

# 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/order-processing/sale-order/so-configuration/scan-all-types-of-bar-codes.md?ask=<question>&goal=<endgoal>
```

`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.
