> 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/why-cant-i-save-a-quote.md). # Why can't I save a quote? If the Save button stays disabled, the quote is missing something it requires. A standard quote saves only once it has a customer and property, at least one line item, a selection in the Terms and Conditions dropdown, a total that is not negative, a quote validity between 1 and 3650 days, no pending sales-tax lookup or unresolved tax request, and at least one unsaved change. Quotes that use a document template configured without items or pricing do not need a line item or total. They still need customer and property, Terms & Conditions, required custom fields, and an unsaved change. The most common cause is terms and conditions: if your business hasn't set any up, that dropdown is empty and no quote can be saved until one is added. > **Where to find it:** On the open quote, check the Save button and the Terms and Conditions dropdown ## Related guides * [Why can't I edit a quote?](/revenue/quotes/why-cant-i-edit-a-quote.md) * [Why can't I send a quote?](/revenue/quotes/why-cant-i-send-a-quote.md) * [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) --- # 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/why-cant-i-save-a-quote.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.