> 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/setups/configurations/purchase-voucher-configurations/other-settings-1/input-for-m.r.p-on-basis-of-per-unit..md). # Input for M.R.P on basis of Per Unit. YouTube: [How to Configure the entry of MRP on a per Unit basis in Purchase ?](https://www.youtube.com/watch?v=wEFsQOGr-S0) ## How to Configure the entry of MRP on a per Unit basis in Purchase? In this Tutorial, we'll learn how to allows users to input MRP on a per-unit basis. Particularly beneficial for industries like **pharmaceuticals**, where products are packaged in strips, bottles, etc., but require per-unit MRP calculation. ### **Enabling the Feature** * Navigate to the "**Purchase Voucher Configuration"**. * Locate the option and enable **"Input MRP on the basis of per unit"**.

Let's keep this feature enable to observe it's impact.

### **Creating a Purchase Voucher** * Create a new "Purchase Voucher". * Select an item with a **conversion factor** defined in the master data. * Example: A **strip** contains **10 tablets**. * Purchasing **10 strips** results in a total quantity of **100 tablets**. * **Basic rate** is applied per strip, but MRP can now be entered **per tablet**.

Enter the details as demonstrated in the Picture.

### **Transaction & Billing Process** * When billing, the system automatically calculates MRP and rates based on the selected quantity. * **Example 1**: If a customer buys **1 strip**, the system displays the rate per strip and MRP per tablet. * **Example 2**: If a customer buys **5 tablets**, the system divides the rate accordingly.

Here, you can see that the software has automatically calculated the rate as ₹72.50 for 5 tablets.

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/setups/configurations/purchase-voucher-configurations/other-settings-1/input-for-m.r.p-on-basis-of-per-unit..md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.