Salesforce Decode
Salesforcedecode
Back to questions
Headless 360Architect (Hardest)b2bpricingcontractsapi

Expose negotiated B2B contract pricing APIs to headless buyer portals

Real World Scenario

Manufacturing buyers see list price on headless portal instead of contract rates negotiated in Salesforce, causing checkout abandonment and manual quote rework.

Expected Answer

• Resolve buyer account and active contract entitlements in every pricing API request context • Use Revenue Cloud or custom price book APIs returning contract-specific price overlays • Never expose internal discount logic to client—return final authorized unit prices only • Validate contract effective dates and volume tiers on server with audit log • Handle multi-ship-to accounts with ship-to-specific contract assignments • Cache contract prices with short TTL invalidated on contract amendment events • Integration test matrix covering expired contracts, tier breaks, and promotional stack rules

Follow-Up Questions & Answers

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

Main difference: use case and scale. Resolve buyer account and active contract entitlements in every pricing API request context. Use Revenue Cloud or custom price book APIs returning contract-specific price overlays. Pick based on your integration pattern and team capability. B2B headless pricing failures are trust failures—contract context must be first-class in API auth session, not optional query param. Document the decision in an ADR and align with enterprise standards.

Architect Perspective

B2B headless pricing failures are trust failures—contract context must be first-class in API auth session, not optional query param.