The error code INSUFFICIENT_ACCESS_OR_READONLY is caused by the cart being no longer in a valid Checkout State during checkout flow customizations. A cart is an object that represents a collection of products and charges that a customer intends to purchase in the storefront. A cart has a Checkout State field that indicates the current state of the checkout process for the cart. The Checkout State can have values such as Draft, InProgress, Completed, or Cancelled. A cart can only be modified or updated when it is in Draft or InProgress state. A cart cannot be modified or upda ted when it is in Completed or Cancelled state. If an attempt is made to modify or update a cart that is in Completed or Cancelled state, an error with the code INSUFFICIENT_ACCESS_OR_READONLY will be thrown. This error means that the user does not have pe rmission to edit or delete a record because it is read-only or locked. The storefront user does not have access to the Cart Delivery Method object is not a cause of this error code, as it is not related to the cart checkout state or data modification. The Cart Delivery Method object is an object that stores information about the delivery method selected for a cart in the storefront. An error has occurred during the cart shipping charge integration is not a cause of this error code either, as it is not relat ed to the cart checkout state or data modification. The cart shipping charge integration is an integration that calculates and applies shipping charges to a cart based on various factors such as delivery method, location, weight, volume, etc. The storefron t user does not have access to custom fields on the Order Delivery Method object is not a cause of this error code either, as it is not related to the cart checkout state or data modification. The Order Delivery Method object is an object that stores infor mation about the delivery method selected for an order summary in the storefront. Salesforce References:  B2B Commerce Devel oper Guide: Cart Object , [B2B Commerce Developer Guide: Cart Delivery Method Object], [B2B Commerce Developer Guide: Order Delivery Method Object] , [Salesforce Help: Common Error Messages]

Two components in a B2B store template that a developer can use to customize a storefront page are My Lists and Product List. My Lists is a standard component that displays and manages lists of products that customers can create, save, or share in the storefront. A developer can use this component to enable customers to organize their favorite or frequently purchased products into lists and access them easily. Product List is a standard component that displays and filters products from one or more product lists in the storefront. A developer can use this component to showcase products from different categories or collections and allow customers to browse or search for products based on various criteria. Order List is not a component in a B2B store template, but rather an object that stores information about orders placed by customers in the storefront. Address List is not a component either, but rather an object that stores information about addresses associated with customers in the storefront. Salesforce References: [B2B Commerce Developer Guide: My Lists Component], [B2B Commerce Developer Guide: Product List Component] , [B2B Commerce Developer Guide: Order List Object], [B2B Commerce Developer Guide: Address List Object]

The event that is triggered within Salesforce B2B Commerce whenever a cart’s state changes is cartChange. This event is triggered by the updateCart method of the CCRZ.Cart class, which is responsible for updating the cart data and performing any actions that depend on the cart state, such as applying discounts, taxes, or shipping charges. The event can be used to notify all the components that are listening to it that the cart has changed a nd they should refresh their data accordingly. Salesforce References:  B2B Commerce and D2C Commerce Developer Guide ,  Events ,  Cart Class

The use of a standard Visualforce control such as apex:form is discour aged in Salesforce B2B Commerce page includes and subscriber pages because the CCRZ JavaScript object is not accessible within an apex:form control. The CCRZ JavaScript object is a global object that provides access to various B2B Commerce functions and pr operties, such as logging, utilities, events, and configuration. Using an apex:form control would prevent the developer from using the CCRZ JavaScript object and its features. Visualforce does not “scope” controls that are present on a page and scope of th e control will be set to “ccrz”, as this is not a valid statement. Apex:form does not render DOM components slowly, as this is not a performance issue. JavaScript events are supported within an apex:form control, as this is not a limitation. Salesforce Ref erences: B2B Commerce Developer Guide: CCRZ JavaScript Object, B2B Commerce Developer Guide: Page Includes

Two ways that a developer can deploy some small CSS changes without waiting for the entire project deployment are right-clicking the folder for the component and choosing Deploy Source to Org and right-clicking the CSS file that was edited and selecting Deploy Single File. Deploying source to org is a way of deploying metadata from a local project to an org using Salesforce CLI commands. The developer can use Visual Studio Code to execute these commands by right-clicking on files or folders in the project and choosing from various deployment options. Right-clicking the folder for the component and choosing Deploy Source to Org allows the developer to deploy only the files that belong to that component, such as HTML, JavaScript, CSS, and XML files. Right-clicking the CSS file that was edited and selecting Deploy Single File allows the developer to deploy only that CSS file and not any other files in the project. These options can save time and bandwidth for deploying small changes without affecting other components or files in the project. Modifying the StoreIntegratedService to map to an Apex class ID using Workbench is not a way of deploying CSS changes, as it is only used for registering internal services that are provided by Salesforce B2B Commerce out-of-the-box. Entering the integration class name and version in store administration is not a way of deploying CSS changes either, as it is only used for selecting an existing integration class that has already been registered as an external service. Salesforce References: Salesforce CLI Command Reference: force:source:deploy, Salesforce Developer Tools for Visual Studio Code, B2B Commerce Developer Guide: Integration Framework, B2B Commerce Developer Guide: RegisteredExternalService Object

The correct answer is  A and D .  To implement a business rule around shipping, the developer will need to create a class that implements the sfdc_commerce.CartShippingCharges interface and may need to contain logical branching to handle different scenarios 1 2 .  The sfdc_commerce.CartShippingCharges interface is a standard interface that defines the methods for calculating shipping charges for a cart 1 .  The developer can use this interface to override the default shipping logic and apply custom rules based on the cart amount or oth er factors 1 2 .  The developer may also need to use conditional statements or other logic to determine when to use freight shipping or standard shipping 3 .

The implementing class cannot call out to another service and a class will need to implement the sfdc_checkout.CartShippingCharges interface are not the correct answers.  The implementing class can call out to another service if needed, such as an external shipping service or a pricing engine 2 .  The sfdc_checkout.CartShippingCharges interface is a deprecated interface that was used for calculating shipping charges for a cart only 1 .  It has been replaced by the sfdc_commerce.CartShippingCharges interface, which supports both carts and orders 1 .  References:

B2B Commerce on Lightning Experience Developer Guide

B2B Commerce and D2C Commerce Developer Guide

Salesforce Accredited B2B Commerce Developer

sfdc_commerce.CartShippingCharges Interface

Integrate with Lightning B2B Commerce

Shipping Rules 101: Here’s What You Need to Know

A method to re solve if the current storefront customer is a Salesforce B2B Commerce guest user in an apex class is to use ccrz.cc_CallContext.isGuest. This property will return true if the current user is a guest user, or false otherwise. For example,  if(ccrz.cc_CallCon text.isGuest){ // do something for guest user }  will execute some logic only for guest users. Salesforce References:  B2B Co mmerce and D2C Commerce Developer Guide ,  Call Context

In Lightning Web Components, the decorators @api , @track , and @wire play crucial roles. The @api decorator is used to expose public properties and methods, making them accessible to other components. The @track decorator is used to mark private properties as reactive, so the UI updates when their values change. The @wire decorator is used to wire Apex methods or Salesforce data to the component. Salesforce documentation on LWC development extensively covers these decorators, explaining their usage and best practices.

 To implement the use of a third-party service for either tax, shipping, or pricing calculation in a B2B Commerce store, a developer must complete these three tasks:

Create an Apex class that implements the appropriate interface for the calculation type. For example, for tax calculation, the developer must implement the sfdc_checkout.CartTax interface and define the getTax method. This method takes a Cart object as an input parameter and returns a list of CartTax objects with the calculated tax amounts.

Create a named credential for authentication with the external service. A named credential specifies the URL of a callout endpoint and its required authentication parameters. The developer can use the named credential in the Apex class to make the callout to the external service and handle the response.

Register the Apex class as the integration in the store administration. The developer must specify the Apex class name in the corresponding field for the calculation type. For example, for tax calculation, the developer must enter the Apex class name in the Tax Calculation Integration field. This way, the store can invoke the Apex class to perform the calculation for each cart.

The other options are not valid tasks for implementing the use of a third-party service. Creating a flow to call the external service directly is not supported for B2B Commerce, and creating an Apex class with an invocable method is not required for the calculation integration.  References:

Integrate with External Services

CartTax Interface

Named Credentials

[Store Administration]

To have a Contact Us page in the storefront that is a web-to-lead form and has the same look and feel as all the pages in the application, the requirement can be fulfil led by creating a Subscriber Page (CC Page). This is a custom Visualforce page that can be added to the storefront and use the standard header and footer components. The page can also include a web-to-lead form that submits data to Salesforce as leads. Sal esforce References:  B2B Commerce and D2C Commerce Developer Guide ,  Subscriber Pages