> 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/purchase/do-not-allow-change-in-lot-number-purchase-if-default-lot-number-is-specified.md).

# Do Not Allow Change in Lot Number (Purchase) if Default Lot Number is specified

**YouTube:** [How to Restrict Lot/ Batch Number Editing When a Default Lot is Specified in Purchase?](https://www.youtube.com/watch?v=_6It1oexJp0)

## How to Restrict Lot/ Batch Number Editing When a Default Lot is Specified in Purchase?

This tutorial explains how to prevent users from changing the **lot number** in a purchase voucher when a **default lot number** has been configured.

***

### **Set Default Lot Number in Purchase Voucher Configuration**

* Open **Purchase Voucher Configuration**.
* Navigate to **Other Settings 2**.
* Locate the option Labeled: **"Default Lot No** **"**
* Specify the **default lot number** to be used during Purchase Entry.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FDG5mHOvLTKuxS3Oh2DWS%2FAdmin%20Setup%20-%20Do%20Not%20Allow%20Change%20in%20Lot%20Number%20in%20Purchase%20if%20default%20lot%20number%20is%20specified.png?alt=media&amp;token=fc46dd4e-39f8-4bde-849c-ba5f320118df" alt=""><figcaption><p>As shown in the picture, define the <strong>Default LOT Number</strong>.</p></figcaption></figure>

***

### **Access Logic Admin Settings:**

* Open the **Logic Folder** and run **Logic Admin**.
* Go to **Global Settings**.
* Navigate to the **Purchase** tab.
* Locate and enable the option: **"Do Not Allow Change in Lot Number in Purchase if default lot number is specified"**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FaibH4kav0LKIoBxePKbg%2FDefault%20LOT%20Number%20-%20Admin%20Setup.png?alt=media&amp;token=bd3c809c-676c-49c7-8029-1fe4d063de2b" alt=""><figcaption><p>Let's keep this feature enable to observe its impact in Purchase.</p></figcaption></figure>

* Click **Save** to confirm the configuration.
* **Restart the software** to activate the changes.

***

### **Verify Functionality During Purchase Entry**

* Open the **Purchase Voucher** module.
* While making a purchase entry:
  * The **default lot number** will be **automatically selected**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FsdkxfOdWlaY5xNormmkA%2FLOT%20No%20in%20purchase.png?alt=media&amp;token=1eae2ae1-e611-4ac8-b504-28746e94e826" alt=""><figcaption><p>As you can see in the image above, the <strong>default LOT Number</strong> has been picked automatically, and you cannot make any changes to it.</p></figcaption></figure>

* The system will **restrict any attempt to modify** the selected lot number.

***

### **Conclusion**

By enabling this setting, you can enforce data consistency and avoid unintended modifications to lot numbers during purchase entries.


---

# 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/purchase/do-not-allow-change-in-lot-number-purchase-if-default-lot-number-is-specified.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.
