> 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/user-access/logic-global-admin/others/other-settings/filter-items-on-basis-of-branch+item-allocation.md).
# Filter Items on basis of Branch+Item Allocation
YouTube: [How to Filter Items Based on Branch + Item Allocation?](https://www.youtube.com/watch?v=kNl9QBNKOCw)
## How to Filter Items Based on Branch + Item Allocation?
This tutorial explains how to enable and use the feature that **filters available items in sales and purchase transactions based on branch-wise item allocation**.
***
### Enable the Feature in Logic Admin
* Open **Logic Admin**.
* Navigate to **Global Settings.**
* Under the **Others** section click on **Other Setting**.
* Locate and enable the option labeled as:
> **"Filter Items on basis of Branch+Item Allocation"**
* Click on **save** and **restart the software** to apply the changes.
***
### Allocate Items to Branches
* Open the **Setup Module** from the main menu.
* Navigate to: **Set Other Item Details → Allocate Items to Branches**
* In the **allocation window**:
* Select the **branch** from the list.
* Select and link the **items** you want to make available for that branch.
* Save the allocation.
**Note:** You can repeat this process for multiple branches to create customized item lists.
***
### Implement the Feature
**Example 1 – Head Office Branch**
* Log in to the **Head Office branch**.
* Open a **Purchase Bill** or **Sale Bill**.
* In the item search list, you will see **only the items allocated** to the Head Office branch.
**Example 2 – Another Branch**
* Log in to the **other branch**.
* Open a **Sale Bill** or **Purchase Bill**.
* In the item search list, only the items allocated to **this specific branch** will be visible.
***
### Benefits
* Prevents selection of unallocated items in transactions.
* Reduces data entry errors.
* Simplifies the search process by showing only branch-relevant items.
* Ensures better control over branch-wise inventory availability.
---
# 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/user-access/logic-global-admin/others/other-settings/filter-items-on-basis-of-branch+item-allocation.md?ask=&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.
