> 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/m.r.p.-should-always-be-greater-than-other-rates-in-purchase-voucher.md).

# M.R.P. should always be greater than other rates in Purchase Voucher

**YouTube:** [How to Ensure MRP is Always Higher Than Other Rates in Purchase Voucher?](https://www.youtube.com/watch?v=i3UOKL_r9Cc)

## How to Ensure MRP is Always Higher Than Other Rates in Purchase Voucher?

This tutorial explains how to enable the setting that ensures the **MRP (Maximum Retail Price)** is always greater than any other rate in a **Purchase Voucher** in Logic ERP.

***

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

* Open **Logic Admin**.
* Navigate to **Global Settings**.
* Go to the **Purchase Options** tab.
* Locate and enable the option labeled: **"MRP should always be greater than other rates in purchase voucher"**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2Fcq8qdNnpwrsZJqL5WbUW%2FAdmin%20Setup%20-%20MRP%20should%20always%20be%20greater%20than%20other%20rates%20in%20purchase%20voucher.png?alt=media&amp;token=d4a5e818-b3ec-4ee0-9bc0-e1c4f222ed4d" alt=""><figcaption><p><strong>Let’s keep this feature enabled to observe its impact on purchase transactions.</strong></p></figcaption></figure>

* Click **Save** to apply the changes.
* **Restart** the software to activate the new setting.

***

### **Validation the option in a Purchase Entry:**

* Open the **Purchase Voucher** screen.
* Begin a transaction by selecting an item.
* Attempt to enter a **Sale Rate** that is **greater than the MRP**.
* The software will display an **error message**:\
  *"Sale Rate cannot be greater than MRP."*

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FM9d64Zpkbh6ewXKxUGVX%2FPrompt.png?alt=media&amp;token=a45546fb-2779-4d19-b1c7-53c5d4e8c509" alt=""><figcaption><p>As you can see, the software has prompted an alert message.</p></figcaption></figure>

***

### **Note:**

This setting is crucial for maintaining **pricing accuracy** and ensuring **regulatory compliance**, especially in sectors where MRP enforcement is mandatory.


---

# 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/m.r.p.-should-always-be-greater-than-other-rates-in-purchase-voucher.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.
