> 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/order-processing/purchase-order/po-configuration/do-not-allow-entry-without-lot-number.md).

# Do Not Allow Entry without Lot Number

**YouTube:** [How to Restrict Saving Purchase Orders Without a Lot Number?](https://youtu.be/GIULXGjfjZk)

## How to Restrict Saving Purchase Orders Without a Lot Number?

This tutorial explains how to restrict saving a **Purchase Order without a Lot Number** in Logic ERP. This feature ensures that every item entry includes a lot number, helping maintain accurate inventory tracking and batch control.

***

### **Objective of This Feature**

* Enforce **Lot Number entry** in Purchase Orders
* Improve batch-wise inventory tracking
* Prevent incomplete transactions
* Ensure data accuracy and compliance

***

#### **Access to Purchase Order Configuration**

* Go to **Purchase Order Module**
* Open **Configuration Window**
* Navigate to **Other Settings**
* Locate and enable the option labeled as:

> **“Do Not Allow Entry without Lot Number”**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FedkUbsBmJoyuYGrlHZ5k%2FCNF.png?alt=media&amp;token=90aa26c9-0562-46b1-b2eb-1cbf456fd0bf" alt=""><figcaption></figcaption></figure>

* Click **OK** to apply changes.

**Functionality**

* System will not allow saving a Purchase Order without entering a Lot Number

***

### **Create Purchase Order (Without Lot Number)**

* Start a **New Purchase Order Entry**
* Enter **Supplier Name**
* Go to **Item Details Section**
* Do **not** define Lot Number
* Try to proceed/save

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F3c4VajRcMIIJDLNkUHc4%2FLot%20Number%20Prompt.png?alt=media&amp;token=9734cfaa-5560-4c18-9fbe-b685aefdd714" alt=""><figcaption></figcaption></figure>

**System Behavior**

* System **restricts the action**
* Displays error message:
  * *“Please enter the lot number”*

***

### **Create Purchase Order (With Lot Number)**

**Correct Action**

* Define the **Lot Number** for the item

**Result**

* Purchase Order is successfully saved

***

### **Key Benefits**

* Ensures proper batch tracking
* Prevents incomplete data entry
* Improves inventory accuracy
* Enhances compliance and traceability

***

### **Best Practice Tips**

* Always define lot numbers during item entry
* Use standardized lot naming conventions
* Train users on importance of batch tracking

***

### **Final Outcome**

* Purchase Orders cannot be saved without Lot Number
* Accurate batch-wise inventory management
* Reduced errors in stock tracking
* Improved operational efficiency


---

# 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/order-processing/purchase-order/po-configuration/do-not-allow-entry-without-lot-number.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.
