RFQ in B2B Ecommerce: Quote Management, Custom Pricing & Sales Workflows
Request for Quote is the transaction type that separates B2B ecommerce from B2C. Consumer stores have fixed prices and add-to-cart buttons. B2B stores have negotiated pricing, volume discounts, custom configurations, and sales teams who need to approve terms before an order is placed. The RFQ process is where these realities intersect with digital commerce.
Most B2B companies handle quoting through email. A buyer sends a request, a sales rep opens a spreadsheet, calculates pricing based on volume and account history, sends back a PDF, the buyer responds with changes, the rep revises, and three days later an order might happen. This process works – until you’re handling 50 quotes per day and losing deals because your response time is measured in days while competitors respond in hours.
Building RFQ into your ecommerce platform doesn’t eliminate the sales team. It eliminates the manual friction that slows them down. The goal is a system where buyers can submit structured requests digitally, sales teams can respond with accurate pricing quickly, approvals happen within the system instead of over email, and the accepted quote converts directly into an order without re-entering data.
We’ve built quoting systems for manufacturers, distributors, and wholesale operations. The implementations that work share common patterns. The ones that fail share common mistakes. This guide covers both.
What Is RFQ in B2B Ecommerce?
A Request for Quote is a formal buyer inquiry asking a seller for pricing on specific products or services, typically with defined quantities, specifications, and delivery requirements. In B2B ecommerce, the RFQ process is the digital workflow that replaces the email-and-spreadsheet cycle with structured submission, response, negotiation, and conversion.
The RFQ is distinct from catalog purchasing. Catalog purchasing uses published prices – the buyer adds products to a cart and checks out. RFQ purchasing uses negotiated prices – the buyer specifies what they need, the seller provides custom pricing, and the transaction happens only after both parties agree on terms.
In practice, most B2B ecommerce platforms need both. Some products have fixed catalog pricing. Others require quoting. Some customers get catalog pricing on standard items and negotiate on custom configurations. The quoting system needs to coexist with catalog purchasing, not replace it.
Key Takeaways
- RFQ is a conversion workflow, not a feature checkbox. The quoting process is where B2B buyers decide whether to purchase from you or your competitor. Response time, pricing accuracy, and workflow friction directly affect close rates.
- Quote response time is the single biggest conversion factor. Buyers who receive quotes within 4 hours are 4-6x more likely to convert than those who wait 24+ hours. Automating price calculation and approval routing compresses response time from days to hours or minutes.
- The accepted quote must become an order with one click. If a buyer accepts a quote and then has to re-enter products, quantities, and pricing into a separate order form, you’ve failed. Quote-to-order conversion should be a single action.
- Sales teams need visibility, not data entry. Reps should spend time on pricing strategy and customer relationships, not copying data between systems. The quoting platform should auto-populate product data, apply pricing rules, and handle calculations.
- Integration with ERP and CRM is non-negotiable. Quotes that exist only in the ecommerce platform create data silos. Quote data must flow to ERP for margin validation and to CRM for pipeline tracking.
What Quoting Systems Handle
1. Product Configuration and Specification
For configurable products – custom dimensions, material selections, finishing options, assembly configurations – the quoting system captures the complete specification. This goes beyond variant selection. A buyer requesting a quote for 500 custom-machined parts needs to specify material grade, tolerance requirements, surface finish, and certification requirements. The quoting system must capture these specifications in structured fields that the sales team can price against.
2. Volume-Based Pricing Calculation
B2B pricing almost always varies by volume. A quoting system applies tiered pricing automatically: 1-99 units at list price, 100-499 at 12% discount, 500-999 at 18% discount, 1000+ at negotiated pricing requiring sales approval. The system calculates the price, the rep validates or adjusts, and the buyer sees the final number – not a vague “volume discounts available” message.
3. Multi-Line Quote Management
B2B purchases are rarely single items. A typical RFQ includes 10-50 line items across multiple product categories, each with its own quantity, specification, and pricing logic. The quoting system must handle multi-line submissions, allow per-line-item pricing adjustments, calculate totals with mixed discount structures, and present a coherent quote document.
4. Approval Workflows and Margin Protection
Not every quote should go out without review. Quotes below margin thresholds, quotes for new customers, quotes exceeding dollar limits, or quotes with non-standard terms need approval before they reach the buyer. The quoting system routes these to the appropriate approver – sales manager, finance, operations – with context about why the quote was flagged.
5. Quote Lifecycle Management
A quote is not a single event. It’s a lifecycle: draft, submitted, under review, approved, sent to buyer, buyer reviewing, accepted, converted to order – or rejected, expired, revised. The system tracks this lifecycle, sends reminders for expiring quotes, allows revisions without starting over, and provides reporting on conversion rates, response times, and lost-quote reasons.
Buyer vs. Seller Workflow
| Step | Buyer Experience | Seller Experience |
|---|---|---|
| Request initiation | Adds items to quote cart from catalog or submits custom specification form | Receives structured RFQ with product details, quantities, and buyer account information |
| Pricing | Waits for quote response (ideally hours, not days) | System auto-calculates pricing based on volume, account tier, and margin rules; rep reviews and adjusts |
| Negotiation | Reviews quote, requests changes to pricing/quantities/terms | Receives revision request, adjusts quote, resubmits |
| Approval | Internal approval workflow (if buyer org requires it) | Internal approval workflow for margin exceptions or non-standard terms |
| Acceptance | Accepts quote, which converts to order with one click | Order created automatically from accepted quote, flows to fulfillment |
| Follow-up | Tracks order status, reorders from previous quotes | Quote analytics: response time, conversion rate, average deal size |
RFQ Workflows in Detail
The Buyer-Initiated RFQ
The most common workflow. A buyer browses your catalog, selects products they want to quote (rather than add to cart), specifies quantities and any custom requirements, and submits the RFQ. The system routes the request to the appropriate sales rep based on territory, account assignment, or product category.
What makes this work. The RFQ submission must capture enough information for the sales team to price accurately without follow-up questions. Required fields for specifications, delivery timeline, and any special requirements reduce back-and-forth. Account-specific context (purchase history, contract terms, credit status) should auto-populate so the rep doesn’t start from zero.
Where this breaks down. When the RFQ form is a generic text box that says “describe your needs” – the rep spends more time clarifying requirements than calculating pricing. When submitted RFQs sit in a shared email inbox instead of a routed queue, response times depend on who checks the inbox first.
The Sales-Initiated Quote
The rep creates a quote proactively – during a phone call, after a site visit, or based on a buyer’s purchasing patterns. The quoting system allows the rep to build a quote from the product catalog, apply customer-specific pricing, add notes and terms, and send it directly to the buyer’s account.
What makes this work. The rep can build a quote quickly using product search, recent order history, and saved pricing templates. The quote appears in the buyer’s ecommerce account alongside any RFQs they’ve submitted, creating a single view of all active quotes.
Where this breaks down. When the quoting system is disconnected from the ecommerce platform and quotes are sent as email attachments. The buyer receives a PDF they can’t interact with – they can’t adjust quantities, accept individual line items, or convert to order without manual data entry.
The Automated Re-Quote
For repeat purchases, the system generates a new quote based on a previous order, updated with current pricing. The buyer receives a notification that their quote is ready for review. If pricing hasn’t changed, they accept with one click. If pricing has changed, the delta is highlighted and they can accept, negotiate, or decline.
What makes this work. Automation handles the 60-70% of quotes that are routine reorders with stable pricing. Sales reps focus on the 30-40% that require negotiation, custom pricing, or new products. Buyer satisfaction increases because reorder quoting takes seconds instead of days.
Where this breaks down. When pricing changes aren’t communicated clearly – the buyer accepted last quarter’s quote at $12.50/unit and the automated re-quote shows $13.75 without explanation. Transparency about price changes (raw material cost increase, volume tier change) maintains trust.
The Multi-Vendor RFQ (Buyer Side)
A buyer needs to source from multiple suppliers and wants to compare quotes side by side. On platforms that support this workflow, the buyer submits the same RFQ to multiple vendors, receives responses in a normalized format, and compares pricing, lead times, and terms in a single interface.
What makes this work. Standardized RFQ formats that different suppliers can respond to consistently. Comparison tools that normalize across different pricing structures (per-unit vs. per-case, different shipping terms). This is where marketplace platforms have an advantage over standalone B2B stores.
Where this breaks down. When suppliers respond in different formats, with different inclusions and exclusions, making apples-to-apples comparison impossible without manual normalization.
Platform Options for RFQ
Adobe Commerce (Magento) B2B Module
Adobe Commerce includes a native B2B module with quote management functionality. Buyers request quotes from the storefront, sales reps respond from the admin panel, negotiation happens within the platform, and accepted quotes convert to orders.
Strengths. Native integration with catalog, pricing, and customer account systems. Multi-company account support with separate negotiation permissions. Quote expiration, revision tracking, and line-item-level pricing adjustments. No third-party extensions required for basic quoting.
Limitations. The quoting UI in the admin panel is functional but not designed for high-volume quote operations. Complex approval workflows require customization. Integration with external CRM or CPQ systems requires development. The buyer-side quote experience is basic compared to purpose-built CPQ platforms.
Best for. B2B operations where quoting is one of several purchasing methods (alongside catalog purchasing) and where the volume of quotes is manageable through the Magento admin interface – typically under 100 quotes per day.
Shopware B2B Suite
Shopware 6 with the B2B Suite extension provides quote management as part of a broader B2B commerce workflow. The implementation is tightly integrated with Shopware’s rule engine, allowing complex pricing and approval logic.
Strengths. Deep integration with Shopware’s rule-based pricing engine – volume tiers, customer group pricing, and time-based pricing can be applied automatically to quotes. Organizational buying structure with budget management and approval hierarchies. Flow Builder allows customizing quote workflows without code.
Limitations. The B2B Suite is a commercial extension, adding cost on top of the Shopware license. Ecosystem is smaller than Adobe Commerce, with fewer third-party integrations. Documentation for advanced B2B quoting scenarios is limited compared to Adobe Commerce.
Best for. B2B operations prioritizing workflow flexibility and rule-based automation, especially those also needing organizational buying structures with budget controls.
CPQ Platforms (Configure-Price-Quote)
Dedicated CPQ platforms like Salesforce CPQ, Oracle CPQ, or Vendavo handle complex quoting scenarios that ecommerce-native solutions can’t: configurable products with compatibility rules, complex pricing models with multiple discount dimensions, guided selling workflows, and document generation. They integrate with your ecommerce platform through API.
Strengths. Purpose-built for complex quoting: product configuration with constraint validation, multi-dimensional pricing, approval workflows with parallel routing, and professional quote document generation. Handles the scenarios where a product has 50 configurable options and pricing depends on the combination.
Limitations. Expensive – Salesforce CPQ starts at $75/user/month and enterprise implementations often cost $200K+ to deploy. Integration with ecommerce platform adds complexity. Overkill for straightforward volume-based quoting. Learning curve for sales teams is significant.
Best for. Operations with highly configurable products, complex pricing models, and large sales teams. Manufacturing companies with engineered-to-order products. Businesses where a single quote can involve 100+ line items with interdependent configuration options.
Third-Party Quoting Extensions
For platforms that don’t include native quoting (or where native quoting is insufficient), third-party extensions add RFQ capabilities. Options exist for Magento (Cart2Quote, Quotation Manager), Shopify (various apps), WooCommerce (YITH Request a Quote), and other platforms.
Strengths. Lower cost than CPQ platforms or platform migration. Can be implemented quickly (days to weeks vs. months). Often designed for the specific platform’s workflow patterns.
Limitations. Feature depth varies dramatically. Integration with pricing rules, customer accounts, and ERP may be shallow. Support and maintenance depend on the extension developer’s longevity. Upgrading the underlying platform can break extension compatibility.
Best for. Businesses that need basic quoting functionality without the cost or complexity of native B2B platforms or CPQ systems. A good starting point before committing to a more comprehensive solution.
Real-World Implementations
Industrial Parts Distributor
A distributor handling 2,000+ SKUs across fasteners, fittings, and electrical components needed to move quoting from email to their ecommerce platform. Their challenge: 80% of orders started as quotes because most customers had negotiated pricing, but the email-based process averaged 18-hour response times and the close rate on quotes over 24 hours old was under 15%.
What we built. Quote request from catalog with quantity breaks auto-calculated from the customer’s pricing tier. Sales dashboard showing all open quotes ranked by value and time-since-submission. Automated pricing for quotes within standard margin ranges (no rep intervention needed). Approval routing for quotes below margin floor or above dollar threshold. One-click quote acceptance that creates an order with the quoted pricing locked in.
Results. Average quote response time dropped from 18 hours to 2.4 hours. Quote-to-order conversion increased from 34% to 51%. Sales reps handled 3x more quotes per day because they only manually priced the 30% that fell outside automated rules. The system paid for itself within four months through recovered deal velocity alone.
Custom Packaging Manufacturer
A packaging manufacturer producing custom boxes, inserts, and displays needed a quoting system that could handle product configuration (dimensions, material, print specifications, finish, quantity) with pricing that varied across all these dimensions. Their existing process: buyer fills out a web form, production team manually calculates pricing, sales rep creates a quote in Excel, emails it to the buyer. Average turnaround: 3-5 business days.
What we built. A structured configuration interface where buyers specify exact dimensions, select materials from qualified options, upload artwork for print specifications, and choose finishing options. The system calculates a preliminary price estimate using a pricing matrix and displays it immediately. For standard configurations, this estimate is the final price. For custom configurations that fall outside the matrix, the system routes to production engineering for precise pricing with full context – no follow-up questions needed.
Results. Standard configuration quotes (65% of volume) went from 3-5 day response to instant pricing. Custom configuration quotes dropped to same-day response because the structured submission eliminated the clarification cycle. Buyer satisfaction scores improved measurably because the pricing process felt professional and responsive rather than manual and slow.
Common Mistakes
| Mistake | What Happens | What to Do Instead |
|---|---|---|
| Quote form is a text box | Reps spend time clarifying instead of pricing | Structured fields for product, quantity, specs, timeline |
| No automated pricing rules | Every quote requires manual calculation | Auto-calculate for standard scenarios, manual for exceptions |
| Quote lives only in email | No tracking, no analytics, no reuse | Quote lifecycle management in platform |
| Quote doesn’t convert to order | Buyer re-enters data to place order | One-click acceptance creates order |
| No quote expiration | Stale quotes with outdated pricing get accepted | Configurable expiration with renewal workflow |
| No approval workflow | Reps give away margin without oversight | Automated routing for exceptions |
| Separate systems for quoting and ordering | Data discrepancy between quoted and ordered | Single system or tight integration |
The Mistakes in Detail
Treating the RFQ form as a suggestion box. If your quote request form is an open text field where buyers describe what they want in freeform, you’ve built an email system with extra steps. Every unstructured submission creates a clarification cycle: the rep reads the request, doesn’t have enough information, emails the buyer for details, waits for a response, then starts pricing. Structured fields – product selection from catalog, quantity inputs, specification dropdowns, delivery date pickers – eliminate this cycle entirely.
Calculating every quote manually. If your sales team manually calculates pricing for every quote, including routine reorders at standard pricing, you’re paying knowledge workers to do arithmetic. Implement pricing rules that auto-calculate for standard scenarios: volume tiers, customer-specific pricing, contract pricing. Manual intervention should be reserved for exceptions – custom configurations, non-standard terms, margin exceptions.
Disconnecting quoting from the catalog. When your quoting system doesn’t pull product data from your catalog, reps manually enter product names, SKUs, and descriptions into quotes. This creates errors and inconsistencies. Quotes should be built from catalog data – product details, images, specifications, and base pricing auto-populate from the catalog. The rep adds quantity and adjusts pricing, not product data.
Ignoring quote analytics. If you can’t answer these questions, your quoting process is a black box: What’s your average quote response time? What’s your quote-to-order conversion rate? Which reps close the most quotes? Which product categories have the highest quote volume? What’s your average deal size by customer segment? These metrics drive operational improvements.
Building quoting as an isolated module. A quote that exists only in your ecommerce platform but doesn’t sync to CRM (for pipeline tracking) or ERP (for margin validation and order processing) creates operational silos. The sales team can’t see quote activity in their CRM. Finance can’t validate margins against ERP data. When the quote converts to an order, someone re-enters data into the ERP. Integration isn’t optional – it’s what makes quoting operational rather than decorative.
Measuring Quoting Effectiveness
Track these metrics to evaluate whether your quoting system is actually improving your business.
Quote response time. Measured from buyer submission to quote delivery. Segment by quote type (standard vs. custom) and by rep. Industry benchmark: under 4 hours for standard quotes, under 24 hours for custom. If your average exceeds these, the system isn’t fast enough.
Quote-to-order conversion rate. Percentage of sent quotes that convert to orders. Segment by product category, customer segment, deal size, and rep. A healthy B2B quote conversion rate is 25-50% depending on industry. Below 20% suggests pricing or response time issues.
Average deal size. Track whether digital quoting changes deal size. Often it increases because the structured interface makes it easier for buyers to add line items and because automated pricing removes the friction of requesting quotes for additional products.
Quote revision rate. How many quotes go through revision before acceptance. A high revision rate (above 30%) suggests pricing is frequently misaligned with buyer expectations or that the initial quote doesn’t capture requirements accurately enough.
Time-to-close. Days from initial RFQ to order placement. Track the full cycle, including negotiation and revision rounds. Compare against your pre-system baseline and against industry benchmarks.
Expired quote rate. Percentage of quotes that expire without buyer action. High expiration rates (above 40%) suggest either poor lead qualification (sending quotes to unqualified buyers) or uncompetitive pricing.
Platform-Specific Implementation Notes
Adobe Commerce. Enable the B2B module. Configure company accounts with appropriate quote permissions. Set up price negotiation rules and quote expiration periods. Customize the quote email templates. For advanced workflows, extend the quote API to integrate with external CRM or CPQ systems. Consider the Magento Quote Extension for features beyond native capabilities.
Shopware 6. Install the B2B Suite extension. Configure organizational structures with budget management. Set up Flow Builder rules for quote approval routing. Use the Rule Builder for automated pricing logic. The B2B Suite’s quote management integrates with Shopware’s order management – accepted quotes flow directly into order processing.
WooCommerce. Install a quoting plugin (YITH Request a Quote is the most established). Configure which products allow quoting vs. standard purchase. Set up email notifications for quote requests and responses. Limitations: WooCommerce quoting plugins are generally simpler than platform-native B2B solutions – they handle basic request-respond-accept flows but lack advanced approval workflows, margin validation, and deep ERP integration.
Headless/API-first platforms. Build the quoting workflow as an API service that your frontend consumes. This gives maximum flexibility for the buyer-facing experience but requires building the complete workflow: submission, assignment, pricing calculation, approval, revision, acceptance, and order conversion. Use your ERP or CRM as the system of record for quotes if the ecommerce platform doesn’t have native quoting.
The Future of RFQ in B2B Ecommerce
Three trends are reshaping how B2B quoting works:
AI-assisted pricing. Machine learning models trained on historical quote data, win/loss outcomes, and market pricing can suggest optimal pricing for each quote – maximizing close probability while protecting margins. The sales rep sees a recommended price with confidence interval, not just a cost-plus calculation. Early implementations show 5-15% improvement in both conversion rate and average margin.
Agentic procurement. AI agents acting on behalf of buyers will submit RFQs programmatically, evaluate responses automatically, and accept quotes that meet defined criteria without human intervention. This requires quoting systems with complete API coverage – submission, response, negotiation, and acceptance all accessible through machine-to-machine interfaces. See our analysis of AI agentic commerce for the broader implications.
Real-time dynamic pricing. Instead of static price lists with manual adjustments, pricing engines that factor in real-time inventory levels, demand signals, competitor pricing, raw material costs, and production capacity to generate optimized quotes instantly. The buyer submits an RFQ and receives pricing within seconds that reflects current market conditions – not last quarter’s price sheet.
Frequently Asked Questions
When should a B2B store use quoting vs. catalog pricing?
Use catalog pricing for standardized products with stable pricing and straightforward purchasing – products where every buyer pays the same price (or a price determined by their customer group). Use quoting when pricing depends on volume, configuration, customization, or negotiation – when the price isn’t knowable until the buyer specifies what they need and how much they need. Most B2B stores use both: catalog pricing for standard items and quoting for custom, high-volume, or complex purchases.
How do I handle RFQ for products with long lead times?
Include lead time estimates in the quote response. For made-to-order products, the quote should include both pricing and a delivery timeline based on current production capacity. Build production capacity checking into the quoting workflow so the quoted delivery date is realistic, not aspirational. If lead times change between quote submission and acceptance, notify the buyer proactively.
What’s the minimum viable quoting system?
At minimum: a structured RFQ submission form (not a text box), email notification to the assigned sales rep, a way for the rep to respond with pricing within the platform, buyer notification of the quote response, and one-click acceptance that creates an order. This can be built with a quoting plugin in days. It won’t have approval workflows, automated pricing, or analytics – but it replaces the email-and-spreadsheet process.
How do I integrate quoting with my ERP?
Quotes should sync to ERP for two purposes: margin validation during quote creation (checking that quoted pricing meets minimum margin requirements) and order creation when a quote is accepted. The integration approach depends on your ERP and ecommerce platform. Middleware platforms (Celigo, Boomi, MuleSoft) handle data mapping and transformation. Direct API integration works for simpler scenarios. The key requirement: when a quote converts to an order in your ecommerce platform, the order must appear in your ERP without manual data entry.
How do I handle quote revisions without losing the history?
Every quote revision should be versioned. Version 1 is the original quote. Version 2 is the buyer’s requested revision. Version 3 is the seller’s response. Each version preserves the complete quote state – line items, pricing, terms, notes. The buyer and seller should be able to see what changed between versions. This history is essential for dispute resolution and for analyzing negotiation patterns.
Can I automate quote approval without losing pricing control?
Yes, through rule-based approval. Define the conditions under which quotes can be auto-approved: within standard margin range, below a dollar threshold, for established accounts with good payment history, for standard (non-custom) products. Quotes that fall outside these rules route to human approvers. Start conservative (auto-approve only the most routine quotes) and expand automation as you gain confidence in the rules.
How do I handle international RFQs with different currencies and terms?
Configure multi-currency pricing in your quoting system. Quotes should display in the buyer’s preferred currency with the exchange rate locked at quote creation (or quote acceptance, depending on your policy). Terms and conditions should be localizable. Tax handling, Incoterms, and payment terms may vary by region. For international quotes, include explicit terms about which party bears shipping costs, customs duties, and exchange rate risk.