> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/sales-portal/quotes-overview.md). # Quotes A **quote** is a saved, priced proposal you build for a customer — the products and services they want, the term, the discount, and the amounts — that you can edit over time, send for the customer's approval, and later turn into an order of record. Because a quote is a durable document rather than an in-flight wizard, it can sit with a customer for days, come back for changes, and pick up internal approvals along the way without losing its history. ## Where quotes live * **The admin console** carries the primary surface: **Commerce → Quotes** in the sidebar. Administrators see every quote in the workspace. * **The Sales portal** has the same quote screens wired in, with two honest caveats. First, the stock **Sales Default** profile does not grant the **Quotes** resource — a sales rep can use quotes only after an administrator enables **Quotes** on their profile's **Resource Permissions** (see [Profiles & Permissions](/product/using-peakcommerce/profiles-and-permissions.md)). This is a setup step, not a bug: it lets each organization decide whether reps quote directly. Second, the Sales portal's navigation doesn't yet include a Quotes tab — reps reach the quote screens from links (for example, a link an admin adds to a tailored Sales page, or the portal's quotes address, `/sales/quotes`). Record access follows the usual scope rules: unless your profile grants full record access (as an administrator's does), the list shows **the quotes you own**. A quote belonging to another rep isn't just hidden from the list — opening it directly behaves as if it doesn't exist, so reps can't probe each other's pipelines. ## The Quotes list The list shows each quote in a single table: * **Quote** — the quote number (for example `Q-00042`) and the name you gave it. * **Status** — where the quote is in its life (see below). * **Total** — the quote's total value, in its currency. * **Term** — the contract term. One honest rough edge: the column currently renders the stored value as-is (for example `12_months`) rather than a formatted label. The list follows the console convention: rows don't click through. Use the **actions menu** (the `⋯` at the end of each row) to **Open**, **Edit**, or **Delete** a quote (delete asks for confirmation). To start a new quote, use the **New quote** button at the top of the list. ## Statuses A quote's status tells you, at a glance, where it stands: * **Draft** — being built; not yet sent to anyone. * **Pending approval** — held for internal sign-off because its discount exceeds the rep's authority ceiling (see [Creating & editing a quote](/product/sales-portal/creating-and-editing-quotes.md)). * **Sent** — shared with the customer for their approval. * **Accepted** — the customer has approved it. * **Declined** — the customer declined it. The decline is recorded on the quote; no one is notified automatically today, so watch the list. * **Processing** — the quote is mid-commit into an order. * **Completed** — the quote has been processed; it carries a reference to the order it produced. * **Failed** — the commit into an order errored. This is a real, visible status: the quote keeps the upstream error message, and the commit can be retried once the underlying issue is resolved — a failure is never silently swallowed. * **Expired / Cancelled** — no longer live. ## Related * [Creating & Editing a Quote](/product/sales-portal/creating-and-editing-quotes.md) * [Sending a Quote for Customer Approval](/product/sales-portal/sending-quotes-for-customer-approval.md) * [Sales Portal Overview](/product/sales-portal/sales-portal-overview.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.peakcommerce.com/product/sales-portal/quotes-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.