Salesforce Decode
Salesforcedecode
Back to questions
Headless 360Architect (Hardest)b2brevenue-cloudcpqheadless

Design headless B2B quote configuration with Salesforce Revenue Cloud APIs

Real World Scenario

Industrial distributor replaces legacy CPQ UI with custom React buyer portal requiring complex bundle configuration, contracted pricing, and approval workflows.

Expected Answer

• Use Revenue Cloud / CPQ APIs for product catalog, price rules, and quote line configuration server-side • Never trust client-side price calculation—validate totals on server before quote submit • Model buyer account hierarchy and entitlement contracts in API context for price resolution • Expose configuration state as REST resources enabling save-resume across sessions • Integrate approval workflow webhooks notifying buyers of status in portal UI • Handle large BOM configurations with pagination and async pricing jobs for heavy bundles • Version quote API contracts coordinating with ERP order export integrations

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Main difference: use case and scale. Use Revenue Cloud / CPQ APIs for product catalog, price rules, and quote line configuration server-side. Never trust client-side price calculation—validate totals on server before quote submit. Pick based on your integration pattern and team capability. B2B headless CPQ is server-authoritative pricing—React is presentation; Revenue Cloud APIs own configuration truth. Document the decision in an ADR and align with enterprise standards.

Architect Perspective

B2B headless CPQ is server-authoritative pricing—React is presentation; Revenue Cloud APIs own configuration truth.