> 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/guides/feature-guides/acquire-and-convert/guide-quote-to-cash-acceptance.md). # Building a Quote-to-Cash Acceptance Flow ### Overview A sales rep has agreed terms with a customer — now you need them signed and paid before the deal goes cold. A **quote-to-cash acceptance flow** turns a negotiated quote into a single guided link the customer opens to **review the terms, accept (and sign), and pay** — converting the quote into a live subscription in one sitting, with no back-and-forth and no manual order entry. This guide builds that sales-assisted close. It composes the same journey primitives you've seen elsewhere — prefill, a review/consent step, payment, and an order action — aimed at closing a quoted deal. ### The example we'll build **Beacon, an enterprise data company,** sends a prospect a quote for the Business plan at a negotiated annual price. Instead of a PDF and an email thread, the rep sends a **"Review & accept"** link. The customer opens it to the exact quoted plan and price, reads the terms, accepts them, pays, and is provisioned — the deal closes itself. ### Before you begin * The **quoted plan and price** exist in your catalog (or as an offer), so the journey can present the agreed terms rather than a generic catalog. * Your terms / order form content for the customer to review and accept. * *(Optional)* an **e-signature integration** connected, if you require a formal signature rather than a click-through acceptance. PeakCommerce captures the acceptance as a journey step; a connected e-signature provider handles a legal signature where you need one. ### 1. Create the acceptance journey 1. Go to **Content → Journeys** and click **+ New Journey**. 2. Choose the **Type** — **E-Commerce** if the link is sent to a prospect who isn't a user yet, or **Customer Self-Service** if they must sign in first. Name it (for example *Quote — Business Annual*). 3. Build a short, high-trust flow: **Review quote → Accept & sign → Pay → Confirmation** ### 2. Prefill the quote from the link The rep's link should open straight to the agreed terms — never make the customer re-select what sales already negotiated: * Use a **plan-based URL prefill** so the link sets the quoted plan (by id), the currency, and the starting step. The customer lands on the **Review quote** step with the Business plan and the negotiated price already in place. * For a non-list (negotiated) price, attach the agreed terms as an **offer** the prefilled link applies, so the journey presents the deal — not rack rate. ### 3. Review and accept the terms The **Review quote** and **Accept & sign** steps are where the customer commits: * **Review** — show the plan, the negotiated price, the term, and the order terms clearly. Use a **Content** step so it's purely informational. * **Accept & sign** — capture the customer's agreement (a consent / acknowledgement step records that they accepted the specific terms). Where a formal signature is required, hand off to your connected **e-signature integration**; otherwise a click-through acceptance is captured to the journey context for your records. ### 4. Take payment and create the order * The **Pay** step (the **Payment** role) collects payment for the quoted amount. * On completion, a `create_order` action converts the accepted quote into a **real subscription** on the agreed plan and price — and the role's locked internal writes record the order and keep the account current, so PeakCommerce's records match the deal regardless of what the billing system returns. ### 5. Branch for "not yet" and "needs a change" A quote flow should handle the customer who isn't ready to click *pay*: * **Request changes** → branch to a step that routes the customer back to the rep (a contact / "talk to sales" hand-off) instead of forcing acceptance. * **Pay later / deposit** → if you allow it, branch to collect a deposit now and the balance on a schedule, rather than full payment up front. ### 6. Measure the close * Track the acceptance funnel on **Analytics**: quote links opened → accepted → **paid**. A gap between *accepted* and *paid* points at the payment step; a gap before *accepted* points at the terms or the price. ### Get creative * **Expiring quotes.** Add an expiry to the offer the link applies, so a negotiated price doesn't live forever — and the urgency closes deals. * **Multi-product quotes.** Present a bundle (base plan + add-ons + services) on the review step so the whole deal is accepted and paid in one flow. * **Co-branded close.** Put the acceptance flow on a branded host (a subdomain mapping) so the link is on your domain — more trust at the moment of signing. * **Renewal quotes.** Reuse the same flow at renewal: send a re-contracting quote the customer accepts and pays to extend. ### Tips * **Prefill the negotiated terms.** The whole point is that sales already did the deciding — the link should open to the exact plan, price, and term. * **Be honest about signatures.** A click-through acceptance is captured natively; a legally binding signature uses a connected e-signature integration. Use the one your deal actually requires. * **Always offer an off-ramp.** Let a customer route back to the rep instead of trapping them at "pay now." ### FAQ **Does PeakCommerce do e-signatures?** The journey natively **captures acceptance** of specific terms (a consent / acknowledgement step recorded to the order). For a formal, legally binding signature, connect an **e-signature integration** and hand off at the accept step. Choose based on what the deal requires. **How does the customer get the negotiated price, not list price?** Apply the agreed terms as an **offer** that the prefilled link carries, so the journey presents the negotiated deal rather than the catalog rate. **What does the customer end up with?** A real subscription. On payment, a `create_order` action converts the accepted quote into a live subscription on the agreed plan and price. --- # 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/guides/feature-guides/acquire-and-convert/guide-quote-to-cash-acceptance.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.