> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/user-guides/management-dashboard/quotes.md).

# Quotes

Quotes module provides functionality to offer prices to the customers.

Use the **Quotes** module of the Emporix Management Dashboard to manage a list of quotes requested by your customers. You can use the module to create new quotes, accept or reject the ones that already exist.

The **Quotes** module is made of two sections

* [Quotes](https://github.com/emporix/emporix-documentation-portal/tree/master/content/user-guides/management-dashboard/quotes/README.md) - where you can manage all the details of the existing quotes and create new ones
* [Status Codes](/user-guides/management-dashboard/quotes/status-change-reasons.md) - where you can manage status types for the quotes

{% hint style="info" %}

* To check quotes management possibilities, see [Quotes guide](/user-guides/core-commerce/quote-management.md) in the Core Commerce section.
* To check the API documentation, see [Quote Management Service guide](/api-documentation/api-guides/quotes/quote/quote.md) and the [Quote Service](/api-documentation/api-guides/quotes/quote.md) in the Emporix API Reference.
  {% endhint %}


---

# 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://developer.emporix.io/user-guides/management-dashboard/quotes.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.