> 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/allow-entry-of-mrp-in-purchase-order.md).

# Allow Entry of MRP in Purchase Order

**YouTube:** [How to Enable Entry of MRP in Purchase Orders?](https://youtu.be/4BP2GBmlmy4)

## How to Enable Entry of MRP in Purchase Orders?

This tutorial explains how to enable **MRP (Maximum Retail Price) entry** in the Purchase Order module in Logic ERP. By default, the MRP field is disabled, but with this setting, users can manually enter MRP for each item during purchase transactions.

***

### **Objective of This Feature**

* Allow manual entry of **MRP in Purchase Orders**
* Provide flexibility in pricing control
* Ensure accurate MRP recording during procurement
* Improve data completeness for inventory

***

### **Understand Default Behavior**

**Initial Observation**

* Open **Purchase Order Module**
* Go to **Item Details Section**

**System Behavior**

* **MRP Column is disabled** by default
* Users cannot enter MRP manually

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FRPQMU8G5gTekcDoXafJp%2FMRP%20-%20Desabaled.png?alt=media&amp;token=a2d1901b-e52b-4a1f-81d1-108d09edd591" alt=""><figcaption></figcaption></figure>

***

### **Enable Entry of MRP in Purchase Order**

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

> **“Allow entry of MRP in Purchase Order”**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2Fel98332LmIbrmbZGDcId%2FCNF.png?alt=media&amp;token=8e0098b2-106f-4c4b-a47d-ad302c0cca0e" alt=""><figcaption></figcaption></figure>

* Click **OK** to apply changes.

***

### **Verify Option in Purchase Order**

* Start a **New Purchase Order Entry**
* Select the **Supplier**

**System Behavior**

* Go to **Item Details Section**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FDPBmKayGc5l9ddzcdLFm%2FMRP%20-%20Enabled.png?alt=media&amp;token=befa1e83-ffef-433a-9a45-4b5631fdf285" alt=""><figcaption></figcaption></figure>

**Result**

* **MRP Field is now active**
* Users can manually enter MRP for each item

***

### **Key Benefits**

* Flexibility to define MRP during purchase
* Improved pricing accuracy
* Better inventory and pricing records
* Supports dynamic pricing scenarios

***

### **Best Practice Tips**

* Ensure correct MRP entry to avoid pricing issues
* Cross-check MRP with supplier data
* Use this feature only when MRP is not predefined

***

### **Final Outcome**

* MRP field becomes editable in Purchase Orders
* Users can enter accurate MRP values
* Better control over pricing data
* Improved efficiency in procurement process


---

# 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/allow-entry-of-mrp-in-purchase-order.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.
