> 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/banquet/banquet-module/transaction/faq-on-reservation/how-to-create-a-kitchen-order-ticket-kot.md).

# How to create a kitchen order ticket (KOT)?

To create a Kitchen Order Ticket (KOT), follow these steps within the Transaction menu:

1\. Navigate to the Menu: Go to the Transaction menu and click on Kot/charges.

2\. Select the Category: Set the Category to KOT.

3\. Identify the Reservation: Click on Reserve No and select the specific reservation number for which you are generating the ticket.

4\. Choose Items: Click on the R symbol to select the items you wish to include in the order.

5\. Finalize: Click Save to complete the process and raise the KOT.

You can also view any Pending KOT/Charges by navigating to the Queries menu and selecting the Pending Bills option, where you can then click Display to see the current list


---

# 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/banquet/banquet-module/transaction/faq-on-reservation/how-to-create-a-kitchen-order-ticket-kot.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.