> 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-1/kot/kds-master.md).

# KDS Master

**KDS Master (Kitchen Display System Master)** is used to configure and manage kitchen display screens in the POS system.

* It helps the kitchen staff view all incoming **Kitchen Order Tickets (KOTs)** on a digital display instead of printed tickets.

## Steps to Create / Open KDS Master

Step 1: Navigate through the menu using the following path:

1. **Point of Sale module→ Masters1 → KOT → KOT Table.**
2. The KDS Master screen will appear.

Step 2: On the screen:

1. Click the **New** button.
2. A new entry form will open.

This allows the user to add a new KDS configuration.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-91bece4d2fbd49424ddc31396dab675c686d263e%2Fs37.png?alt=media" alt=""><figcaption></figcaption></figure>

Step 3: Fill in the required fields:

1. Enter a unique identification code for the KDS screen(KDS ID).
2. Enter the name of the KDS display(KDS Name).

* Enable the **Active** option to activate the KDS.
* This ensures the KDS is available for live order display.

Step 4: After entering all details:

1. Review the information carefully.
2. Click the **Save** button.

The system will successfully create and activate the KDS Master entry.


---

# 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-1/kot/kds-master.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.