> 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/open-item.md).
# Open Item
An **Open Item** is a master setup used to define items that are not fixed under a single predefined item structure. It allows the user to create items based on an **Outlet**, along with their **Group** and **Tax Structure**, so they can be used in transactions such as billing and sales.
### Steps to Create an Open Item
1.Navigate to the **Point of Sale** module and select **Masters1**.
* Click on **Open Item.**
* The Open Item screen will appear.
2\. Click on the **New** button to start creating a new Open Item.
3\. Choose the **Outlet Name** from the available list.
* This ensures the item is mapped to the correct outlet/location.
4\. Select the appropriate **Group** for the item.
* Select the applicable **Tax Structure.**
* These settings define how the item will be categorized and taxed during transaction.
5\. After entering all required details, click on the **Save** button.
* The system will successfully create and store the Open Item.
---
# 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/open-item.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.
