RFQ vs cart-only B2B checkout — when to pick which

A classic B2B-webshop design question: do you let the buyer click a button and order, or do you make them request a quote (RFQ — Request for Quote) first? “Always RFQ” and “always cart” are both broken patterns. The right answer: decide per product category, based on measurement.

The numbers on nortinia.com itself

On our own webshop, which sells both consulting packages and AI products, on a 90-day window:

• Consulting packages (Tier 2-3, hybrid “on-premise + consulting”): 73% flowed through RFQ. Average contract value EUR 8,400. Average response time to an RFQ within 14 hours; quote-to-contract conversion: 41%.
• Tier-1 AI products (fixed price, self-serve, ≤ EUR 600/month): 27% went through the classic cart-only path. Cart-to-payment conversion: 62%; cart abandonment 38%. Average order value EUR 287.

The two paths aren't rivals — they complement each other. The mistake is trying to cram both buyers into a single flow.

When cart-only

When all three of these hold:

1. Fixed, publishable price — no negotiation, no sizing by buyer.
2. Self-serve provisioning — the product activates automatically after payment (API key, access, etc.); no “a colleague has to handle it”.
3. The buyer's role is appropriate — one person (an exec, an IT lead) can close the purchase on the corporate card. If 3 approvers are involved, drop cart-only.

Upsides: fast conversion, no sales overhead, buyer decides on their own pace. Downsides: only works under the upper limit — above EUR 1,000-1,500/month an engagement conversation is often needed.

When RFQ

Conversely, when any of these holds:

1. Custom scope — every customer buys something different (consulting project, custom integration, hybrid product)
2. Price can't be stated pre-discovery — it takes 30 minutes of conversation to figure out whether a 4-week or 12-week project is required
3. Onboarding takes time — the sales handoff adds value, because without a pre-sales architect call the buyer picks the wrong package

Upsides: better match, less churn, higher average value. Downsides: slower (mean 11 days deal-time RFQ → contract), bound by sales capacity.

The hybrid “cart-only quote”

There's a third path, which the flow we shipped on 2026-06-14 introduced: a consulting package goes into the cart, but the cart triggers a quote request, not an order. The buyer assembles the package (3 modules + 1 audit), and the “I'm interested” button generates a quote equivalent to a classic RFQ — BUT with the cart UX, matching the buyer's mental model.

Measurement: this hybrid generated 18% more quote requests than the pure form-based RFQ, and the sales team got the same amount of work — just with more structured data. The quote lines are generated from the cart lines, prefilled, and sales hits Send in 80% of cases.

The decision sheet

For each of your products, answer 3 questions:

• Can you describe the full offer on one page? If yes → a cart-only experiment is legitimate.
• Does the buyer need a pre-sales conversation to pick correctly? If yes → RFQ or hybrid.
• Is the average value > EUR 2,000? Then classic cart-only conversion is statistically too low — RFQ produces a better ROI.

Takeaway

Cart vs RFQ isn't an ideology. It's a measurement. For some product categories cart-only wins (fast, cheap, self-serve), for others RFQ wins (higher value, slower, sales-heavy). Most B2B catalogs need both, side by side, and the “cart-mode quote” hybrid is often the fastest-growing segment.