> 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/kot-table.md).
# KOT Table
A **KOT Table** refers to the table setup used in the **Kitchen Order Ticket (KOT)** process in restaurant management systems.\
It helps users define and manage dining tables within an outlet so that orders can be assigned correctly during billing and kitchen operations.
## Steps to Create a KOT Table
Step 1: Navigate through the menu using the following path:
1. **Point of Sale module→ Masters1 → KOT → KOT Table**
2. Once the screen opens, click the **New** button.
Step 2: After clicking **New**, the system will display the outlet selection screen.
1. Select the required **Outlet** from the list.
2. Click **OK** or proceed to the next screen.
This ensures that the table is created under the correct outlet or branch.
Step 3: After selecting the outlet, enter the following details:
1. Enter the **Table Name or Table Number**.
2. Enter the No. of Covers (seating capacity of the table).
3. Enter the sequence number for table arrangement and display order.
This helps the system arrange tables in proper order.
Step 4: Choose the required **Shape (TPOS)** for the table layout.
* The shape represents how the table will appear in the Touch POS (TPOS) screen.
Step 5: After entering all details:
1. Verify the information entered.
2. Click the **Save** button.
* The system will successfully create the new KOT Table.
---
# 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/kot-table.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.
