> 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/item-instruction.md).
# Item Instruction
The **Item Instruction** feature is used to define specific instructions for individual items in the system. These instructions help guide preparation, serving, or handling requirements for each item, ensuring consistency in operations.
### Steps to Create and View Item Instruction
Step 1: Navigate to the **Point of Sale** module.
1. Go to **Master3 > Item Instruction**.
* The Item Instruction screen will appear.
Step 2: Click on the **Add** button to create a new instruction entry.
Step 3: Select the required details from the available options:
* **Product Group**
* **Sub Group**
* **Item**
After selecting these details, click on the **Search** button.
* The system will display the matching items based on the selected filters.
Step 4: Click on the **Add** button for the required item.
* Enter the **Item Instruction** in the provided field.
* Select the appropriate **Level** for the instruction (based on system configuration or requirement).
Step 5: Save the Item Instruction
* After entering all required details, save the configuration to successfully assign the instruction to the selected 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-3/item-instruction.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.
