> 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/status-change-reasons.md).

# Status Codes

Quotes status codes bear information about quotes current states.

When a quote is created, the customers can approve it, request a change or decline the quote. Every customer decision about a quote is reflected in the quote's status change.

| Customer Action | Result                                                                                                                                                       | Quote Status Change |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- |
| Accept          | The proposition presented in the quote is approved by a customer.                                                                                            | Accepted            |
| Change          | Email from a customer with change request details. The customer has to choose a change request reason and can also add some free text with more description. | Pending             |
| Decline         | Email from a customer with a decline reason. The customer has to choose a decline reason and can also add some free text with more description.              | Declined            |

If the customers want to request a change in a quote or they decide to decline it, they need to select a reason for their decision. By default, status codes for the following reasons are available in the system:

* **For a change request:**
  * Wrong material
  * Provided price too high
  * Delivery time late
  * Other
* **For declining a quote:**
  * No longer needed
  * Price too high
  * Delivery time late
  * Other

The codes are available in the Management Dashboard, under **Quotes** -> **Status Codes**, you can also create a custom status code if needed.

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

If the quote is declined or there's a request for change, you can see the quote's status change straight away in the quotes dashboard, plus you can check the reason's details in the quote edit mode, in general tab.

<figure><img src="https://3057647601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbTY7EwZtYYQYC6GOcdTj%2Fuploads%2Fgit-blob-71e438fbe0a68440d67cc19c021f7a973d1e605f%2Fstatus_codes2.png?alt=media" alt=""><figcaption></figcaption></figure>

## Creating a custom status code

1. Go to **Quotes** -> **Status Codes** and choose **Create Status Code**.
2. Select the status type, it can be either **Change** or **Decline**.
3. Enter the code you want to use as a reason for a change request or quote decline.
4. **Optional**: Add additional comments about the quote change reason.

After you save the new status code, the customers are able to select it from the drop-down menu as a change reason when they request an update or decide to decline a quote.


---

# 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/status-change-reasons.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.
