> 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/faq-on-masters/how-do-i-set-up-a-kot-printer.md).

# How do I set up a KOT printer?

To set up a KOT (Kitchen Order Ticket) printer, you must first create the printer in the system and then allocate it to specific product groups. The KOT printer is essential for forwarding order details such as table numbers, items, and quantities to the kitchen and billing divisions.

**Step 1:** Create the KOT Printer

1. Navigate to **Master1 > kot > Kot printer.**
2. Click the New button.
3. Enter the Printer location (e.g., Kitchen, Bar).
4. Input the printer share name.
5. Optional Backup: You can set a second print option to automatically redirect the KOT to another printer if the primary one experiences a problem.
6. Click Save to finalize the creation.

**Step 2:** Allocate the KOT Printer

Once the printer is created, you must assign it to the relevant product groups so the system knows which items should be printed at that location.

1. Go to **Master1 > Kot > Kot printer Allocation.**
2. Click the Open button.
3. Click on printer location to view the list of KOT printers you have created.
4. Select the appropriate product group for the chosen printer location.
5. Click Save to update the allocation.

Other Printer Allocation OptionsDepending on your operational needs, the system also provides more granular allocation tools in the Master3 menu:

* **Outlet-Item Printer Allocation:** Used to assign printers based on specific items within an outlet.
* **Outlet-Item System Kot Printer Allocation:** Allows you to allocate items to a KOT printer based on both the outlet and the specific computer system being used


---

# 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/faq-on-masters/how-do-i-set-up-a-kot-printer.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.