A rep gets a 22% discount approved in a Slack thread on Tuesday. During signature, legal agrees to move the start date and drop one product. The contract is signed on Friday. On Monday, someone in finance books the order from the quote in the CRM, with the original products and the original start date. The first invoice goes out wrong, and the customer disputes it.
Every step had an owner. Sales got the discount approved, legal negotiated the terms, and finance booked the order. The order was wrong because each step worked from a different version of the deal.
Quote to order covers the first two stages of order-to-cash: the quote and its approvals, then the contract and signature. It ends when the order booked in the ERP matches what the customer signed.
What is the quote to order process?
Quote to order is the path from a configured, priced quote to a booked sales order. It includes approving discounts and non-standard terms, generating the contract, collecting signatures, and creating the order in the ERP. Quote to cash is the longer path, which continues through invoicing and payment. Quote to order stops at the booked order.
Where it breaks
- The approval lives in a message. The discount was approved in Slack or email. Nothing on the quote records who approved it, at what level, or against which policy, so nobody downstream can check the order against it.
- The signed version differs from the quote. Terms change during signature, a product comes off, or a start date moves. The CRM still holds the quote as it was before signature.
- Booking waits for someone to notice the signature. The signing tool records it, but the order is created when someone checks. A deal signed on Friday books on Monday, or in a batch at quarter end.
- The order is booked from the quote. Whoever books the order works from the record they can see, and that record is the quote.
- Amendments are booked as new deals. A mid-term upgrade goes through as a fresh quote and a second contract, so the customer ends up with two subscriptions and a renewal date nobody can calculate.
- The CPQ product doesn’t exist in the ERP. A new bundle was added to the price book but never set up as an item in the ERP, so the order fails to book and sits in an error queue.
What it costs
The visible cost is the disputed invoice. A customer who signed one thing and was billed for another pays late, or pays only the part they agree with, and finance spends a week finding out why.
The less visible cost is the audit trail. When an auditor or the board asks why a deal was booked at a 22% discount, the answer is in a Slack thread, if anyone can find it. Discounts that can’t be traced to an approval tend to grow, because nobody can show which ones broke policy.
Quarter end makes both worse. Deals signed in the last days of the quarter are booked in a rush, by hand, from whatever record is open.
What to fix first
- Write the approval onto the quote. Record the approver, the discount, the policy and the time as fields on the record, where the order can be checked against them.
- Send the approved version for signature. Generate the contract from the approved quote, so the document sent is the one that was approved.
- Book on the signature event. Trigger the order from the signing tool’s webhook, instead of a person checking status or a nightly job.
- Compare the order to the signed contract before booking. Check products, quantities, prices and dates line by line. If anything differs, stop and send it to a person. The integration never decides which version is right.
- Carry the quote ID through. Put it on the order and the invoice, so every booked figure traces back to its approval.
- Book amendments as amendments. Link a mid-term change to the original contract and co-terminate it, instead of creating a second deal.
- Map every CPQ product to an ERP item. Block approval of any quote that includes an unmapped product.
The guides to building a quote-to-order integration and a CPQ to ERP sync have the prompts for each step.
Where quote to order fits
Quote to order feeds order booking, the third stage, where the order reaches the ERP. Everything after it inherits the order. Provisioning grants access from it, billing invoices from it, and revenue recognition starts from the contract behind it.
For all eight stages, and the five handoffs where most of the trouble sits, see the order-to-cash process.