> 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/change-lot-rates-for-all-branches-when-rate-changed-in-module-overwrite-lot-rates.md).

# Change Lot Rates for all branches when rate changed in module Overwrite Lot Rates

**YouTube:** [How to Configure Global Setting to Apply Lot Rate Changes to All Branches via Overwrite Lot Rates?](https://www.youtube.com/watch?v=ERPJxaDkL-g)

## How to Configure Global Setting to Apply Lot Rate Changes to All Branches via Overwrite Lot Rates?

In this tutorial, we will discuss a **global option in Logic ERP** that allows you to **synchronize lot rates across all branches** whenever a change is made in one branch.

***

### Enable Global Setting

* Open **Logic Admin**.
* Navigate to **Global Settings** 
* Under the **Other** click to **Others** **Settings.** 
* Locate and enable the option labeled as:

> **“Change Lot Rates for all branches when rate changed in module Overwrite Lot Rates”**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FrHCUlTgkTlW6NI0vdW3l%2FGlobal%20Settings.png?alt=media&amp;token=ab26fa90-a1c6-4942-820f-e1afe0650131" alt=""><figcaption></figcaption></figure>

* Save the changes and **restart the software** for the setting to take effect.

***

### Update Lot Rates

* Navigate to **Inventory Menu** and Locate the option **"Overwrite Lot No.'s/Rates"**.
* Select the **required items and lot number**.
* Refresh the data.
* Edit and update the new rates.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FRdy988mx89bnwrV1gWiu%2FLot%20Rate%201700.png?alt=media&amp;token=019eaf2e-d121-4f25-b88b-d6490d586bc7" alt=""><figcaption></figcaption></figure>

* Save the changes.

***

### Verify in Other Branches

* Log in to another branch (e.g., **Madhukar branch**).
* Open the **Sale Bill window** and initiate a new transaction.
* You will notice that the **updated sale rate (e.g., 1700)** defined in the Head Office branch has also been applied in the Madhukar branch.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FduT7Y6eq8bBOczyJL2ft%2FMadhukar%20Branch%20(1).png?alt=media&amp;token=3e10191b-952c-4b11-8a2e-cf424902e274" alt=""><figcaption></figcaption></figure>

* This ensures that **all common lot numbers across branches** are updated automatically.

***

### Additional Configuration

* When updating rates from **any branch**, open the **Overwrite Lot Rate window**.
* Under **Configuration**, ensure that the system is set to **“Take rates from other branch”** for proper synchronization.

***

### Key Benefits

* Ensures **rate consistency** across all branches.
* Reduces manual effort by avoiding repetitive updates.
* Prevents **price mismatches** between Head Office and branch locations.


---

# 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/change-lot-rates-for-all-branches-when-rate-changed-in-module-overwrite-lot-rates.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.