> 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/item-master.md).

# Item Master

The **Item Master** is a central record used to create and manage all items in the system. It stores important details such as item name, group, sub-group, tax structure, and rate. Once an item is created in the Item Master, it can be used across transactions like purchase, sales, inventory, and billing.

### Steps to Create an Item in Item Master

1. Navigate to the **Point of Sale** module and select **Masters1**.

* Click on **Item Master**
* The Item Master screen will appear.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-ab190953eeed605de8c71a0db2523eb5e3209dcf%2Fp7.png?alt=media" alt=""><figcaption></figcaption></figure>

2\. Click on the **New**![](https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-ba96cd1cb1536a77fa6be572aa4349461c8c4170%2FScreenshot%20From%202026-06-11%2015-45-19.png?alt=media)button to start creating a new item.

3\. In the item creation screen, enter the **Item Name.**

* Ensure the name is clear and unique for easy identification.

4.Use the **Check** button to verify whether the item already exists in the system.

* If the item already exists, do not create a duplicate entry.

5\. After confirming the item does not exist, select the **Item Group.**

* The item group helps classify the item under a major category.
* Use the available drop down list to choose the correct group.

6.After selecting the item group, choose the **Item Sub Group 1.**

* This further classifies the item into a more specific category.

7\. Next, select the appropriate **Tax Structure.**

* This defines the applicable tax rules for the item during transactions.

8\. Enter the **Item Rate** in the given field.

* Ensure the rate is accurate as it will be used in billing and pricing calculations.

9\. After entering all required details, click the **Save** button.![](https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-dfa8bd56e9a715d78b315676b0a167ddd405370b%2FScreenshot%20From%202026-06-11%2015-46-00.png?alt=media)

* The system will create and store the new item in the Item Master.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-cf511f2f427081d46cfb02f59f707a9ec85a4182%2Fp8.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/item-master.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.
