How to build a quote-to-order integration

What matters here

• The approved discount must travel on the record. An approval that lives in a Slack thread cannot be audited or enforced.
• Signature is an event, not a status somebody checks. Book on the webhook, not on a nightly scan of a signing tool.
• What gets booked must match what was signed, line for line. If they differ, stop rather than reconciling.
• Treat an amendment as an amendment. A mid-term change filed as a new quote breaks the renewal calculation permanently.
• Carry the quote id all the way through. Without it nobody can trace a booked figure back to the approval that allowed it.

Who this is for

You run revenue operations or deal desk. Quotes are approved in one place, signed in another and booked in a third, and reconciling the three at quarter end is somebody's week.

How it works in practice

Everything that sits between a rep building a quote and revenue being booked.

1. 1

   Approval state is written onto the quote

   Who approved, at what discount, against which policy, and when. Not an email thread.

2. 2

   The signature request carries the approved version

   So the document sent is provably the one that was approved, not a later edit.

3. 3

   Signature fires a webhook and booking begins

   Event-driven, because a nightly scan means a Friday signature books on Monday.

4. 4

   The booking is compared to the signed document

   Line for line. A mismatch stops the process instead of being resolved by whichever system wrote last.

5. 5

   The quote id travels to the order and the invoice

   So a booked figure traces back to the approval that permitted it.

6. 6

   Amendments reference the original

   A mid-term change is an amendment with a link, never a fresh contract that orphans the renewal.

Paste these into Claude Code or Codex with the Tray Headless plugin installed. Each stage runs on its own. The systems named in them are the worked example rather than a requirement, and every prompt says so.

Once per project, run /tray-workflows:set-workspace to pick the workspace these build in. Point it at a sandbox first.

1. 1

   Set up, then map the three systems

   Quote, signature and booking each hold part of the truth.

   Headless skills build-workflow

   Copy

   Use build-workflow. The systems in play are Salesforce CPQ, DocuSign
   and NetSuite, or whatever we run in those seats.
   
   I need SBQQ__Quote__c and SBQQ__QuoteLine__c with whichever fields
   hold approval state, the DocuSign envelope and what its Connect
   webhook actually sends on completion, and NetSuite SalesOrder and the
   contract record on the ERP side.
   
   Show me where a discount is stored in each. They will not agree, and that
   disagreement is the integration.

2. 2

   Make the approval travel with the quote

   An approval in an email thread cannot be enforced or audited.

   Headless skills build-workflow

   Copy

   Use build-workflow. When a quote is approved, write onto the quote record:
   the approver, the approved discount percentage, the policy threshold it
   was tested against, the justification, and the timestamp.
   
   Then lock the approved version. If any line item, quantity or price
   changes after approval, revoke the approval and require it again. A quote
   that can be edited after approval is not an approved quote.
   
   Never let the integration approve anything itself. It records and it
   enforces, it does not decide.

3. 3

   Trigger on signature, and book exactly what was signed

   The comparison that stops a customer being invoiced for something else.

   Copy

   Trigger booking on the DocuSign envelope completed webhook, not on a
   scheduled scan. A Friday signature should book on Friday.
   
   Then compare, line for line, before writing anything to the ERP:
   
     Every product on the signed document appears on the order
     Quantities match exactly
     Prices match the approved discount, to the cent
     Term dates match
     The total matches
   
   Any difference stops the process and raises it to the deal desk. Do not
   reconcile a mismatch automatically. The signed document is the contract,
   and an integration quietly adjusting it is how a customer receives an
   invoice they did not agree to.

   This comparison is the whole control. Without it, an edit made between approval and signature books silently and is found at renewal.

4. 4

   Handle amendments as amendments

   Where most quote-to-order implementations quietly break.

   Headless skills tray-gotchas

   Copy

   Use tray-gotchas, then handle the amendment cases:
   
   Mid-term upgrade. Create an amendment linked to the original contract,
   co-terminated to the same end date, prorated from the effective date.
   Never a fresh contract.
   
   Downgrade. Same linkage, and flag it for revenue recognition rather than
   processing it silently.
   
   Renewal. Reference the expiring contract so the renewal figure derives
   from the chain, including every amendment along the way.
   
   Cancellation within a cooling-off period. Reverse the booking and record
   why, rather than leaving a booked order nobody will invoice.
   
   A mid-term change filed as a new deal produces two contracts for one
   customer, and the renewal number is wrong from that point on.

5. 5

   Carry the ids, and reconcile the chain

   So a booked figure can be traced back to the approval that allowed it.

   Copy

   Stamp the quote id on the envelope, the order and the invoice, and the
   contract id on every amendment.
   
   Then reconcile weekly across the chain:
   
     Signed envelopes with no booked order
     Booked orders with no signed envelope
     Bookings where the discount exceeds what was approved
     Amendments with no parent contract
   
   Report days from approval to signature, signature to booking, and the
   count of mismatches caught. If mismatches are frequent, the problem is
   upstream in quoting rather than here.

6. 6

   Prove it works, then hand it to deal desk

   Because approval thresholds change with the comp plan.

   Copy

   Run the per-step schema checks and the whole-workflow audit before this
   touches production.
   
   Then open the same workflow in Tray Build so the deal desk can adjust
   approval thresholds and the mismatch tolerance in the visual canvas.
   Those move with the comp plan, and they should not need a coding
   assistant.

What it connects to

Three systems hold one commercial agreement between them.

Named systems are the ones most teams run, not the only ones that work. Each is an authentication in your Tray workspace, referenced by name, so the workflow never holds a credential. Where we have a connector page, the name links to it.

Questions people ask

Related guides