Shopify B2B Draft Order Approval: The Workflow Every Wholesale Brand Needs

The $50K mistake nobody talks about

A sales rep creates a wholesale draft order in Shopify with the wrong customer tier, applies a stacked discount, and clicks "Send invoice." Two days later, the buyer pays and the brand ships—at margins that turn the deal into a net loss. By the time finance reconciles, the goods are out and the discount is locked.

The fix is not "be more careful." It is a structural approval queue between draft order creation and the actions that cost money (invoicing, shipping, completion).

Why Shopify's native flow leaves a gap

• Draft orders can be created by anyone with the right permission.
• "Send invoice" and "Mark as paid" are one click each—no review gate.
• Discounts above policy are visible only if someone looks.
• Custom pricing per customer is great until a rep applies the wrong customer.

The approval queue model

1. Detect. A draft order above a configurable USD threshold lands in a queue, not in the inbox of the merchant.
2. Notify. Approvers receive email (and optional SMS for time-sensitive deals) with deal context.
3. Review. Approver sees customer, line items, discounts, payment terms—directly in Shopify admin.
4. Decide. One-click Approve (invoice goes out) or Reject (with reason logged).
5. Audit. Every decision logged with approver, timestamp, reason.

Threshold rules that match real wholesale

• USD-based: orders under $5,000 auto-approve; $5,000–$25,000 to RevOps; above to Finance.
• Discount-based: any discount above 25% requires approval regardless of value.
• Customer-tier: new accounts always require approval until first three orders complete.
• Payment-term: Net-60 or above goes to Finance regardless of value.

Who sits in the approval matrix

1. RevOps lead: first line for routine wholesale exceptions.
2. Finance: high-value, long-term, or non-standard payment terms.
3. Founder: strategic or first-time enterprise accounts.
4. Delegation: approvers can delegate during vacations without breaking the queue.

Where this pays back fast

• Margin protection: rogue discounts caught before payment.
• Cash flow: Net-60 deals reviewed for credit risk before shipping.
• Compliance: sanctioned countries flagged before invoice.
• Audit: SOC 2 and ISO 27001 reviewers love the trail.

What kills adoption

• Approval queue that requires leaving Shopify admin—reps and approvers both bail.
• Too-low thresholds—every order in the queue, approver fatigue, rubber-stamp.
• No SLA visibility—deals stall in the queue, sales blames "the approval thing."
• No delegation—approver on vacation = full freeze.

Telemetry that proves the queue is working

• Median approval time per tier; alert when SLA breached.
• Rejection rate: if zero, threshold is too high; if very high, rep training is needed.
• Margin saved: dollar impact of rejected/edited orders.
• Audit trail completeness: 100% of approved orders have a recorded approver.

Merchant example: a CPG brand catches a $52K margin error

NorthPeak Supply, a Shopify Plus merchant selling functional beverages to 180 wholesale accounts, ran draft orders without an approval gate for two years. Revenue grew 40% year-over-year — but blended wholesale margin dropped from 38% to 31%. Finance assumed it was freight inflation until a quarterly audit found three reps applying "Established Partner" pricing to accounts that had never completed onboarding.

One draft order in March totaled $52,400: wrong tier (15% instead of 8%), stacked promo code (additional 10%), and Net-60 terms on a buyer with two late payments in the prior year. The rep sent the invoice Friday afternoon. The buyer paid Monday. Warehouse shipped Tuesday. Finance discovered the error Thursday during AR reconciliation — and had no record of who authorized the terms.

NorthPeak implemented a four-step approval queue over 30 days: shadow mode for two weeks, pilot on LATAM accounts for one week, full rollout on day 22. In the first 90 days, the queue flagged 47 orders; 12 were rejected or edited before invoicing. Finance calculated $118,000 in margin protected — more than the annual cost of the approval tooling.

Before vs after: what changes in the rep workflow

How the queue connects to your wholesale stack

Approval is not an island. The queue sits between draft order creation and the downstream systems that move money and goods. When an order is approved, the invoice sends, ERP sync fires, and fulfillment can proceed. When rejected, the rep gets a reason code and edits the draft — no silent overrides.

Integrations worth wiring on day one

• ERP / NetSuite: push approved orders only; block sync for queued or rejected drafts.
• CRM (HubSpot, Salesforce): log approval status on the deal record so account managers see queue state.
• Slack: informational alerts for approvers — decision still happens in Shopify admin, not in a reaction emoji.
• Collections / AR: tie overdue-invoice triggers back into the queue so chronic late payers cannot bypass review.

Rollout mistakes that undo the investment

• Threshold too low: 80% of orders queue on day one; approvers rubber-stamp by week two.
• No shadow mode: rules misfire on live deals; sales blames "the approval thing" forever.
• Missing rep training: reps do not know which orders auto-approve vs queue; they route around via manual tags.
• No SLA visibility: deals stall silently; leadership hears about the queue only when a big account complains.

Where GateFlow fits

GateFlow puts every wholesale draft order above your USD threshold into a queue inside Shopify admin, notifies the right approver via email (SMS on Growth+ plans), and writes a full audit trail. Learn more about GateFlow and join the early-access list.