> 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/display-message-if-item-has-already-been-ordered.md).

# Display Message if Item has Already been Ordered

**YouTube:** [How to Enable Alerts for Previously Ordered Items in Purchase Orders](https://www.youtube.com/watch?v=kH4OMpe_Pu0)?

## How to Enable Alerts for Previously Ordered Items in Purchase Orders?

This tutorial explains how to **enable an alert message when an item has already been ordered in a previous Purchase Order** in Logic ERP. This feature helps prevent duplicate ordering and improves purchase decision-making.

***

### **Objective of This Feature**

* Alert users if an item has **already been ordered**
* Prevent unnecessary **duplicate purchases**
* Provide **visibility of previous order details**
* Improve purchase planning and control

***

### **Access to Configuration**

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

> **"Display Message if Item has Already been Ordered"**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FhwW7QeEgC4VMwsqKIRYC%2FCNF.png?alt=media&amp;token=6d0466d1-e9e9-470a-a02c-31e611b8c10b" alt=""><figcaption></figcaption></figure>

* Click **OK** to apply changes

***

### **Create Purchase Order**

* Open **Purchase Order Window**
* Select the **Supplier Name**

**Item Entry**

* Scan or enter
  * **Item Code / Item Name**

**System Alert**

* If the item has been ordered earlier:
  * System displays an **alert message**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FePLmwvDyvtqisDmctW2E%2FPrompt.png?alt=media&amp;token=4553a749-62fa-432e-ac04-5de00fcceeee" alt=""><figcaption></figcaption></figure>

**Alert Information Includes**

* Previous **Purchase Order details**
* Helps user review past transactions

***

### **Implement Action Based on Alert**

**Available Options**

* **Click “No”**
  * Stop adding duplicate item
* **Click “Yes”**
  * Proceed with ordering the item again

***

### **Key Benefits**

* Avoids duplicate purchase orders
* Enhances decision-making with past data
* Improves inventory control
* Reduces unnecessary stock buildup

***

### **Best Practice Tips**

* Always review alert details before proceeding
* Use this feature for better stock planning
* Combine with stock reports for accurate decisions

***

### **Final Outcome**

* Users receive alerts for previously ordered items
* Duplicate ordering is **controlled effectively**
* Purchase decisions become **more informed and efficient**
* Inventory remains **optimized and well-managed**


---

# 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/display-message-if-item-has-already-been-ordered.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.
