> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/welcome.md). # Welcome Welcome to the comprehensive documentation for Boss It's POS system. Whether you're a new user getting started, an experienced operator looking to maximise efficiency, or an administrator managing system configurations, this documentation hub has been designed to support you every step of the way. This documentation provides everything you need to know about our POS system, including: **Product Information** Detailed guides covering all aspects of the system's functionality, from basic operations to advanced features. Each section is crafted to help you understand not just how to use the system, but how to use it effectively. **Process Documentation** Step-by-step procedures for common tasks, troubleshooting guides, and best practices. These resources ensure you can handle day-to-day operations with confidence. *** As new features are added to the system and common questions arise, we update these guides to ensure they remain current and useful. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bossithq.com/welcome.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 `build a script that syncs our docs to a CMS` 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.