PranavNagrecha/AwesomeSalesforceSkills / skills/admin/b2b-vs-b2c-requirements
b2b-vs-b2c-requirements
VerifiedUse this skill to determine whether a Salesforce Commerce project should use B2B Commerce (account-gated, BuyerGroup-based, contract pricing) or D2C Commerce (consumer storefront, guest checkout, individual-based). Trigger keywords: B2B vs B2C, commerce platform selection, buyer journey, account-based purchasing, consumer storefront, licensing decision. NOT for implementation mechanics — use admin/b2b-commerce-store-setup or admin/b2c-commerce-store-setup for configuration work. NOT for Salesforce B2C Commerce (SFCC/Business Manager) setup.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.9 KB |
| references/examples.md | markdown | 5.1 KB |
| references/gotchas.md | markdown | 6.8 KB |
| references/llm-anti-patterns.md | markdown | 7.1 KB |
| references/well-architected.md | markdown | 5.5 KB |
| scripts/check_b2b_vs_b2c_requirements.pyexecutable | script | 6.3 KB |
| templates/b2b-vs-b2c-requirements-template.md | markdown | 3.3 KB |
templates/b2b-vs-b2c-requirements-template.md
View on GitHub# B2B vs D2C Commerce Requirements — Work Template
Use this template when working on a Salesforce Commerce platform selection decision before any storefront implementation begins.
## Scope
**Skill:** `b2b-vs-b2c-requirements`
**Request summary:** (fill in what the client or user asked for)
---
## 1. Buyer Persona
| Question | Answer |
|---|---|
| Are buyers business entities (Accounts) or individual consumers? | |
| Do multiple contacts within the same organization share a cart or order history? | |
| Are orders placed on behalf of an Account, or by individuals acting independently? | |
| Are order approval workflows or spending limits required at the account level? | |
**Conclusion:** [ ] Business Account buyer (→ B2B Commerce) [ ] Individual consumer (→ D2C Commerce) [ ] Both (→ B2B2C hybrid)
---
## 2. Guest Checkout Requirements
| Question | Answer |
|---|---|
| Is anonymous browsing (no login required) needed? | |
| Is guest checkout (purchase without account creation) a firm requirement? | |
| What is the org's Salesforce release version? (Must be Winter '24+ for B2B guest checkout) | |
**Conclusion:** [ ] Guest checkout required [ ] Guest checkout not required
---
## 3. Pricing and Catalog Segmentation
| Question | Answer |
|---|---|
| Is pricing negotiated per account or account tier (contract pricing)? | |
| Do different buyers need to see different product catalogs? | |
| Is pricing uniform across all buyers (or segment-based without per-account negotiation)? | |
**Conclusion:** [ ] Account-gated pricing/catalog (→ B2B Commerce) [ ] Uniform/segment pricing (→ D2C Commerce)
---
## 4. License Verification
| License | Active in Org? | Notes |
|---|---|---|
| B2B Commerce | [ ] Yes / [ ] No | Check Installed Packages or WebStore creation dialog |
| D2C Commerce | [ ] Yes / [ ] No | Check Installed Packages or WebStore creation dialog |
**License gap (if any):** (describe any licenses that need to be procured before implementation begins)
---
## 5. Platform Decision
**Recommended platform:**
[ ] B2B Commerce — because: (fill in rationale)
[ ] D2C Commerce — because: (fill in rationale)
[ ] B2B2C Hybrid (two WebStores) — because: (fill in rationale)
**Unmet requirements requiring custom development:** (list any requirements that cannot be satisfied natively by the selected platform)
---
## 6. Follow-On Skills
After this decision is finalized, activate the appropriate implementation skill:
| Next Step | Skill |
|---|---|
| B2B Commerce storefront implementation | admin/b2b-commerce-store-setup |
| Salesforce B2C Commerce (SFCC) setup | admin/b2c-commerce-store-setup |
| Product catalog configuration | admin/commerce-product-catalog |
| Pricing and promotions setup | admin/commerce-pricing-and-promotions |
---
## 7. Review Checklist
- [ ] Buyer persona documented (Account-based vs. individual consumer)
- [ ] Guest checkout requirement confirmed or ruled out
- [ ] Pricing model documented (negotiated/contract vs. uniform)
- [ ] Catalog segmentation needs documented
- [ ] Active licenses verified in org
- [ ] Platform decision recorded with rationale
- [ ] Unmet requirements flagged
- [ ] Follow-on implementation skill identified
---
## Notes
(Record any deviations from the standard decision process, ambiguous requirements, or open questions.)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |