> 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/party-wise-settings/setup-supplier-+-company-+-group-item-wise-markdowns-for-po.md).

# Setup Supplier + Company + Group/Item Wise Markdowns for PO

**YouTube:** [How to Retrieve Party + Company/Group wise Markdowns defined for PO as TD in Purchase?](https://www.youtube.com/watch?v=uiJdZcbWXxA)

## How to Retrieve Party + Company/Group wise Markdowns defined for PO as TD in Purchase?

In this tutorial, we will learn how to set up **Supplier + Company + Group/Item-wise Markdowns for Purchase Orders**. This setup automatically applies predefined markdowns while fetching purchase orders during purchase entry, ensuring accurate pricing, consistency, and faster purchase processing.

***

### **Open Supplier Markdown Setup**

* Go to the **Main Menu**.
* Expand the **Setup** menu.
* Navigate to **Party Wise Settings**.
* Click on **Setup Supplier Company Group Item Wise Markdowns for PO**.

<figure><img src="/files/SjBotC5da9Dad8TJ9DZp" alt=""><figcaption></figcaption></figure>

***

### **Define Markdowns Using Batch Mode**

Batch mode is used when you want to apply markdowns to **multiple suppliers or items at once**.

* We will start by working in **Batch Mode.**
* **Select the supplier using the “Select Parties” option.**&#x20;

<figure><img src="/files/nm1kJq9XbnEZeYvZxQld" alt=""><figcaption></figcaption></figure>

* Choose the **Entry Type**&#x20;

  > **In the Entry Type field, choose either Item or Company + Group.**

<figure><img src="/files/ZWUTv9wZ65Wa74Q7qKM5" alt=""><figcaption></figcaption></figure>

**Since Company + Group is selected as the Entry Type:**

* First, **select the Group** from the given options.

<figure><img src="/files/cq9wf2q6QKPca60TdBcc" alt=""><figcaption></figcaption></figure>

* Then, **select the Company** accordingly.

<figure><img src="/files/n1miNZRD1iSMZlXsnsqf" alt=""><figcaption></figcaption></figure>

* Enter the **Markdown Percentage**.

<figure><img src="/files/Hcp11Ji7Dp5MwWwg9Tbv" alt=""><figcaption></figcaption></figure>

* Save the configuration.

***

### V**erify Defined Markdowns (Entry Mode)**

* Switch to **Entry Mode**.
* Select the relevant **Supplier / Company / Group / Item**.
* Click **Refresh**.
* The system will display the **defined markdowns**, confirming the setup.

<figure><img src="/files/xJuY2mValJC5Deqkq1bF" alt=""><figcaption></figcaption></figure>

The defined markdown percentage will now be **automatically applied** for the selected supplier, category, or brand during Purchase Order creation.

[<mark style="color:green;">**CLICK HERE**</mark>](/logic-erp-learning-hub-tutorials-and-best-practices/setups/configurations/purchase-voucher-configurations/other-settings-1/pick-party+company+group-wise-markdown-po-as-td.md) to proceed with the implementation of this process.

***

### **Conclusion**

This feature allows you to **centrally control Purchase Order markdowns** for suppliers and item groups, ensuring consistent pricing and reducing manual effort during PO creation.


---

# 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/party-wise-settings/setup-supplier-+-company-+-group-item-wise-markdowns-for-po.md?ask=<question>&goal=<endgoal>
```

`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.
