# QRION showcase: quote to order

> How a QRION workflow turns a closed Salesforce deal into the right store order: lines mapped, margin checked against the account tier’s floor, concessions approved by the right level, credit limits sent to finance, and the order written back to the deal.

Source: https://co-worq.com/examples/quote-to-order

QRION showcase · Order to cash

# Every closed deal priced, approved and ordered the same way.

The handover from sales to operations is where margin quietly leaks: a discount nobody signed off, an account past its credit limit, a product with no match in the store. A quote to order workflow decides before anything is created, not afterwards.

QRION: Quote To Order.A $55,600 closed deal: margin below the floor, a manager’s approval, a finance sign-off on credit, and the order created and written back.

Transcript

This is QRION running one complete business process.

A deal is won. Turning it into the right order at the right price with the right approvals is where most companies lose days.

The quote to order is the handover from sales to operations, and it is where margin quietly leaks.

A discount nobody signed off. An account already passed its credit limit. A product with no match in store. Here, the requirements document is the thing that builds the process.

Not a document people are asked to remember, but the specification the automation is generated from.

This is what the document became. 37 steps wired from the requirements themselves.

Read the closed deal from Salesforce, map every line to the store, work out the margin, and route whatever a person has to decide.

Nothing is created anywhere until the process has an answer it can defend.

Every branch is wired, including the ones nobody wants: not provisioned, unmapped lines, credit declined.

Here is the same process as a list: every step, in the order it runs.

Each one is a business step rather than a technical one. Read the quote, check the account is provisioned, price it, approve it, order it, and record it. Read it top to bottom, and you have the process without opening a single technical screen.

The rules are stated once. Every account sits in a tier, and every tier has a margin floor.

At or above the floor, the order goes through on its own. Below it, the size of the concession decides who has to sign.

Up to two points goes to sales ops. Up to five to a sales ops manager. Beyond that, the VP of sales. The latter is in the process, not in somebody's head.

Published with the Salesforce and store connections carried across.

From here, the process is listening for closed deals.

A real deal in a real Salesforce org. Snow Devil Outfitters, $55,600. The moment it moves to closed one, the process picks it up. Nobody rekeys anything.

10 server racks and a 100 water bottles at prices that were negotiated rather than listed.

The run as it happens. The account is provisioned for ordering, and both lines map to real products in the store.

The margin comes out at 26.5% against a tier floor of 30.

Three and a half points of concession. Too much to pass on its own, so the process stops and asks.

This is the sales ops manager's queue. The order total, the margin, the floor it missed, and the concession are all on the card. Nothing exists in the store yet. The decision is made before anything is created, not explained afterwards.

Approved.

And the process immediately finds the second reason to stop.

$55,600 against a $40,000 credit limit. That is finances call, not sales.

A different person, a different queue, the same run, still holding.

With both signatures in hand, the order is created in the store as a business to business order at the quantities from the quote against the right company account, at the prices that were agreed, placed against the Snow Devil company account, and tagged back to the process that created it.

And back in Salesforce, the deal itself carries the proof, the order it became, and the status it ended in. Written by the process, not typed by a person, which is what makes it worth auditing.

The margin it went out at and the concession that was approved are on the record beside it.

One process. Every closed deal, priced, approved, and ordered the same way.

## What is a quote to order workflow?

It is a governed process that turns a won deal into an order. When an opportunity closes in Salesforce, the workflow checks the account is set up for ordering, maps every line to a product in the store, and works out the margin against the floor for the account's tier. A concession below the floor goes to the approver its size requires, and an order over the credit limit goes to finance. Only then is the order created in the store, and the deal carries the order it became.

Systems

Salesforce, Shopify B2B

Routing

Straight through, discount approval by concession size, or finance

Controls

Margin floor per tier; credit limit; nothing created before approval

Showcase

QRION capabilities on demo data; not a customer result

Why the handover breaks

## The quote and the order live in different systems, so they drift

- ### Orders are retyped

    Someone rekeys the deal into the store. Lines go wrong, negotiated prices do not survive, and the customer disputes the invoice.

- ### Discounts are approved afterwards

    If approval happens at all, it happens in email after the commitment was made, and nobody checks the margin floor.

- ### Credit limits are missed

    Sales closes a deal larger than the account’s credit limit, and finance finds out when the invoice is overdue.


The workflow

## One closed deal, from Salesforce to the store and back

Generated from the requirements document: 37 business steps, every branch wired.

1.  1

    System step

    ### Deal closes

    An opportunity moving to Closed Won starts the run. Nobody rekeys anything.

    Role

    Salesforce

2.  2

    System step

    ### Check and price

    Account provisioned for ordering, every line mapped, margin against the tier’s floor.

    Role

    Margin policy

3.  Approval gate

    ### Approve the concession

    Below the floor, the size of the concession decides who signs: sales ops, manager or VP.

    Role

    Sales operations

4.  Approval gate

    ### Finance on credit

    Over the credit limit is finance’s call, in a different queue, in the same run.

    Role

    Finance

5.  5

    System step

    ### Order and write back

    B2B order at the agreed prices; the deal records the order, margin and approved concession.

    Role

    Shopify · Salesforce


In the demo, a $55,600 deal came out at 26.5% margin against a 30% floor and $15,600 over a $40,000 credit limit, so it stopped twice before any order existed.

What this shows

## Decided before anything is created, not explained afterwards

A showcase of QRION's capabilities, run on demo data. It is not a customer result or a project estimate.

- ### An approval ladder in the process

    Margin floors per tier and approvers by concession size are stated once and applied to every deal.

- ### Two people, one run

    The sales ops manager and finance each decide in their own queue while the run holds, with the facts on the card.

- ### Every branch wired

    Unprovisioned accounts, unmapped lines and declined credit each have a path, so nothing half-created is left behind.

- ### Proof on the deal

    Salesforce shows the order the deal became, its status, the margin and the concession, written by the process.


Questions

## About this example

Is this a customer result or a project estimate?

No. It is a showcase of what QRION can do, run on demo data. It shows the capabilities a governed workflow uses; it is not a customer result, a project estimate or a forecast of return.

Who approves a discount?

The size of the concession decides. In the demo policy, every account tier has a margin floor; at or above it the order goes through on its own. Up to two points below goes to sales operations, up to five to a sales operations manager, and beyond that to the VP of sales. The ladder is in the process, not in somebody’s head.

What happens when something does not fit?

Every branch is wired, including the ones nobody wants: an account not provisioned for ordering, a line with no matching product, credit declined. Nothing is created in the store until the process has an answer it can defend.

Who built the workflow?

The process was generated from the requirements document: 37 steps, each a business step rather than a technical one. Read top to bottom, the list of steps is the process. Technical staff publish it with the Salesforce and store connections.

Which systems does it use?

This example uses Salesforce and Shopify B2B. QRION works with more than 1,000 business systems, so the same pattern applies to other CRMs and order systems.

## Still retyping won deals into orders?

Bring one of your processes to a working session and see how QRION would run it.

[Book a working session](https://calendar.app.google/yF5awaB5GSSMDumE8)[See the high-value order review](https://co-worq.com/examples/high-value-order-review)