> 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/outlet-item-printer-allocation.md).
# Outlet - Item Printer Allocation
The **Outlet – Item Printer Allocation** feature is used to assign printers to specific outlets for printing item orders. It ensures that order tickets are printed on the correct printer based on the selected outlet configuration.
### Steps to Create and View Outlet – Item Printer Allocation
Step 1: Navigate to the **Point of Sale** module.
1. Go to **Master3 > Outlet-Item Printer Allocation**.
* The Outlet–Item Printer Allocation screen will appear.
Step 2: Click on the **Open** button to proceed.
Step 3: Click on the **Outlet** field and select the required outlet from the list.
* Click on the **Add** button to create a new printer allocation entry.
Step 4: Select the required **Printer Name** from the available list.
* Ensure the correct printer is selected for the chosen outlet.
Step 5: Save the Allocation
* After selecting the outlet and printer, click on the **Save** button to successfully complete the Outlet–Item Printer Allocation setup.
---
# 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/outlet-item-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.
