Book Image

Salesforce B2C Solution Architect's Handbook

By : Mike King
Book Image

Salesforce B2C Solution Architect's Handbook

By: Mike King

Overview of this book

There’s a huge demand on the market for Salesforce professionals who can create a single view of the customer across the Salesforce Customer 360 platform and leverage data into actionable insights. With Salesforce B2C Solution Architect's Handbook, you’ll gain a deeper understanding of the integration options and products that help you deliver value for organizations. While this book will help you prepare for the B2C Solution Architect exam, its true value lies in setting you up for success afterwards. The first few chapters will help you develop a solid understanding of the capabilities of each component in the Customer 360 ecosystem, their data models, and governance. As you progress, you'll explore the role of a B2C solution architect in planning critical requirements and implementation sequences to avoid costly reworks and unnecessary delays. You’ll learn about the available options for integrating products with the Salesforce ecosystem and demonstrate best practices for data modeling across Salesforce products and beyond. Once you’ve mastered the core knowledge, you'll also learn about tools, techniques, and certification scenarios in preparation for the B2C Solution Architect exam. By the end of this book, you’ll have the skills to design scalable, secure, and future-proof solutions supporting critical business demands.
Table of Contents (20 chapters)
1
Section 1 Customer 360 Component Products
7
Section 2 Architecture of Customer 360 Solutions
13
Section 3 Salesforce-Certified B2C Solution Architect

Chapter 3

  1. SFRA provides the fastest time to value and is mobile-optimized. Reasons for choosing a headless experience (custom or PWA kit) include increased flexibility and the de-coupling of responsibilities, but not implementation time.
  2. Service Cloud for the CSR functionality, and an order management solution for order modification requirements. B2C Commerce is not a system of record for orders. Order modifications should be performed in a downstream system such as Salesforce Order Management.
  3. Service agents could be making changes directly in Production, which is not the system of record for content, and those changes are getting wiped out by the scheduled nightly replication from Staging.
  4. Storefront changes can be supported by modifying the SFRA code base, but Commerce APIs do not allow for custom code extensions; only the Open Commerce API (OCAPI) allows for that, so additional work will be required in a middleware layer between the mobile app and B2C Commerce...