> 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-2/faq-on-masters-2/how-to-configure-the-happy-hours-discount.md).

# How to configure the happy hours discount ?

To configure the Happy Hours Discount, you can either set it up for specific items within an outlet or use a predefined discount slab. Both configurations are managed within the Master2 section of the system.Option

**1: Standard Happy Hours Configuration**

This method allows you to apply a specific discount percentage to individual items for a selected outlet:

1. Navigate to **Master2 > Happy Hours Discount.**
2. Click the Open button.
3. Select the desired Outlet from the list.
4. Click the Search icon in the Item field to find and select the specific item.
5. Enter the Discount Percentage to be applied.
6. Click the Save button to finalize the configuration.

**Option 2: Happy Hours Discount Slab**

If you are using discount slabs to manage your happy hour promotions:

1. Navigate to **Master2 > Happy Hours Discount.**
2. Click the New button.
3. Select the appropriate Discount Slab from the options provided.
4. Click Save to apply the slab settings


---

# 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-2/faq-on-masters-2/how-to-configure-the-happy-hours-discount.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.