> 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/purchase-transactions/quote-score.md).
# Quote Score
A **Quote Score** is an evaluation or rating assigned to vendor quotations based on predefined criteria such as price, quality, delivery time, service, and vendor performance. This process helps organizations compare multiple vendor quotations and select the most suitable supplier.
## Steps to Create a Quote Score
Step 1: Go to the **Purchase** main menu.
1. Click **Transaction**.
2. Select **Quote Score**.
* The Quote Score screen will appear.
Step 2: Click the **Open** button.
* The system will display the list of available quotations.
Step 3: Choose the required **Quote Selection** from the displayed list.
* The selected quotation details will appear on the screen.
Step 4: Click the **Score** button.
1. Enter or confirm the score for the selected quotation.
Step 5: After verifying the score details, click the **Save** button.
* The quotation score will be saved successfully in the system.
---
# 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/purchase-transactions/quote-score.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.
