> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/procurement/quotes/create-and-manage-quotes.md).

# Manage quotes

This topic describes how to search, renew, or delete a quote.

### Searching for a quote

To search for a quote:

1. Navigate to the **Quotes** page.  
2. Use the filter options on the page to find the required quote, then select  **Search**. You can search using a purchase order or reference number, or date.
3. In the  **Actions** column, select **View** to see detailed information for the quote.

### Renewing a quote

To renew an expired quote:

1. Navigate to the Quotes page, then select the quote to renew.
2. Select **Renew Expired Quote**. 
3. Select **Yes** to confirm that you want to renew the quote. Your renewal request is submitted to SoftwareOne for action.

### Deleting a quote <a href="#deletequote" id="deletequote"></a>

To remove a quote:

1. Navigate to the Quotes page, then select the quote you wish to delete.
2. On the Quote Detail page, select **Delete Quote**.
3. Select **Yes** to confirm that you want to delete the 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://docs.platform.softwareone.com/modules-and-features/procurement/quotes/create-and-manage-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.