Salesforce Certified B2C Commerce
DeveloperB2C Commerce Cloud LATEST
EDITION 2024/25 GUARANTEED GRADE A+
Business Manager
Configure storefronts in real time. Categorize, price, search,
display, navigate, and promote merchandise.
Control Center
Gives your IT staff operational control over your site, such as
starting instances, and managing users.
UX Studio
Install on your local machine. Modify site presentation and business
logic, such as payment processors, and shopping carts.
Account Manager
Lets your IT staff create user accounts on B2C Commerce, grant and
revoke user access to B2C Commerce instances.
Tools Support
Use XChange to enter support tickets, visit user forums, and
participate in the Commerce Cloud community.
A customer realm
includes a primary instance group and a secondary instance group,
both of which have tools that you can use to configure your ecommerce
sites.
Staging instance
used for site configuration, data enrichment, and data import.
Development instance
used to test your site before deployment.
Production instance
hosts the live site that is used by customers.
Primary Instance Group
The primary instance group has three instances, which merchants use
to add data, test code, and run live sites. A realm can have only one
PIG per realm.
Secondary Instance Group
The secondary instance group (SIG) contains your sandbox instances.
The minimum number of sandboxes in a SIG is 3, and the maximum is 47.
Commerce Cloud
The Commerce Cloud is the underlying resources used to run your
instances and live site that are managed by Salesforce. You never
interact directly with the cloud, but it is the foundation that
supports your site.
Instance Types
,Sandbox, Staging, Development, and Production
Developer
Instance Type: Sandbox, Staging
Developer Responsibilities
A developer creates or modifies templates, pipelines, and scripts on
a local machine and uploads them to a Sandbox instance to test.
Ultimately, the developer is responsible for uploading code to the
Staging instance. The developer can also export data added by
merchandisers on the Staging instance to use as test data for the
sandboxes.
Merchandiser
Instance Type: Staging
Merchandiser Responsibilities
A merchandiser or online marketer is usually responsible for creating
campaigns and promotions, managing product information, and
configuring search behavior.
Administrator
Instance Type: All instances
Administrator Responsibilities
An admin is responsible for granting access to instances and
functionality on instances. The admin restarts instances, manages
data feeds, and uploads certificates.
Quality Assurance Engineer
Instance Type: Development
Quality Assurance Engineer Responsibilities
This role is responsible for testing the site in conditions as close
to production as possible. No code development is done on the
Development instance.
Commerce Cloud provides two reference applications
SFRA (Storefront Reference Architecture)
SGJC (SiteGenesis JavaScript Controllers)
Key SFRA Benefits
Mobile first design: Recent industry trends makes it clear that a
greater percentage of shoppers are making purchases directly from
mobile phones and tablets instead of from laptops or desktops. SFRA
was therefore designed from a Mobile-First perspective, optimizing
the experience of mobile shoppers.
Extensibility: SFRA was designed with extensibility in mind, allowing
merchant developers to implement storefronts by adding a
customization layer on top of the core reference application code,
without having to modify the core. SGJC, in contrast, requires
merchants to directly modify the core reference application code.
Import and Export
,Feeds data from external systems into B2C Commerce, such as product,
pricing, and inventory information. You also Import and Export to
move data from one instance type to another.
Create XML feed files that conform to B2C Commerce schemas to import
data into B2C Commerce.
We recommend using the scheduled job feature to automate data import
and export. Developers, administrators, and merchants need to work
together to determine the frequency and schedule of import feeds.
Developers are responsible for implementing the cartridges. Admins
are responsible for creating the XML files containing data from the
systems of record for products, pricing, and other data. They are
also responsible for configuring the jobs needed to run the import.
Data is validated during import. If the import experiences too many
errors it can fail. To recover from a failed import, you must
successfully complete another import.
Data Replication/Code Replication
Securely moves data and code between instances. Replication is a one-
way process from Staging to either a Development or Production
instances. You can roll back from a replication to the previous
version of the instance.
Code Upload
Used to upload code from a developer's local machine via UX Studio to
a Sandbox or Staging instance. Developers are responsible for code
upload.
Catalog Feeds
Used to process .zip files from Certona. This feature is only for
additional information that is added to the catalog that isn't part
of the normal catalog import and export process.
Sites and Storefronts
In Salesforce B2C Commerce, a site is the application and associated
code that runs a storefront. A storefront the user's online
experience. A site can have multiple storefronts with different URLs
for different brands, locales (with currency and tax differences), or
multiple channels. If you are referring to a specific URL, B2C
Commerce uses the term storefront.
Site Architecture Scenarios
When designing your site, your architect must consider the following:
-The geographical relationship between storefronts and the teams that
maintain them
-Data that is shared between sites, such as product data, tax and
payment information, user roles and permissions, promotions, or
, application code
-Whether the storefront needs to be localized for different market
locales or restructured for them
-Data that must remain separately controlled due to corporate
structure or legal requirements
-Whether customer, basket, or transaction data carries over from one
storefront to the next
-Example: An apparel retailer lets customers shop simultaneously at
both their adult and children's sites. On the other hand, a retailer
with two very different customer bases, such as a book publisher for
religious books and fantasy fiction, can prevent crossover.
One Site, Multiple Storefronts
If you have many storefronts and a single team maintaining them, you
can manage them easier as a single site, even if the products are
different for each site. Similarly, if you want to share baskets
between storefronts, the storefronts must be part of a single site.
If you are deploying many localized sites with similar branding and
products, it's faster and easier to manage new storefronts as an
extension of an existing site.
Multiple Sites, Multiple Storefronts
You can have multiple sites, each of which supports multiple
storefronts. You can also choose to share site data, such as customer
data, between sites.
Business Manager
is the Salesforce B2C Commerce online tool for configuring and
managing B2C Commerce storefronts. This important tool is the command
center for your B2C Commerce merchandising, administration, and site
development capabilities.
Personas
-Merchandisers configure site data, such as products, images,
campaigns, promotions, and search settings.
-Administrators configure B2C Commerce site settings, import and
export site data, and roll out code and data changes.
-Developers use Business Manager to access the storefront application
directly to debug and troubleshoot problems, and configure
development-specific settings.
Create Version Directories
You can create version directories on your server instance via the
Business Manager if you have the appropriate permissions. When
developing your application in Studio, you can select which directory
to upload files. Using version directories lets you retain previous
versions while saving your changes to a specific server directory so
that you can retest the application against an older version.
