> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/revenue/quotes/set-terms-and-conditions-on-a-quote.md).

# Set terms and conditions on a quote

Every quote needs terms and conditions before it can be saved. Pick a set from the Terms and Conditions dropdown, which sits below the Sales Tax Rate on the quote. If your business has only one set, it's selected for you automatically on a new quote.

Terms and conditions are set up for your business ahead of time and aren't created from the quote screen, so if the dropdown is empty, your business has none yet and no quote can be saved until one is added.

> **Where to find it:** On the open quote, the Terms and Conditions dropdown (below the Sales Tax Rate)

## Related guides

* [Add a line item to a quote](/revenue/quotes/add-a-line-item-to-a-quote.md)
* [Apply a discount to a quote](/revenue/quotes/apply-a-discount-to-a-quote.md)
* [Attach a file to a quote](/revenue/quotes/attach-a-file-to-a-quote.md)
* [Create a quote](/revenue/quotes/create-a-quote.md)
* [Format descriptions and terms with rich text](/revenue/quotes/format-descriptions-and-terms-with-rich-text.md)
* [Custom pricing on quote line items](/revenue/quotes/custom-pricing-on-quote-line-items.md)


---

# 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://learn.withessential.com/revenue/quotes/set-terms-and-conditions-on-a-quote.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.