Explanation:

If the checkout process fails in the B2B store after adding the promotions subflow 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 currently configured to run a different Checkout flow template, which does not include the promotions subflow.

Explanation:

Scenario (📝)
When administrators clone Salesforce’s out-of-the-box Checkout Flow template, the new flow isn’t automatically active. Until it’s activated, it remains a draft and won’t be callable during checkout. Understanding flow lifecycle states (Draft, Activated, Deactivated) is key to ensuring customers interact with the correct flow during their buying journey.

✅ Correct Option: A. Activate the flow
After cloning and saving, the flow must be activated to become available. Only active flows can run within the storefront checkout process. Without activation, the system still relies on the old flow or produces errors if none is active, making this step essential.

❌ Incorrect Option: B. Add a version letter
Salesforce automatically versions flows when they’re saved. Administrators don’t manually add version letters; instead, Salesforce handles version numbering (e.g., Version 1, Version 2). Adding a letter doesn’t enable the flow for checkout.

❌ Incorrect Option: C. Change the permissions on the existing checkout flow
Permissions affect who can manage or edit flows, not whether they’re runnable. The cloned flow’s usability depends on activation, not permissions on the original template.

❌ Incorrect Option: D. Rename the existing Checkout Flow in place
Renaming the existing flow doesn’t deploy the cloned one. The cloned flow needs activation regardless of names. Renaming only helps for clarity in Admin setup, not functionality.

Reference:
Salesforce Help – Build a Flow

Explanation:

An Administrator is finalizing a Salesforce B2B Commerce storefront for deployment. Having assigned a catalog and buyer groups, they must complete remaining setup tasks within the Store setup wizard to ensure the store functions correctly. These tasks involve configuring critical components that govern pricing and transaction processes. The wizard guides Administrators through essential steps to make the storefront operational, ensuring buyers can browse, price, and complete purchases seamlessly.

Correct Options:

✅ B. Assign Price Books to a store:
Assigning Price Books in the Store setup wizard links product pricing to the storefront, enabling accurate display of prices for buyer groups. This step is mandatory to ensure buyers see correct, account-specific pricing during their shopping experience. Without Price Books, the store cannot process transactions effectively, making this a critical setup task.

✔️ E. Configure checkout flow:
Configuring the checkout flow in the Store setup wizard defines the steps buyers follow to complete purchases, such as adding payment and shipping details. This ensures a smooth, customized checkout experience tailored to business needs. It’s a required step to make the storefront fully functional for order processing.

Incorrect Options:

❌ A. Load tax rates:
While tax rates are important for accurate order calculations, they are not configured within the Store setup wizard. Tax rates are typically managed in separate tax configuration settings or integrations, not as a mandatory wizard step, making this option incorrect for store deployment.

🚫 C. Load shipping costs:
Shipping costs are configured outside the Store setup wizard, often through shipping integrations or settings in Salesforce B2B Commerce. While necessary for order fulfillment, this task isn’t part of the wizard’s mandatory steps, rendering it incorrect for this context.

🛑 D. Build the search index:
Building the search index enhances product discoverability but is not a required step in the Store setup wizard. It’s a post-setup task performed to optimize search functionality, not a prerequisite for store deployment, making this option unsuitable.

Reference:
Salesforce B2B Commerce Store Setup
Salesforce B2B Commerce Price Books
Salesforce B2B Commerce Checkout Flow

Explanation:

To configure the checkout time-to-live in Salesforce B2B Commerce, an Administrator shouldD. 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.

Explanation: If a language is deleted from Experience Builder,C. The content is no longer visible but is not deleted. This means that while the content associated with that language will not be displayed in the Experience Builder or the storefront, it remains in the system. This allows for the possibility of re-adding the language at a later time and restoring the visibility of the content without having to recreate it.