> 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/purchase/purchase-module/masters/approved-supplier-item.md).
# Approved Supplier Item
The **Approved Supplier Item** feature is used to map or assign approved products to a supplier. This helps ensure that purchases are made only from authorised suppliers for specific items.
## Steps to Create an Approved Supplier Item
Step 1: Navigate to the **Purchase** main menu from the dashboard.
1. In the **Purchase** menu, click on **Masters**.
2. Select **Approved Supplier Item** from the sub-menu.
* The Approved Supplier Item screen will open.
Step 2: Click on the **Open** button.
Step 3: Click on the **Supplier Search** icon.
1. Select the required supplier from the list.
* The selected supplier details will be displayed on the screen.
Step 4: Click on the **Add** button.
1. Click on the **Product Search** icon.
2. Select the required product from the list.
* The selected product will now be linked to the supplier.
Step 5: Verify that the correct supplier and product are selected.
1. Click on the **Save** button.
* The Approved Supplier Item will be saved successfully.
---
# 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/purchase/purchase-module/masters/approved-supplier-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.
