> 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/sending-quotes-for-customer-approval.md). # Sending a Quote for Customer Approval Once a quote is ready, you can put it in front of the customer as a secure link they open to review and **approve or decline without signing in** — no account, no password. This page covers sending the link, what the customer sees, and what happens on approval. For building the quote, see [Creating & Editing a Quote](/product/sales-portal/creating-and-editing-quotes.md). ## Send the link Open the quote and click **Send to customer**. The quote moves to **Sent** and a secure approval link appears in the editor with a **Copy** button. Two things to know, honestly: * **No email is sent.** "Send" mints the link and marks the quote sent — *you* share the link with your customer however you work (email, chat, your CRM). * **The link is valid for 14 days.** That's the link's own lifetime — long enough for a real sales cycle. The quote's **Expires** date is the business-level expiry the customer sees on the page; the two are separate. Clicking **Resend link** on a sent quote mints a fresh 14-day link any time. The link is signed and tied to that one quote. It never lets the customer see anything else in your workspace. You can also re-send a quote that was declined or expired — useful after revising the terms. > **Approvals first.** A quote whose discount is over your authority ceiling must be approved internally before it can be sent — the **Approval** panel on the quote explains the hold. A held quote can't go to a customer. > **Gotcha — edits after sending.** There is no quote versioning live today. If you edit the quote after sending, an un-actioned link shows the quote's **current** state, not what it looked like when you sent it. Re-copy the link and tell the customer when terms change. ## What the customer sees The link opens a clean page carrying your organization's name and the quote summary: each line item with its quantity (one-time items marked as such), the subtotal, the discount if there is one, and the total per billing period. There is no app navigation, and the page says plainly that nothing is charged until they approve. The customer can: * **Approve quote** — optionally typing their name to sign, then confirming; or * **Decline** — which records the decline on the quote. **A link is single-use by state, not by trickery:** only a quote in the **Sent** status can be acted on. Once it's been approved or declined — by this link or any earlier one — a second attempt gets a clear "already decided" response rather than a silent failure. The quote records who approved and when. > **Declines are recorded, not broadcast.** Declining marks the quote **Declined** — nothing more. No notification is sent to you or anyone else today, so keep an eye on your **Quotes** list for quotes you're waiting on. ## What happens on approval By default, an approved quote **routes back to you**: it's marked **Accepted** and waits for you to process it into an order when you're ready (**Process quote** in the editor). Automatic processing on approval — where acceptance immediately commits the order — is available on request via the API; there's no in-app setting for it today. Processing — whether you trigger it or it runs automatically — goes through **one guarded commit path** with the same safeguards either way: * **It produces an order of record** in PeakCommerce — a durable record of what was agreed. It does **not** create a subscription, an invoice, or a charge in your billing system; nothing is billed by processing a quote. * **It can't run twice.** A quote already processed refuses a second commit and points at the existing order — a double-click, or you and the customer's auto-process racing, can't create two orders. * **The over-authority gate still applies.** A discount that exceeds the authority ceiling can't slip through at commit time, even on the automatic path. * **Failures are visible.** If the commit errors, the quote moves to **Failed** with the upstream error message stored on it — never a silent drop. On the automatic path the customer's approval is still recorded (their intent is never lost); the commit can be retried once the issue is resolved. Either way, the outcome is always visible on the quote's status in the **Quotes** list. --- # 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/sending-quotes-for-customer-approval.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.