> 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/prompt-for-lot-no.-for-every-item-in-case-of-po-retrieval.md).

# Prompt for Lot No. for every item in case of PO Retrieval

**YouTube:** [How to Enable Lot/ Batch Number Prompt for Each Item During Purchase Order Retrieval ?](https://www.youtube.com/watch?v=vmccp8bAD50)

## How to Enable Lot/ Batch Number Prompt for Each Item During Purchase Order Retrieval?

This setting ensures that users are prompted to enter a **lot number for each item** during purchase order (PO) retrieval, improving batch traceability and inventory accuracy.

***

### **Step-by-Step Configuration**

* Open the **Logic Folder** and run **Logic Admin**.
* Go to **Global Settings**.
* Navigate to the **Purchase** tab.
* Locate and enable the option: **“Prompt for lot number for every item in case of PO retrieval.”**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FeL7HaXP8xO8DBHEB6toM%2FAdmin%20Setup%20-%20Prompt%20for%20Lot%20No.%20for%20every%20item%20in%20case%20of%20PO%20Retrieval.png?alt=media&amp;token=2c357fd6-a58b-4081-906e-10b0c6b60366" alt=""><figcaption><p>Let's Keep this feature enable to observe its Impact in Billing.</p></figcaption></figure>

* Click Save to apply the setting.
* **Restart the Software** to activate the changes.

> **Note:** This setting is also available within **Purchase Voucher Configuration**, where it must be enabled **individually for each voucher series**.\
> Using **Global Settings** ensures that the rule is enforced **across all series and branches**.

***

### **Functionality During Purchase Entry**

* Begin a new **Purchase Entry** by retrieving a **Purchase Order**.
* Select the desired **purchase order** from the list.
* Choose the items you wish to retrieve.
* The system will automatically display a **Lot Number window** for **each item**.
* You must specify:
  * The **Lot Number**
  * The **Quantity** to be retrieved

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F3oAvGCahw9JJ4IANUPy4%2FLOT%20Number%20Window.png?alt=media&amp;token=8e6d31f7-4f6f-4e32-8124-f6db2d3c658c" alt=""><figcaption><p>The system automatically displays a 'Lot Number' window for each item.</p></figcaption></figure>

***

### B**enefits**

* Improves **lot-level tracking** and **inventory management**.
* Ensures that **every item** has a **defined lot number** during purchase.
* Minimizes manual follow-ups and errors in stock identification.


---

# 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/prompt-for-lot-no.-for-every-item-in-case-of-po-retrieval.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.
