> 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-3/faq-on-masters-3/what-is-outlet-item-allocation.md).

# What is Outlet-Item allocation?

Outlet-Item allocation refers to specialized methods within the system used to assign KOT printers to specific items at the outlet level, providing more granular control than standard group-based allocation.There are two primary ways to manage this:

**1. Outlet-Item Printer Allocation**

This method allows you to assign specific printers to individual items within a chosen outlet.

* **Navigation: Master3 > Outlet-Item Printer Allocation.**
* **Process:** Click Open, select the relevant outlet, then click Add to choose the printer name for those items.

**2. Outlet-Item System KOT Printer Allocation**

This is a more specific configuration where items are allocated to a KOT printer based on both the outlet and the specific computer system (terminal) used to place the order.

* **Navigation: Master3 > Outlet - Item System Kot Printer Allocation.**
* **Process:** Click New, select the Outlet name and System, then click Add to choose the specific items to be allocated.

**Comparison with Standard Allocation**

While these methods offer item-level precision, the system also supports KOT Printer Allocation by product group (via **Master1 > Kot > Kot printer Allocation**), which is used to assign printers to entire categories of products at once.

**Verification and Monitoring**

To ensure these allocations are functioning correctly, you can use the Outlet Item Audit report. This audit provides a review to:

* Monitor and verify item-wise sales and usage.
* Ensure correct item configuration and pricing.
* Maintain billing accuracy and prevent discrepancies or misuse.


---

# 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-3/faq-on-masters-3/what-is-outlet-item-allocation.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.