If the checkout process fails in the B2B store after adding the promotionssubflow to the checkout flow template, the two possible reasons could beA. A new version of the checkout flow template has not been activated, meaning the changes have not been applied; andB. The Checkout page on the Experience Builder site is currentlyconfigured to run a different Checkout flow template, which does not include the promotions subflow.

Store Migration is the B2B Commerce capability used to move a configured storefront between Salesforce environments. Salesforce documents the store-migration process for scenarios such as moving configuration from a sandbox to production. The administrator exports the store configuration, includes the required Store Configuration and Site.com metadata in a change set, deploys that change set to the target environment, and then applies the exported configuration. Store Publish is associated with making storefront changes available rather than transferring configuration between Salesforce orgs. Commerce Importer is intended for commerce data import scenarios, while Migration Toolkit is not the standard B2B Commerce feature identified for this operation. Therefore, Store Migration is the appropriate feature for deploying store configuration from one org to another.

================

To target CMS content at a particular store, an Administrator needs toB.Create CMS content and assign it in Experience Builder. This involves creating content within the CMS workspace and then using Experience Builder to place and assign this content to specific pages or components within the store, ensuring it appears in thedesired location.

To update product images for a large number of products, the Administrator should use:

B. Data Loader:This tool allows for the bulk updating of records in Salesforce, including product images. By preparing a CSV file with the updated image paths and using Data Loader, the Administrator can efficiently update the images for all relevant products across allstores in the org.

To set up Tiered Pricing fora product, an administrator needs to configureA. Price Adjustment Schedules. This functionality allows for the creation of pricing tiers that apply different discounts based on the quantity of items purchased, enabling volume-based pricing strategies.

Externally hosted product images must be permitted by Salesforce ' s Content Security Policy before the storefront can retrieve and display them. Salesforce instructs Administrators to register an external image host as a Trusted URL and enable the img-src CSP directive. Trusted URL definitions can also use an asterisk as a wildcard when multiple applicable subdomains must be covered. Therefore, if the imported image URLs are structurally correct but their host or subdomain is not included by the existing trusted-site configuration, adding the appropriate wildcard CSP Trusted Site resolves the resource-loading restriction. Activating the product does not authorize the browser to load content from an external domain, while disabling Lightning Locker or relaxing the entire CSP is unnecessary and creates broader security exposure.

To determine which price is shown to customers with multiple price booksassigned, an Administrator should useC. Pricing Strategies. Pricing Strategies in Salesforce B2B Commerce allow administrators to define rules and criteria for selecting the appropriate price book for a customer, ensuring that the correct prices are displayed based on the customer ' s attributes and the business ' s pricing policies.

By enabling Commerce in Setup, the object added to the data model isB. Store. The Store object is a fundamental component of Salesforce B2B Commerce, representing the digital storefront where products and services are offered to customers.It serves as the central entity around which various commerce functionalities are configured and managed.

To add additional languages to a B2B Commerce site, an Administrator must take the following three steps:B. Enable Translation Workbench, which is a tool for translating text and customizations into different languages;D. Enable Data Translation, which allows for the translation of data records; andE. Add the Supported Language field to the Store page layout, which specifies which languages are supported by the store.

Salesforce CMS separates content management from the destinations where that content is published. A CMS workspace is the shared repository in which content is created and maintained, while channels identify the endpoints that consume published content. Salesforce documentation explains that content published in a workspace becomes available to the channels associated with that workspace. For Commerce stores, each store can have its own public channel, and those store channels can be added to the same CMS workspace. This design allows the marketing team to maintain shared content once while distributing it independently to both storefronts. Creating separate workspaces would unnecessarily duplicate content administration, while using only one channel would not correctly represent two distinct store publishing endpoints. Therefore, one shared workspace with one channel per store is correct.

================