Salesforce B2B Commerce uses Salesforce CMS workspaces to manage and associate product media with commerce stores. Salesforce specifically states that when images are imported globally for all stores through a CSV file, the import must identify a CMS workspace where those imported images are linked. If an appropriate CMS workspace does not already exist, the Administrator must create one before beginning the global image import. An external image host can hold the physical image files, but creating such a host is not the required prerequisite identified by the global import process. Likewise, Image Catalog and Media Catalog are not the required Salesforce CMS containers for this operation. Therefore, creating a CMS Workspace is the required step before performing the global image import.

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

For selling products without physical delivery, the minimum objects involved includeB. CartDelivery Charge Group,C. Cart Delivery Group, andE. Cart Delivery Group Method. These objects allow for the configuration of delivery options that do not involve physical shipping, such as digital delivery or services, by defining how delivery charges are applied and managed within the cart and order processes.

To enable external buyers to view products on the storefront, the objects that need to be set to " Public Read Only " access level areOrder Delivery Method (B),Catalog (C), andPrice Book (E). Order Delivery Method is crucial for buyers to understand shipping options; Catalog structures the product offerings and navigation; and Price Book holds the pricing details necessary for purchase decisions. Providing " Public Read Only " access to these objects ensures that external buyers can browse products, understand pricing, and comprehend delivery options without compromising other data ' s security or integrity. Accounts (A of a ProductCode is fundamental for the indexing processitself.

Salesforce Flow supports multiple execution contexts, and the default execution mode is User or System Context—Depends on How Flow Is Launched . In this mode, the flow does not force one universal security context; instead, the mechanism that launches the flow determines whether it executes in user or system context. Salesforce identifies this configuration as DefaultMode in Flow metadata. By comparison, System Context with Sharing explicitly enforces record-level sharing while bypassing some user permissions, and System Context Without Sharing provides broader data access. For a standard checkout flow configured to use the caller ' s appropriate runtime context, the default User or System Context setting is therefore the applicable selection.

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

When moving a store from Sandbox to Production, the three components an Administrator needs to consider as part of the Change Sets includeB. Store Configuration Component, which contains the store ' s setup and configuration settings;C. Custom Objects and Fields, which are used to extend the functionality and store custom data; andE. Process Builder Flows, which automate business processes within the store. These components are crucial for ensuring the store ' s functionality and customizations are retained when moving to the production environment.

To leverage an existing Salesforce Billing product implementation in their B2B Commerce storefront, an administrator shouldD. Create a custom Component in Experience Builder. This custom component can integrate Salesforce Billing functionality into the B2B Commerce storefront, allowing for seamless invoice and payment processing within the commerce experience.

An Administrator can configure an alternative or new checkout flow in theStore tile in the Commerce app (C). This area provides access to store configurations, including checkout process customizations. The Commerce app ' s Store tile allows administrators to define and manage various aspects of the checkout experience, such as payment options, order review, and final confirmation steps, ensuring a seamless and efficient checkout process for users. TheCheckout Button on the Cart page (A),Experience Builder on the Checkout page (B), andProcess Builder Button in Experience Builder (D)are not the primary locations for configuring the checkout flow in Salesforce B2B Commerce.

To modify the account or person account associated with the OrderSummary without Salesforce Order Management licenses, it ' s necessary thatC. The OrderLifeCycleType field on the associated OrderSummary is set to UNMANAGED, indicating thatthe order is not being managed by Salesforce Order Management, andD. The user executing this action has either the " Edit Unmanaged Order Summaries " or " B2B Commerce Integrator user " system permission, granting them the ability to make changes to unmanaged orders.

If search filters are not visible on the Category Detail page when viewing the storefront in Spanish, it could be due toThe picklist value ' s translations not being completed in Translation Workbench (C). The Translation Workbenchin Salesforce allows Administrators to provide translations for various UI elements, including picklist values used in search filters. If these translations are incomplete or missing, the filters may not display correctly in the specified language. This issue highlights the importance of comprehensive translation efforts to ensure a seamless multilingual user experience. Browser translation issues (A), site page variations (B), and untranslated category data (D) can also affect localization, but the visibility of search filters is directly tied to the completeness of translations in the Translation Workbench.

Valid options fora Price Adjustment Schedule include:

B. Percentage:This allows for discounts or price increases based on a percentage of the original price, providing flexibility in pricing strategies.

C. Range:This option enables the application of different price adjustments based on the quantity or total value of items, allowing for volume discounts or tiered pricing structures.