sfb2b-architect

Architect scalable Salesforce B2B Commerce storefronts with data modeling and integration patterns.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/Architect-And-Bot/sf-b2b-commerce-template --skill sfb2b-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sfb2b-architect
Source: https://github.com/Architect-And-Bot/sf-b2b-commerce-template/tree/main/.claude/skills/sfb2b-architect
Command: npx skills add https://github.com/Architect-And-Bot/sf-b2b-commerce-template --skill sfb2b-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical architecture guidance for Salesforce B2B Commerce platform covering data models, integration patterns, security, performance optimization, and architectural decisions for the storefront.

Core Features & Use Cases

  • Data modeling guidance for Product2 structures, Buyer Account hierarchies, entitlements, and pricebook strategies.
  • Standardized integration patterns for ERP, CPQ, middleware, and event-driven flows, enabling decoupled systems.
  • Comprehensive security model including permission sets, access controls, and object/field-level security alignment with entitlements.
  • Performance optimization techniques such as caching strategies, delta price sync, and scalable cart/checkout patterns.
  • Deployment and governance guidance for multi-channel B2B storefronts with repeatable architectures.

Quick Start

Describe your Salesforce B2B storefront requirements and generate a tailored architecture plan.

Frequently Asked Questions about sfb2b-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I model Buyer Account hierarchies and entitlements for Salesforce B2B Commerce?

Salesforce B2B Commerce data modeling requires structuring Buyer Account hierarchies and entitlements alongside Product2 and pricebook strategies. Architectural guidance delivers standardized design patterns for mapping complex buyer relationships and access controls into scalable storefront data models.

What are the best integration patterns for connecting ERP and CPQ to B2B Commerce?

B2B Commerce integration patterns connect ERP, CPQ, and middleware through event-driven flows and decoupled architectures. Architectural guidance provides standardized integration designs that enable synchronized data across external systems without tight coupling.

How does entitlement governance work with object and field-level security in B2B storefronts?

Entitlement governance in B2B storefronts aligns permission sets and access controls with object and field-level security. Architectural guidance maps entitlement models to Salesforce security structures ensuring buyers only access authorized products and pricing.

Can I use delta price sync and caching to optimize B2B Commerce performance?

Delta price sync and caching strategies optimize B2B Commerce performance by reducing synchronous price calculations and redundant data loads. Architectural guidance provides scalable cart and checkout patterns to maintain storefront responsiveness under high transaction volumes.

How do I architect multi-channel B2B storefront deployments with repeatable structures?

Multi-channel B2B storefront deployments require repeatable architectures covering data models, security, and integration patterns. Architectural guidance delivers governance frameworks and standardized structures enabling consistent deployment across diverse B2B commerce channels.

What limitations should I consider when scaling B2B Commerce cart and checkout patterns?

Scaling B2B Commerce cart and checkout patterns requires addressing entitlement complexity, ERP synchronization latency, and large catalog performance constraints. Architectural guidance identifies these limitations and provides decoupled integration designs to mitigate bottleneck risks.