Explanation

Administrators configure checkout flows through the Commerce App's store-level settings. The Store tile in the Commerce App provides centralized access to checkout flow configuration, allowing administrators to select, customize, or create alternative checkout processes that define the steps buyers follow from cart to order completion.

✅ Correct Options

C. Store tile in the Commerce app
The Store tile in the Commerce App is the central location for configuring checkout flows. Administrators access store settings here to select pre-built checkout flows or configure custom flows. This interface allows you to define checkout steps, payment options, and order confirmation processes, providing complete control over the purchasing journey.

❌ Incorrect Options

A. Checkout Button on the Cart page
The Checkout Button on the Cart page is a user interface element that initiates the checkout process, not a configuration tool. This button triggers the configured checkout flow but doesn't provide administrative access to modify or create alternative checkout flows. It's a front-end component for shoppers, not an admin configuration point.

B. Experience Builder on the Checkout page
Experience Builder allows page layout customization and component arrangement on checkout pages, but it doesn't configure the underlying checkout flow logic. While you can modify page appearance and component placement, the actual checkout process steps, validations, and business logic are controlled through the Commerce App Store settings.

D. Process Builder Button in Experience Builder
Process Builder is a Salesforce automation tool for creating record-triggered processes, not for configuring checkout flows in B2B Commerce. Experience Builder doesn't contain a Process Builder button, and Process Builder isn't used to define commerce checkout sequences or steps within the storefront purchasing experience.

📌 Summary
Configure alternative or new checkout flows through the Store tile in the Commerce App. This central location provides access to checkout flow settings, allowing administrators to customize the complete purchasing process.

🔗 Reference
Salesforce B2B Commerce - Checkout Configuration

Explanation

Lightning Experience checkout in B2B Commerce requires enabling Orders as the foundational object for capturing purchases and Optional Price Books for Orders to support dynamic B2B pricing models. These org preferences activate the order lifecycle and price flexibility essential for multi-buyer scenarios. Without them, checkout fails to process store orders or apply buyer-specific pricing from assigned price books.

✅ Correct Option: B. Enable Optional Price Books for Orders
Enabling Optional Price Books allows Orders to reference multiple price books beyond the standard one, crucial for B2B where buyers use different pricing via buyer groups. During Lightning checkout, the cart dynamically pulls prices from the buyer's assigned price book. This supports complex pricing without manual overrides. ​

✅ Correct Option: D. Enable Orders
Enabling Orders activates the Order object and related functionality required for B2B checkout flows. Lightning Experience checkout creates Order records with Sales Store field populated, linking to the storefront. This preference is mandatory as B2B Commerce relies on Orders for cart conversion, payment processing, and fulfillment. ​

❌ Incorrect Option: A. Enable Account Relationships
Account Relationships support account hierarchies or parent-child linkages but aren't required for B2B Lightning checkout. Basic buyer accounts with approval and group assignment suffice for checkout without relationship mapping, which serves advanced scenarios like account switching. ​

❌ Incorrect Option: C. Enable Negative Quantity
Negative quantities enable returns or adjustments on Order Product records but aren't prerequisites for checkout. Positive quantity ordering works standard during purchase flows. This setting applies post-checkout for inventory corrections, not initial order creation. ​

Summary
Enable Orders for object activation and Optional Price Books for B2B pricing during Lightning checkout. Account relationships and negative quantities support advanced features but don't gate basic checkout. Set these in Setup > Order Settings for seamless store purchasing. ​

Reference
Salesforce Help: B2B Commerce on Lightning Experience Enhanced Checkout ​
Salesforce Help: B2B Commerce Permission Sets

Explanation

Correct Options:

✅ B. Experience Sites
Experience Sites, built via Experience Cloud, must be configured in Digital Experiences setup to host the B2B Commerce storefront. This includes creating or linking the site, setting up pages, themes, and membership—enabling both internal previews (e.g., for admins) and external access (for buyers). Without this, the store can't be accessed or published for users.

✅ D. Profiles and Permission Sets
Profiles and permission sets are configured in Setup > Users to control access for internal (e.g., Commerce Business User profile) and external users (e.g., Buyer or Buyer Manager permission sets). This ensures proper object permissions, community membership, and feature access like viewing products or placing orders—critical for activating the experience safely.

✅ E. Salesforce CMS
Salesforce CMS is set up outside the Commerce app in the CMS workspace to create, manage, and deliver content (e.g., images, banners) to the storefront. Assigning CMS channels and workspaces to the store is required for enhanced LWR sites and full content functionality, supporting personalized experiences for internal testing and external buyers.

Incorrect Options:

❌ A. Custom attributes
Custom attributes on objects like Products or Accounts can enhance personalization (e.g., for filtering), but they're optional and often configured in Object Manager or within Commerce app settings. They're not a prerequisite for deploying or activating the core B2B Commerce experience for users.

❌ C. Multi-Factor Authentication
MFA is configured in Setup > Identity for added security on logins, especially for external Experience Cloud users. While recommended, it's not mandatory to deploy or activate the storefront—basic functionality works without it, though production orgs may enforce it org-wide.

Summary
The three essential configurations outside the Commerce app are Experience Sites (for the storefront platform), Profiles and Permission Sets (for user access controls), and Salesforce CMS (for content management). These enable a complete, accessible B2B Commerce experience for internal and external users. My initial inclusion of MFA was incorrect—it's optional; CMS is the key third aspect.

Reference:
Salesforce Help: "Get Started with Salesforce Commerce" (covers prerequisites like sites, profiles, CMS)
Salesforce Help: "Configure Internal Users for Commerce" (profiles/permissions)

Explanation

Migrating B2B Commerce store configuration is a two-part process. The metadata (structure, pages) and certain data (catalog assignments) require different deployment methods aligned with standard Salesforce release management.

✅ A. Add the Store Configuration to a change set.
The store's metadata, including its definition, page templates, and components, is deployed using change sets. This is the standard method for moving configuration metadata from sandbox to production.

✅ D. Export the store configuration from the Store Administration.
Within the Commerce setup, you can export the store's configuration bundle (e.g., catalog assignments, price book links) as a file. This file is then imported into the target production org to complete the data-side migration.

❌ B. Import the settings to the Production environment with Workbench.
While Workbench is a data tool, the specific store configuration import is handled via the native Commerce administration interface, not a generic API tool. The official process uses the dedicated export/import feature.

❌ C. Export the store settings with Data Loader.
Data Loader is for standard and custom object records. The interconnected store configuration is packaged as a specialized bundle, not as discrete records easily handled by Data Loader. The dedicated export feature is designed for this purpose.

Summary:
Deploy store metadata with a Change Set and store-specific configuration data using the Export/Import feature in Store Administration. This two-pronged approach covers all necessary elements.

Reference:
Salesforce Help: Migrate Store Configuration

Explanation

Activity Tracking in Salesforce B2B Commerce relies on Commerce Einstein to collect, store, and analyze buyer interactions in the storefront. Enabling Commerce Einstein allows tracking of product views, searches, clicks, and purchases, which can then be used for personalization, recommendations, and reporting. Without Commerce Einstein, Activity Tracking features are not available out-of-the-box.

🟢 Correct Option

🟢 B. Deploy Commerce Einstein
Commerce Einstein is the native Salesforce tool for tracking buyer activity on B2B Commerce storefronts. Once deployed, it automatically captures page visits, product interactions, searches, and order behavior. This data is critical for building insights, generating recommendations, and powering analytics dashboards. No additional manual tracking setup is required beyond enabling Commerce Einstein.

🔴 Incorrect Options

🔴 A. Set a Cookie for Tracking
While cookies may be involved behind the scenes for session management, manually setting a cookie is not a required or supported step for enabling Activity Tracking in B2B Commerce. Tracking is handled by Commerce Einstein, not through custom cookie configuration.

🔴 C. Configure Time to Live with Experience Builder
TTL configuration in Experience Builder controls caching and session durations for site components, not buyer activity tracking. Adjusting TTL does not enable Activity Tracking or record user interactions in the storefront.

🔴 D. Leverage Google Analytics
Google Analytics can provide external tracking and reporting, but it does not integrate with Salesforce Activity Tracking or Commerce Einstein functionality. Google Analytics is optional and external, while Activity Tracking requires Commerce Einstein for Salesforce-native insights.

Summary
To enable Activity Tracking in a B2B Commerce storefront, the Administrator must deploy Commerce Einstein. Other options like cookies, TTL settings, or Google Analytics are not required to activate native Salesforce tracking and analytics.

Reference
Salesforce B2B Commerce Administration Guide – Enable Commerce Einstein
Salesforce Help: Track Buyer Activity in B2B Commerce