Salesforce Certified B2B Commerce Administrator Practice Test - Questions Answers, Page 18

A cart item with a type of charge is a special type of cart item that represents a fee or a discount applied to the cart or a cart delivery group. A cart item with a type of charge has the following characteristics:

It is created with the Cart Delivery Group Method after the freight integration: The freight integration is responsible for calculating the shipping costs for each cart delivery group based on the shipping method, the destination, and the weight and dimensions of the items. The freight integration can create a cart item with a type of charge to represent the shipping cost for each cart delivery group.

It is linked directly to a Cart Id: A cart item with a type of charge can be associated with a cart id, which means that it applies to the entire cart. For example, a cart-level discount or a tax charge can be represented by a cart item with a type of charge linked to a cart id.

B and D are not accurate statements because:

A cart item with a type of charge is not linked directly to a catalog id. A catalog id is used to identify a product or a variant in the catalog. A cart item with a type of charge does not represent a product or a variant, but rather a fee or a discount.

A cart item with a type of charge is not created with the Cart Delivery Group Method after the shipping integration. The shipping integration is responsible for determining the available shipping methods for each cart delivery group based on the origin, the destination, and the inventory availability. The shipping integration does not create any cart items with a type of charge.

To override the shipping charge calculation logic in B2B Commerce for Visualforce, a developer must implement the sfdc_checkout.CartShippingCharges interface. This interface defines two methods: calculateShipping and calculateShippingForCart. The calculateShipping method takes a CC Cart Delivery Group Method record as an input and returns a CC Cart Item record of type Shipping. The calculateShippingForCart method takes a CC Cart record as an input and returns a list of CC Cart Item records of type Shipping. These methods are invoked by the B2B Commerce for Visualforce framework during checkout to calculate the shipping charge for each cart delivery group and the entire cart respectively.Reference:Add a Shipping Service,Calculate Shipping at Checkout, B2B Commerce for Visualforce Developer Guide

To indicate that inventory is available for all items and amounts in the cart, the developer must return sfdc.checkout.IntegrationStatus.Status.SUCCESS from the inventory class. This is a predefined constant that represents a successful inventory check result. If the inventory class returns any other value, such as sfdc.checkout.IntegrationStatus.Status.FAILURE or sfdc.checkout.IntegrationStatus.Status.PARTIAL, the checkout process will be blocked or modified accordingly.Reference:Create an Inventory Class,Check Inventory at Checkout, B2B Commerce for Visualforce Developer Guide

There are two ways to configure taxes in B2B Commerce: using the Salesforce out-of-the-box tax solution or using a third-party tax engine. The Salesforce out-of-the-box tax solution allows the developer to configure tax rates and rules for each state in the B2B Commerce administration. The developer can specify the percentage at which a product is taxed and the country, state, or province where that rate applies.The developer can also map the tax rate to products using tax treatments and create a tax policy that includes all the tax treatments for the store's products1. Alternatively, the developer can configure a tax engine using third-party software, such as Avalara or Vertex. The developer can create an Apex class that implements the sfdc.commerce.CheckoutTaxCalculations interface and register it as the integration in the store administration.The Apex class can call the external service to calculate the tax amount for each cart delivery group and the entire cart2.Reference:Configure Tax Settings for a Store,Add a Tax Calculation Service.

To implement the use of a third-party service for either tax, shipping, or pricing calculation in a B2B Commerce store, the developer must complete three tasks: create an Apex class implementing the appropriate interface, create a named credential for authentication with an external service, and register an Apex class as the integration in the store administration.The Apex class must implement one of the following interfaces depending on the type of calculation: sfdc.commerce.CheckoutTaxCalculations for tax, sfdc_checkout.CartShippingCharges for shipping, or sfdc.commerce.CheckoutPriceCalculations for pricing3.The named credential must provide the URL, authentication protocol, and credentials for accessing the external service4.The Apex class must be registered as the integration in the store administration by selecting it from the drop-down list in the corresponding section5. Creating a flow or an invocable method is not necessary for this task.

When a developer configures a tax integration for a store, the previously calculated tax entries during the checkout flow are deleted from the cart. This is because the tax calculation logic is executed every time the cart is updated or recalculated, and the old tax entries are no longer valid.The new tax integration calculates the tax amount for each cart delivery group and the entire cart, and creates new cart item records of type Tax with the updated values1.Reference:Add a Tax Calculation Service

The error code INSUFFICIENT_ACCESS_OR_READONLY indicates that the storefront user does not have access to the Cart Delivery Method object, which is used to store the selected shipping method for each cart delivery group. This error can occur when the developer configures a shipping cost calculation integration that requires access to this object, but does not grant the appropriate permissions to the storefront user profile or permission set.To resolve this error, the developer must ensure that the storefront user has at least read and edit access to the Cart Delivery Method object and its fields2.Reference:Specify Shipping Group Options for LLI Checkout,Specify Shipping Options for Standard Checkout,CartDeliveryGroupMethod

To debug a flow that has created a defect, the developer should open the flow, select Debug, provide the Input values, and select Run. This option allows the developer to test the flow with real or simulated data points and see how the flow behaves in each step. The developer can also use breakpoints to pause the flow execution and inspect the variable values at any point.The developer can compare the expected and actual outcomes of the flow and identify the source of the defect1.Reference:Debug a Flow in Flow Builder

In checkout, the developer's code should listen for CommerceErrorEvents to help troubleshoot and respond to actions. CommerceErrorEvents are events that are fired when an error occurs during checkout, such as an invalid input, a failed integration call, or a system exception. The developer can use these events to handle the errors gracefully and display appropriate messages to the user.The developer can also use these events to log the errors for further analysis or debugging2.Reference:B2B Commerce Checkout Flow Core Actions