> 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-in-action-a-feature-overview/distribution/billing/no-discount-on-special-category-of-products.md).

# No Discount on special category of products

YouTube: [No Discount on Special Category of products in Pharma Retail](https://youtu.be/51rxssaU3h0?si=5FrkZ48NMqIHYzWf)

### 🚫💊 No Discount on Special Pharma Categories in **Logic ERP**

In this tutorial, we’ll learn how to **restrict discounts** (like 💸 **Cash Discount (CD)**, 🧾 **Trade Discount (TD)**, and 🎯 **Special CD**) for a specific **group of products** — especially useful in **Pharma Retail**, like Schedule H1 items.

***

### 🔧 **Steps to Disallow Discounts for a Group of Items**

#### 1️⃣ **Navigate to Item Settings**

* Go to the **Main Menu** 📂
* Open **Set Other Item Details**
* Click on **"Enter Item Other Details"** 📝.

***

#### 2️⃣ **Select Items with Specific Groups**

* Set the **Item Name** format to: `"Item Name + Shade + Size"`
* Press the **Tab** key ↹
* Now go to **Set Column Attributes** and enable the following ✅:
  * ❌ **DO NOT ALLOW CD(%) FOR SALE/SALE RETURN**
  * ❌ **DO NOT ALLOW TD(%) FOR SALE/SALE RETURN**
  * ❌ **DO NOT ALLOW SPCD(%) FOR SALE/SALE RETURN**

🔍 These columns will now be **visible** in the window.

***

#### 3️⃣ **Choose the Item Group**

* Click on **Select Items** 🛒 to choose a specific item group.
* **For example,** if you want to disallow discounts for **Schedule H1 items**💊, select this group.

***

#### 4️⃣ **Restrict Discounts**

* Click on **Do Not Allow CD** ❌
* Press the **Spacebar** ⌨️
* Select **"Yes"** ✅ to restrict **Cash Discount (CD)** for the chosen group.&#x20;
* Repeat the same steps to restrict:
  * **TD (Trade Discount)** 📉
  * **SP/CD (Special Cash Discount)** 💼

***

#### 5️⃣ **Apply to the Entire Row**

* Press **F2** 🖱️.
* From the dropdown, select **"Yes"** to apply it to **all items** in the group
* Now, CD ❌ is disabled for **all Schedule H1 items**
* Similarly, follow the same process for **TD** and **SP/CD** to disable them for all **Schedule H1** items.
* Click **💾 Save** to finalize the changes.

***

### 🧾 **Verifying the Changes in Sale Bill**

* Navigate to the **Sale bill** module🧾to observe it's impact.
* Add an item from the **Schedule H1** **Group** to a sale bill.
* Initially, the system picks up the default CD 💸for this item.
* But on clicking **Save Bill** ✅\
  ➡️ The **discount gets removed automatically** ❌

✅ **Success!** This confirms that the **restriction has been applied** successfully.

***

🛡️ By following these steps, you ensure compliance and maintain proper control over discount policies in **Pharma Retail** with Logic ERP.


---

# 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-in-action-a-feature-overview/distribution/billing/no-discount-on-special-category-of-products.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.
