> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/store-manager/prime-web/print-automations.md). # Print automations {% embed url="" %} ## How to Configure Print Automation for KOT and Invoice In this guide, we will walk through the steps to configure print automation for Kitchen Order Tickets (KOT) and Invoices. ### Step-by-Step Guide 1. **Access Live Orders and Session Setting:** Begin by navigating to the Live Orders and Session Setting section of your system. 2. **Navigate to the Printers Tab:** Once in the settings, locate and click on the Printers tab. 3. **Scroll to Receive Printers:** Scroll down until you find the Receive Printers section. 4. **Open Settings:** Click on the Settings icon to access further configurations. 5. **Automated Workflow Configuration:** Go to the Automated Workflow tab. Here, you can assign automation for various states of an order such as Acknowledgement, Food Ready, and Dispatch. Choose the desired state for automation. 6. **Save Changes:** After selecting the appropriate automation settings, ensure to save the changes. Once these steps are completed, all printers will automatically print on the Acknowledgement for KOT and Bill. Thank you for following this guide! --- # 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.urbanpiper.com/store-manager/prime-web/print-automations.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.