> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/point-of-sale/point-of-sale-module/masters-3/discount-type.md).
# Discount Type
The **Discount Type** feature is used to define different types of discounts in the system. It helps categorize discounts based on their purpose, usage, and applicable conditions such as specific days or promotional rules.
### Steps to Create and View Discount Type
Step 1: Navigate to the **Point of Sale** module.
1. Go to **Master3 > Outlet - Discount Type**.
* The Discount Type screen will appear.
Step 2: Click on the **New** button to create a new discount type.
Step 3: Enter Discount Details.
Enter the required information in the available fields:
* **Discount Type** – Enter the name of the discount type.
* **Narration** – Provide a short description or explanation of the discount type.
* **Applicable Days** – Select the days on which the discount will be applicable.
Ensure all details are entered correctly before proceeding.
Step 4: Save the Discount Type.
* After entering all required details, click on the **Save** button to successfully create and store the Discount Type.
---
# 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://help.rbsgo.com/point-of-sale/point-of-sale-module/masters-3/discount-type.md?ask=&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.
