* Salesforce Commerce for B2B & D2C *

Hi @Salvatore Pira

I would recommend checking the following points:

1. Make sure you are passing record variables to the Add Order Item Summary action rather than passing individual record IDs or existing records directly.
2. Verify that the Order Item Summary record variable includes all required fields, especially Name, Type, and TypeCode, along with the correct OrderSummaryId and OrderDeliveryGroupSummaryId.
3. Confirm that the Product2Id and PricebookEntryId correspond to the intended product and price book entry.
4. Check that the Reason value is valid and that the UnitPrice, Quantity, and TotalLineAmount values are consistent.
5. Verify that your user has the required permission to use the Add Order Item Summary action. Also, confirm that the order can accept the requested change under its current lifecycle status.
6. If the action still fails, check the Flow error details and debug logs to identify the underlying exception.

Salesforce documentation: 

I hope this helps! If you find this answer helpful, please select it as the Best Answer. 

Thanks, 

Deepak Sachdeva 

Nubys Tech. Pvt. Ltd. 

Main Checkout is not a separate package. It is included with Salesforce Commerce, and a store that already uses the B2B Legacy Checkout flow does not get that flow replaced in place. 1. In the Commerce app, open the store and go to Settings, then Checkout. 2. Clone the Salesforce checkout template for Main Checkout, or create a new flow from that template. Main Checkout does not use the old cart-session structure, so the legacy flow cannot be converted into it. 3. Activate the cloned flow and select it as this store's checkout flow. 4. Rebuild any custom steps from the legacy flow on the new one. Those steps do not carry over. If Main Checkout is not in the template list, reply with the Commerce release on the org. Older releases only expose the legacy checkout template.

The standard B2B LWR cart does not list every coupon. It has a coupon code field where the shopper types a code. Automatic promotions, the ones that do not need a code, show on the cart as applied adjustments when the cart qualifies. Coupon promotions apply only after the shopper enters the code. There is no standard component that prints all coupon codes on the cart. Codes are also limited by the promotion's buyer group or segment, so a list of every coupon in the org would include codes that shopper cannot use. To show a chosen set of codes, add a custom LWR component on the cart page and display only the coupons that promotion is meant to offer that buyer. Keep the standard coupon field so they can still type a code.

There is no standard CSV export of the product recommendations shown to one shopper. The order, product, and similar exports are catalog and transaction files. They do not include Einstein recommendation content. Einstein recommendation reporting for a Salesforce Commerce store is aggregated performance in the Einstein area of the store. It is not a customer-level file of what was displayed. Storefront activity tracking records shopper events such as product views and purchases so Einstein can build recommendations. That activity is not a log of the recommendation slots rendered for a specific customer, and it is not available as a native CSV of those recommendations. To keep the products recommended to a specific buyer, you would need to capture that response in the storefront yourself.

Switch Account keeps the shopper logged in only when the account they select is a buyer account they are allowed to use in this store. If that check fails, the LWR store drops the buyer context, sends them to the home page, and they appear as a guest. 1. On the contact, confirm a delegated account or other buyer relationship exists for the account they are switching to, and that account is enabled as a buyer. 2. That account must be in a buyer group entitled to this store. An account the user can see in CRM, but that is not a buyer for the store, will not hold the session. 3. In Experience Builder, the profile menu item must be the standard Switch Account action. A custom item that only links to Home does not set the effective account. 4. Confirm the buyer user has the store's buyer permission set, then retry the switch in a fresh session. If those are already in place and the shopper is still logged out, reply with whether the target account is a delegated account and whether it belongs to the store's buyer group.

Hi Alex, with the Winter ’24 LWR checkout changes, the custom component needs to be placed within the new Checkout Section and follow the interfaces supported by that checkout architecture. 

The CheckoutSavable behavior isn't something you implement by importing an interface into the LWC. The checkout framework invokes the supported public methods on the component when it participates in the checkout flow. 

I'd first verify that the component is using the current Commerce checkout component contract for the Winter ’24/LWR layout, because the older checkoutMode, reportValidity(), and checkoutSave() example may not apply to the new Accordion/Checkout Section architecture. 

If you're already following the current documentation and those methods still aren't being invoked, could you share the component configuration in Experience Builder and the exact Commerce/LWR version? That would help determine whether this is a configuration issue or a regression with the new checkout layout.