Should You Build or Buy RFQ & Quoting on Shopify?
RFQ / quoting is a BUILD for mid-market B2B sellers with a dev bench: native Shopify B2B still has no request-a-quote flow (per July 2026 research), draft orders already act as Shopify's quote object, and an estimated $20,000–$50,000 build (Deploi estimate, illustrative) adds the request form and the approval rules your sales team actually follows. Buy a quote app for a this-week launch, light quote volume, or no dev capacity.
Your profile — see how the verdict shifts
- Confidence
- Medium — Draft orders are a stable native quote primitive and the RFQ gap is real, but the verdict swings on sales-team workflow fit, and quote-app pricing is unverified
- Reference scenario
- $20M–$100M revenue · blended DTC + B2B storefront · inside sales team negotiating price · agency dev bench
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Under $2M B2B revenue | BUY | A handful of quote requests a month doesn't justify a build. A light app, or a plain contact form your team answers with hand-made draft orders, covers it. |
| $2M – $15M B2B revenue | DEPENDS | Buy if fielding price requests is the whole job. Build the moment real negotiation starts: margin floors and approval tiers are workflow, and workflow is what generic apps can't ship. |
| $15M – $75M B2B revenue | BUILD | Quote volume makes the request-to-draft-order pipeline pay in rep time, controlled discounts, and owned win-rate data. This is the reference scenario. |
| $75M+ B2B revenue | BUILD | Quoting is your sales operating system at this scale: it wires into CRM, ERP, and rep-level pricing authority that no generic portal models. |
What RFQ / quoting Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | Large and custom orders convert through a quote or not at all: a working RFQ path captures deals that would never enter standard checkout. |
| Operational efficiency | High | The request arrives as structured data and becomes a draft order in clicks rather than a re-keyed email thread; acceptance converts the quote to a paid order by itself. |
| Data & insight | High | Request-to-quote time, win rate, and discount depth by rep and account are pricing intelligence, and the build-vs-buy choice decides who holds them. |
| Customer experience | Medium | Serious wholesale buyers expect a quote path with a clear response time; a bare mailto link reads as a store that doesn't really do B2B. |
| Retention & LTV | Medium | Fast, consistent quote turnaround is how wholesale accounts get sticky, and negotiated pricing gives the account a standing reason to keep ordering here. |
Spend ceiling: The request form is the cheap half; the approval rules, margin floors, and quote data carry the value. If buyers just want to see hidden prices and nobody truly negotiates, a light app is the honest ceiling. Save the build budget until real negotiation shows up.
What buying enables (top apps)
- + Hide-price and request-a-quote buttons live this week, with vendor-maintained theme compatibility
- + A structured request inbox instead of a mailto: products, quantities, and buyer details captured in one place
- + Convert-to-draft-order handoffs on some tiers, a genuine workflow head start
- + A proven pattern for opening a trade lane on a retail storefront without touching your theme's code
What building additionally unlocks
- + Your approval chain encoded: discount authority by rep, margin floors checked before a quote ever sends, expiry and revision rules
- + Quote-funnel data as owned draft orders and metaobjects: win rates, discount depth, and time-to-close feeding CRM and pricing decisions with no export ceiling
- + One pipeline from request to paid order inside Shopify, composing with the native B2B you already run (companies, catalogs, net terms)
- + Rep-facing tooling shaped to your team: quote templates, margin visibility, and follow-up nudges no generic portal ships
Find Your Verdict in 3 Questions
Is there a dev bench, agency or in-house, that can own a quoting workflow?
Yes: Go to question 2.
No: Your verdict: BUY — a quote app is the only same-quarter path; check exports at signup and diary a re-decision when dev capacity exists.
Does your sales team actually negotiate (margin floors, approval tiers, revision rounds) rather than just field price requests?
Yes: Your verdict: BUILD — draft orders already model the quote; build the request form and the approval rules your reps follow.
No: Go to question 3.
Is quote volume past a handful of requests a week?
Yes: Your verdict: BUILD — at real volume the request-to-draft-order pipeline pays for itself in rep time and controlled discounts.
No: Your verdict: BUY — a light request-form app, or a plain form feeding hand-made draft orders, covers occasional quotes; revisit when volume grows.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | A quote app configures in days; the request-form, draft-order, and approval build runs an estimated 6–10 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | Quote-app fees are modest but permanent, and volume or seat tiers step up as B2B grows; the build's recurring line is flat upkeep with no per-quote fee. | ||
| Maintenance & upgrades | The vendor keeps the widget and portal current for you; a build tracks Shopify's roughly six-month API version cycle across a small, stable surface. | ||
| Switching & exit | Quote history and negotiation threads accumulate in the vendor's database, and exports vary by tier; on the build they're draft orders and metaobjects that never leave your store. | ||
| Risk | |||
| Vendor risk | A fragmented category of mostly small vendors with no verified names yet; a build has no vendor to lose. | ||
| Security & compliance surface | Negotiated prices and buyer contact data sit with a third party on the buy path; the build keeps them inside your Shopify admin. | ||
| Platform-deprecation exposure | Draft orders are a first-class, stable Admin API object; request widgets injected into themes break at theme updates and breakpoints (community-reported pattern). | ||
| Value | |||
| Fit to requirement | Apps ship a generic request form and a hidden-price toggle; the actual requirement is your sales team's workflow: who approves, what the margin floor is, how revisions run. | ||
| Time to market | Days for an app versus an estimated 6–10 weeks for the build (Deploi estimate, illustrative); speed is the app path's honest win. | ||
| Performance & scale | The app adds one more injected script to product pages; the real scale question is quote throughput per rep, where a pipeline beats an inbox. | ||
| Data ownership & AI-readiness | Request-to-quote time, win rate, and discount depth by rep and account are pricing intelligence; owned as draft orders and metaobjects they feed CRM and margin models with no export ceiling. | ||
| Focus & opportunity cost | A quoting build competes with storefront work for the same bench; when B2B is the growth lane, it is the revenue work, which softens the trade. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Quote apps (request-a-quote widgets, category) | Live — A fragmented category of mostly small vendors; shortlist named vendors | Free–$50/mo bands (illustrative) | Hiding prices from retail and capturing structured quote requests without dev work |
| Quote apps (quote-management portals, category) | Live — The deeper end of the category: request tracking, statuses, and draft-order handoff on some tiers | $25–$150/mo bands (illustrative) | Sales teams that want vendor-maintained quote tracking without owning a build |
| Custom (request form + draft orders + approvals) | Build lane — This page's build path The recognized pattern for this named native gap; detailed in the build path below | One-time build, $20,000–$50,000 (Deploi estimate, illustrative) | Teams that negotiate for real: margin floors, approval tiers, owned quote data |
The Build Path
- Quote-request form on metaobjects: A theme section captures products, quantities, company, and target terms into a quote-request metaobject: structured data from the first click, with notifications into email or Slack for the rep on point.
- Draft orders as the quote object: A rep (or a Flow automation) turns the request into a draft order with custom prices, discounts, and payment terms; the invoice email is the quote, and the buyer's checkout converts it to a paid order with no re-keying.
- Approval and margin-floor layer: Discount authority by rep and a margin-floor check run before any quote sends; expiry dates and revision notes live on the draft order, so the negotiation has one source of truth.
- CRM and reporting plumbing: Webhooks push quote events into your CRM and warehouse: request-to-quote time, win rate, and discount depth by rep and account become standing reports.
- Effort band
- $20,000–$50,000 for the request form, draft-order pipeline, and approval layer (Deploi estimate, illustrative); most scopes land in the $25–75K contact-form band
- Typical timeline
- 6–10 weeks (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year, roughly $3,000–$10,000/yr (Deploi estimate, illustrative): API version bumps about every six months plus the quote-rule tweaks sales keeps asking for. There is no per-quote or per-seat line.
- What you own — and what you take on
- You own: the request data, the approval rules, the quote history as draft orders, and the funnel metrics. You take on: sales-team adoption, edge cases like expiry and mid-quote inventory changes, and the upkeep above.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $0–$1,000 (setup + theme placement) | $20,000–$50,000 |
| Years 1–3 (recurring) | $1,800–$9,000 (subscription tiers) | $9,000–$30,000 (maintenance) |
| 3-year total | ≈$1,800–$10,000 | ≈$29,000–$80,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † App path: a mid-tier quote app held flat; category pricing is unverified, so bands are deliberately wide.
- † Build path: request form, draft-order pipeline, and approval layer; maintenance at ~15–20% of build cost per year; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Request widgets injected as theme scripts break at theme updates and breakpoints (community-reported pattern)
- — The negotiation record accumulates in the vendor's database; export completeness varies by vendor and tier
- — Volume and seat tiers creep as B2B grows, so the fee peaks exactly when quoting works
- — The moment a request needs human judgment, apps hand negotiation back to email; you pay the subscription and keep the manual workflow
On the build path
- — The form is the easy 20%; approval rules, expiry, and revision rounds are the real scope
- — Sales-team adoption is the hidden risk: spec the workflow with your reps or they'll keep quoting in spreadsheets beside it
- — Draft-order edge cases need explicit rules: inventory shifts between quote and acceptance, expired quotes, re-quotes on revised requests
- — ~15–20% of build cost per year in upkeep (Deploi estimate, illustrative)
What Merchants Say
The recurring shape in B2B threads: native B2B brought companies, catalogs, and net terms, but a buyer still can't ask for a quote; merchants keep calling RFQ the missing flow.
The app-review complaint shape: the request form works, then the actual negotiation falls back to email, and the 'portal' turns out to be a themed inbox the team stops checking.
If You Change Your Mind Later
If you bought and outgrow it
Check exports the day you sign, not the day you leave: quote history, win-loss outcomes, and buyer details vary by vendor and tier. The form is replaceable in an afternoon; the accumulated negotiation record is the asset at risk, and it's the input your future pricing decisions want.
If you built and want out
Little is stranded: quotes live as draft orders and requests as metaobjects, all inside your store, so retreating to an app later, or moving up to a CPQ suite, keeps the history queryable. The custom code is the only sunk cost, and the workflow spec ports anywhere.
When This Answer Changes
We're watching for:
- ▸ Shopify shipping a native request-a-quote or negotiation flow in B2B (the named gap in the 2026-04-02 release, still open per July 2026 research)
- ▸ Native B2B closing neighboring gaps like auto-approve registration or buyer-side order edits: movement there signals RFQ may be next (per July 2026 research)
- ▸ A major platform or CRM vendor entering the Shopify quote-app category
Verdict change log:
No changes since first publication (August 2026).
Common Questions
Does Shopify have a native RFQ or quote feature?
No. Native B2B, on all paid plans since April 2026, covers company profiles, catalogs, volume pricing, and net payment terms, but buyers still can't request a quote (per July 2026 research). Shopify does ship the back half, though: draft orders, which hold negotiated prices and convert to paid orders. The missing front half, a request form plus approval flow, is exactly what you buy or build.
How do draft orders work as quotes on Shopify?
A draft order is Shopify's quote object: your team sets custom line prices, discounts, and payment terms, sends the invoice email as the quote, and the buyer's checkout converts it into a real order with no re-keying. A build wraps that primitive with the missing pieces: a structured request form, approval rules, and expiry. That's why the build composes well: you're extending Shopify, not replacing it.
When is a quote app the better choice?
When speed or capacity decides: a quote app puts hide-price and request-a-quote buttons live this week with no dev bench, and at a handful of requests weekly the subscription is cheaper than any build (illustrative). The ceiling arrives when real negotiation starts: approval tiers, margin floors, and revision rounds are workflow, and workflow is what generic portals can't express.
Your Next Steps
If you're going with BUILD(matches your selected profile)
- Map the quote workflow with your reps first: who requests, who prices, who approves, and where the margin floor sits
- Model the quote request as a metaobject: products, quantities, company, target price, notes
- Make the draft order the single quote object: custom prices, terms, expiry note, invoice email as the quote
- Encode approval rules before launch: discount authority by rep and a margin-floor check before any quote sends
- Instrument the funnel from day one: request-to-quote time, win rate, and discount depth are the numbers that run your pricing
If you're going with BUY
- Shortlist quote apps by workflow fit, not feature count: does the request convert to a draft order your team can finish?
- Verify exports before signup: quote history, statuses, and buyer details, on your actual tier
- Keep the negotiation record in your CRM from day one, so the app holds the form, not the relationship
- Cap script weight: load the request widget on B2B surfaces only
- Diary a re-decision at the first workflow the app can't express, or the first tier jump
Official Docs & Sources
- Shopify B2B — Shopify Help Center
- Apps and B2B — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Do You Still Need a B2B App Now That Shopify Does B2B Natively?
Most Shopify merchants should pause B2B app spending: native B2B shipped to every paid plan on April 2, 2026.
Should You Build or Buy B2B Catalogs & Price Lists on Shopify?
Native catalogs carry B2B price lists until the 3-catalog cap bites; past it, customize with API-generated catalogs instead of renting a parallel pricing database.
B2B Company Accounts on Shopify: Buy an App, Build, or Go Native?
Company accounts and permissions no longer justify an app for most Shopify merchants: native B2B covers the core on every paid plan since April 2, 2026.
Build or Buy a Blended DTC + B2B Storefront on Shopify?
Native B2B made the blended storefront the default architecture; the build is theme conditionality, and the real fork is one store or two.
Should You Build or Buy Your NetSuite Integration on Shopify?
NetSuite integration is the honest DEPENDS: buy a connector for standard flows, build middleware when the flows are the business.
Ready to quote the way your sales team actually sells?
We'll map your negotiation workflow, spec the request-form-to-draft-order pipeline against what quote apps genuinely cover, and put honest numbers on the build. If a light app is the right call for your volume, we'll say so.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.