> 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/setups/setup-accounts/branch-setup/setup-branch-wise-targets.md).
# Setup Branch Wise Targets
**YouTube:** [How to Set Up and Use Branch-Wise Targets?](https://youtu.be/QSLgUTK4vdo)
## How to Set Up and Use Branch - Wise Targets?
This tutorial explains how to **set up Branch-wise Sales Targets in Logic ERP** and monitor their achievement. It covers defining sales and stock targets for each branch, tracking performance through billing activities, and analyzing results using detailed reports. This feature helps businesses align branch performance with organizational goals.
***
### **Objective of Branch Targets**
* Define **sales goals** for each branch
* Monitor **performance against targets**
* Maintain optimal **stock levels**
* Enable data-driven **business decisions**
***
### **Accessing Branch Target Setup**
* Navigate to **Main Menu → Setup Module**
* Go to **Branch Setup**
* Open **“Setup Branch Wise Targets”**
***
### **Selecting Branch & Period**
* Choose the **Branch** for which targets are to be defined
* Select the **Target Period (Month)**
* Ensures tracking is done for a specific timeframe
***
### **Defining Sales Targets**
* Enter **Target Value**
* Represents total **sales amount goal** for the branch
* Enter **Target Quantity**
* Represents total **units/items to be sold**
***
### **Setting Stock Targets**
* Define **Stock Target Value**
* Ideal inventory value to maintain
* Define **Stock Target Quantity**
* Number of units to keep in stock
**Saving Target Configuration**
* Verify all entered values
* Click **Save**
* Targets will be recorded successfully
***
### **Reviewing Defined Targets**
* View saved targets under **Entry Section**
* Ensure all configurations are correctly defined
***
### **Tracking Target Achievement**
* When billing is performed in the selected branch:
* System automatically tracks:
* **Sales Value Achievement**
* **Quantity Achievement**
***
### **Viewing Target vs Achievement Report**
* Navigate to **Main Menu → Reports/Queries**
* Go to **Customer + Item Sale Analysis**
* Open **“Branch Wise Stock or Sale Target vs Achievement Report”**
**Generating the Report**
* Select:
* **Branch**
* **Date Range**
* Click **Generate/Create**
**Report Insights**
* Displays:
* **Target Quantity vs Achieved Quantity**
* **Target Sales Value vs Achieved Sales**
* **Stock Target vs Current Stock** (Quantity & Value)
***
### **Key Benefits**
* Helps track **branch performance effectively**
* Ensures **target-driven sales strategy**
* Maintains **balanced inventory levels**
* Improves **planning and forecasting accuracy**
***
### **Final Outcome**
* Branches operate with **clear sales and stock goals**
* Performance is continuously monitored
* Management gains **actionable insights**
* Overall business efficiency and growth are enhanced
---
# 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/setups/setup-accounts/branch-setup/setup-branch-wise-targets.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.
