> 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/warehouse-management-features-and-configuration-in-logic-erp/wms-mobile-app/edit-bin-group.md).

# Edit Bin Group

## WMS App – Edit Bin Group

In this tutorial, we will learn how to use the **EDIT BIN GROUP** option of the WMS app to map the physical warehouse: which **bins** sit in which **rack**.

Use it when bins are first placed in a rack, or when a bin is moved to another rack.

***

### Before You Start

* The racks and bins must be created in **Setup\Setup Items\Setup Bins**.
* The rack barcode is the **rack name** as set up in Setup Bins. Print the rack and bin barcodes and fix them on the racks and bins.
* The **EDIT BIN GROUP** option must be allowed for the user in **User Access\Setup Mobile WMS Users**.

***

### Scan the Rack

* Open the WMS app and tap **EDIT BIN GROUP**.
* Scan the barcode of the **rack**, or type it next to **Bin Group :** and tap **Fetch Data**.

The rack is added to the list. If the same rack is scanned again, the app shows *"Bin-Group already scanned..."*.

***

### Scan the Bins of the Rack

* Tap the rack in the list.
* The bins already recorded against this rack are shown.
* Scan the barcode of each **bin** that is physically in the rack.

**System Behavior**

* A bin that is already recorded against the rack is ticked when it is scanned.
* A bin that is not yet recorded against the rack is **added** to it.
* Bins you do not scan stay in the rack.
* To correct a wrong scan, swipe the bin to the right and confirm. This only takes the bin off the list on the phone; it does not remove it from the rack in Logic ERP.

More than one rack can be scanned in the same session.

***

### Upload

* Go back to the rack list.
* Tap **Upload**, then **Yes**.
* The app shows *"Data submitted successfully..."*.

**Result:** The racks and their bins are updated in Logic ERP, so stock placed in these bins is shown against the correct rack.

***

> **Example — Moving a bin to a new rack**
>
> Bin **A-01-05** has been moved from rack **A-01** to rack **A-02**. Rahul opens **EDIT BIN GROUP**, scans the barcode of rack **A-02**, taps it, and scans bin **A-01-05**. The bin is added to rack A-02. He goes back to the rack list and taps **Upload**. From now on, bin A-01-05 belongs to rack A-02.

***

#### Final Outcome

The **EDIT BIN GROUP** option keeps the rack and bin layout in Logic ERP the same as the layout on the warehouse floor, so pick lists and reports show the correct rack for every bin.


---

# 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/warehouse-management-features-and-configuration-in-logic-erp/wms-mobile-app/edit-bin-group.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.
