You're reading from Salesforce B2C Solution Architect's Handbook Design scalable and cohesive business-to-consumer experiences with Salesforce Customer 360

Product type Paperback

Published in Nov 2021

Publisher Packt

ISBN-13 9781801817035

Length 458 pages

Edition 1st Edition

Tools

Salesforce

Concepts

CRM

Author (1):

Mike King

Preface

1. Section 1 Customer 360 Component Products

2. Chapter 1: Demystifying Salesforce, Customer 360, and Digital 360 FREE CHAPTER

3. Chapter2: Supporting Your Customers with Service Cloud

4. Chapter 3: Direct-to-Consumer Selling with Commerce Cloud B2C

5. Chapter 4: Engaging Customers with Marketing Cloud

6. Chapter 5: Salesforce Ecosystem – Building a Complete Solution

7. Section 2 Architecture of Customer 360 Solutions

8. Chapter 6: Role of a Solution Architect

9. Chapter 7: Integration Architecture Options

10. Chapter 8: Creating a 360° View of the Customer

11. Chapter 9: Supporting Key Business Scenarios

12. Chapter 10: Enterprise Integration Strategies

13. Section 3 Salesforce-Certified B2C Solution Architect

14. Chapter 11: Exam Preparation Tools and Techniques

15. Chapter 12: Prerequisite Certifications

16. Chapter 13: Commerce and Integration

17. Chapter 14: Certification Scenarios

18. Assessments

19. Other Books You May Enjoy

Chapter 3

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.
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.
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.
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...

The rest of the chapter is locked