To configure the checkout time-to-live in S alesforce B2B Commerce, an Administrator should D. Update TTL properties in Order Settings under Setup . This involves accessing the Order Settings in the Salesforce Setup menu and adjusting the Time To Live (TTL) properties, such as CheckoutTimeToLive, to define the duration for which a checkout session remains active before expiring.

To meet the requirement that all orders over a certain amount be paid for using a credit card instead of a purchase order, the Administrator should start with B. Add decision logic to hide the option for purchase orders on orders that meet the cr iteria . This approach involves configuring the checkout flow to dynamically adjust the available payment options based on the order amount, ensuring compliance with the specified payment policy.

As part of the Store setup wizard, the remaining steps the Administrator must complete include:

B. Assign Price Books to a store: This ensures that the correct pricing is applied to products within the store.

E. Configure checkout flow: This involves setting up the steps and processes that customers will go through during checkout, including payment and shipping options.

Completing these steps ensures that the store is fully functional and ready for deployment, providing a seamless shopping experience for customers.

When moving a store from Sandbox to Production, the three components an Administrator needs to consider as part of the Ch ange Sets include B. 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; and E. Process Builder Flows , which automate bu siness 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 migrate Store configurations from a development sandbox to a QA sandbox, an Administrator should Use Data Migration (A) to transfer configuration data and related records between environments. Export Store Configuration (D) is also a crucial step as it allows the Administrator to crea te a deployable package of the store's settings, which can then be imported into the QA environment. Apply Store Configuration (B) and Publish the Store (C) are actions taken after the configurations have been successfully migrated and are part of the setu p process in the new environment, rather than the migration process itself.

To move the B2B store configuration from a sandbox to a pro duction environment, an Administrator should A. Add the Store Configuration to a change set and C. Export the store settings with Data Loader . The change set allows for the transfer of configuration settings, while the Data Loader can be used to migrate da ta related to the store setup, ensuring a smooth transition to the production environment.

The System Context with Sharing—Enforces Record-Level Access (D) is crucial to B2B Commerce because it ensures that users can only view products and related data that they are authorized to see, maintaining data security and privacy. This setting is particularly important for storefronts where products need to be displ ayed according to specific customer agreements, contracts, or profiles. It doesn't directly relate to checkout (A), content synchronization (B), or guest browsing (C), but rather to the fundamental aspect of product visibility and access control on the sto refront.

To set up different pricing for differen t groups of buyers, an Administrator should B. Create Price Books to define different pricing structures and D. Create Buyer Groups to segment buyers into groups. Price Books can then be assigned to specific Buyer Groups, allowing for differentiated pricin g strategies based on the buyer group.

An Administrator can directly access Experience Builder to make changes to a storefront from A. All Sites and D. Digital Experiences . These areas within Salesforce provide entry points to the Experience Builder, where administrators can modify the design and layout of storefronts, including components and pages.

If search filters are not visible on the Category Detail page when viewing the storefront in Spanish, it could be due to The picklist value's translations not being completed in Translation Workbench (C) . The Translation Workbench in 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 i ssue 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 visibi lity of search filters is directly tied to the completeness of translations in the Translation Workbench.