> 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-printer-allocation.md).
# KOT Printer Allocation
**KOT Printer Allocation** is a feature used to assign specific **KOT Printers to product groups** in a restaurant management system.
This means that when an order is placed, the system automatically sends the Kitchen Order Ticket (KOT) to the correct printer based on the type of product ordered.
## Steps for KOT Printer Allocation
Step 1: Navigate through the menu using the following path:
1. **Point of Sale module→ Masters1 → KOT → KOT Table**
2. The KOT Printer Allocation screen will open.
Step 2: On the screen:
1. Click the **Open** button.
2. The system will display the allocation setup interface.
Step 3:After opening the screen:
* Click on the **Printer Location** field.
* A list of all **created KOT printers** will be displayed.
Select the required printer from the list.
Step 4: After selecting the printer location:
1. Choose the **Product Group** that should be linked to that printer.
2. Product groups are typically categorized based on menu items.
This ensures correct routing of KOTs based on item type.
Step 5: Once all mappings are completed:
1. Review the selected printer and product groups.
2. Click the **Save** button.
The system will update and store the printer allocation settings successfully.
---
# 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-printer-allocation.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.
