A Shopify B2B quote approval workflow moves a wholesale request through defined states—intake, review, approval, buyer decision, and draft-order conversion—while keeping buyer, company, pricing, PO, expiry, and revision context attached to the same record. The workflow should make exceptions visible without becoming a general ERP.
Why an inbox is not an approval system
Email is good for communication and poor at representing operational state. A message can show that someone replied, but not reliably whether the latest pricing was approved, which revision the buyer saw, whether the PO number changed, or whether the quote was already converted into a draft order.
Spreadsheets improve visibility but create another source of truth. Product and customer details are copied out of Shopify, commercial decisions live in comments or coloured cells, and approved lines are later copied back into a draft order. Every handoff creates an opportunity for stale data or duplicate work.
Use a small, explicit status model
A status should answer what can happen next. Avoid labels that merely describe how a person feels about the quote. A practical flow might be:
Rejected, expired, cancelled, and revision-requested outcomes branch from that main path. The important rule is that each transition records the actor, time, reason or note where appropriate, and the quote version involved.
Capture enough context at intake
Quote intake should be narrow enough for a buyer or sales representative to complete, but rich enough for the reviewer to make a decision without immediately asking for missing basics.
Avoid collecting data simply because it might be useful later. Customer and company data should be limited to what the quote and draft-order workflow needs.
Make approval rules observable
The reviewer should be able to see why a quote requires approval. A total-value threshold answers a different risk question from a discount percentage threshold. Company-specific routing may be useful for strategic accounts, while multi-step approval is appropriate only when each step represents a real decision right.
For example: “Quotes above $20,000 for Company Group A require finance review before they can be sent.” This is an illustrative policy, not a recommended threshold.
Do not imply that a routing email is access control unless the system enforces identity. If managers can override a step, record the override and reason.
Separate revisions from silent edits
Before any approval decision, correcting a draft or submitted quote in place can be reasonable if the system recalculates totals, re-evaluates rules, and records the edit. After a quote has been approved or shown to the buyer, a material change should create a linked revision.
A revision keeps the previous commercial terms inspectable. It also prevents a buyer acceptance from appearing to apply to a version they never saw.
Keep buyer communication narrower than internal review
A buyer-facing quote view needs the commercial terms, expiry, line items, totals, and clear accept, reject, or revision-request actions. It should not expose internal notes, approval comments, routing metadata, or risk signals.
Tokenised links can support a lightweight portal without creating a full customer-account system. Tokens should expire, be replaceable, avoid storage in raw form where practical, and become invalid after terminal decisions.
When draft orders are better than an unstructured quote inbox
A Shopify draft order is the right handoff when the commercial terms are agreed and the merchant wants Shopify to own the invoice and payment link. The quote remains the record of negotiation and approval; the draft order becomes the commerce object used to complete the sale.
This separation is useful. A quote approval tool does not need to become a payment processor, invoice system, or order-management replacement. It needs to transfer the agreed customer, company, line, pricing, and payment-term context accurately and prevent duplicate conversion.
Design for exceptions without building an ERP
The first useful exception set is small: rejection, buyer-requested revision, expiration, cancellation, failed draft-order conversion, and an unavailable product or variant. Each needs a visible state and a recovery path.
Broad bidirectional ERP synchronisation, custom portals, file storage, sales commissions, and complex identity chains can be deferred until a real merchant workflow proves they belong in the product. Scope discipline keeps the approval desk understandable.
Implementation checklist
- Define the quote owner, status model, and permitted transitions
- List the minimum buyer, company, line, price, and PO fields
- Write approval thresholds in policy language before configuring them
- Separate internal comments from buyer-facing notes
- Decide when edits become linked revisions
- Record actor, timestamp, decision, and relevant reason
- Prevent duplicate draft-order conversion
- Test company, location, catalogue, currency, and payment-term context
- Test expired, rejected, revised, and unavailable-item paths
- Limit customer data and document retention and deletion behaviour
Measure workflow quality, not just quote volume
Useful operational measures include time from submission to first decision, time waiting in each approval step, revision frequency, expiry rate, conversion errors, and the share of quotes that reach a draft order without manual re-entry. Interpret these measures alongside quote complexity and account mix.
These metrics describe process health. They do not by themselves prove that an approval tool increased revenue or win rate.
Related product
B2B Quote Approvals
A focused Shopify Admin approval desk for wholesale quotes and Shopify draft-order conversion.