#B2B Commerce15 debatiendo

 Hi @padmini panigrahi

Yes, this is possible, but it requires a custom solution for translating Contact field values dynamically based on the user's selected language.

Salesforce B2B Commerce supports storefront translations, but changing the user's language does not automatically translate the existing values stored in Contact records.

You can consider the following approaches:

1. Use Salesforce Translation Workbench for supported field labels and picklist values.
2. For text field values, build a custom translation solution using Apex and an external translation API.
3. If you support a limited number of languages, maintain language-specific translations in custom fields or custom objects.
4. Use the user's selected language to display the appropriate translated values in your storefront without changing the original Contact record data.

Since you have many users across different regions and countries, I would recommend a custom translation layer that retrieves the appropriate translated values based on the user's selected language.

Official 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.

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. 

Good questions, because B2C Commerce works differently from the rest of Salesforce. 

It doesn't run inside a normal Salesforce org. It runs on its own platform (managed through Business Manager), so you can't build or test a B2C storefront in a Developer Edition org, and it isn't a license you add to Sales or Service Cloud. A company buys a B2C Commerce subscription and gets a realm with its environments, and developers usually work in on-demand sandboxes created inside that realm. 

Shoppers don't need any license. Pricing is normally tied to the sales that go through the storefront rather than per shopper. Internal users (merchandisers, developers, admins) get access to Business Manager through Account Manager, set up by whoever administers the realm. 

For learning on your own, start with the B2C Commerce trails on Trailhead. For hands-on sandbox access, the usual routes are through an employer that already has a realm or through a Salesforce partner company, since there isn't a free self-service B2C realm the way there is a free Developer Edition org. If your goal is to learn commerce in general, B2B Commerce and Commerce on Core do run in normal orgs, so they're easier to practice with.

Hi @Pooja Wable

Variation products almost always go missing on a B2B Commerce (Lightning) store because of how the

Check in this order 

1. Category goes on the parent, not the variants. Assign only the Variation Parent to the category (Catalog → Category → Products). Variants shouldn’t be categorized, and the storefront shows the parent tile with attribute selectors. Also confirm that category’s catalog is assigned to your store (StoreCatalog).
2. Parent and variant setup.
   • Parent: Product Class = Variation Parent, IsActive = true, and the Attribute Set is assigned to the parent.
   • Variants: each has a ProductAttribute record pointing to the parent (VariantParentId) with values for every attribute in the set. A missing or blank attribute value can silently drop the variant.
3. Entitlement covers parent and variants. This is the most common miss. The policy must include the parent and every variant, be active, and be assigned to a Buyer Group. That Buyer Group must be assigned to the store, and the buyer’s account must be a member of it.
4. Pricing on the variants. Each variant needs an active PricebookEntry in a price book assigned to the store and Buyer Group. The parent doesn’t need a price, but variants without one won’t display or purchase correctly.
5. Search index. Run a full rebuild, not just an incremental update, and wait for it to finish. Changes to category assignment or entitlement often need the rebuild to appear.
6. Publish and test as the right user. If your store is LWR, publish the site after changes. Test as an actual buyer in the entitled account (not as an admin or guest), since guest users need their own Buyer Group and entitlement.

 Quick diagnostic queries  

-- Parent is active, has the right class, and is categorized
SELECT Id, Name, IsActive, ProductClass FROM Product2 WHERE Name = '<parent>'
SELECT ProductId, ProductCategoryId FROM ProductCategoryProduct WHERE ProductId = '<parentId>'
-- Variants are linked to the parent
SELECT Id, ProductId, VariantParentId FROM ProductAttribute WHERE VariantParentId = '<parentId>'
-- Entitlement covers parent AND variants
SELECT PolicyId, ProductId FROM CommerceEntitlementProduct WHERE ProductId IN ('<parentId>', '<variantIds>')
-- Variants are priced
SELECT Product2Id, Pricebook2Id, IsActive FROM PricebookEntry WHERE Product2Id IN ('<variantIds>')

If the parent appears in the query results but not on the storefront, the problem is almost always entitlement or the index. If the parent shows but variants don’t, look at the

records and variant pricing.   

I hope you find the above information helpful. If it does, please mark it as Best Answer to help others too.

Hi @Ayaan Saini,

Salesforce does not publish one single combined document for all these products. The best approach is to collect the official pieces below and put them into your own deck or HLD. Here is where to find each part.

1. B2C Commerce (Demandware) + Storefront Next

• Main hub: the Commerce section on developer.salesforce.com/docs/commerce. It has guides for B2C Commerce APIs (SCAPI, OCAPI, Script API), Storefront Next, Composable Storefront (PWA Kit), and SFRA.
• Choose Your B2C Commerce Storefront Type compares SFRA, Composable Storefront and Storefront Next. This page is very useful for an HLD decision.
• Storefront Next Architecture explains the full request flow: shopper → Managed Runtime (server-side rendering) → SCAPI → B2C Commerce backend, plus Einstein and the Salesforce Platform.
• Build and Customize Storefront Next lists the OOTB features, such as Page Designer, checkout, passwordless login, social login, store locator and pickup, and hybrid storefronts.
• For the OOTB business features (catalog, promotions, Business Manager, etc.), use the Salesforce Help B2C Commerce documentation, and check the B2C Commerce Release Notes for the latest additions.

2. B2B Commerce on Lightning

• Use the Salesforce Help “B2B Commerce and D2C Commerce” documentation and the Commerce developer guides.
• Check the Lightning-based commerce guide for the OOTB feature list: buyer groups, entitlements, price books, carts and checkout, orders, and Experience Cloud storefront templates.
• Also read the Commerce Developer Guide for the Connect REST APIs, Apex extension points, and the checkout flow.

3. Salesforce OMS and OCI

• Use the Salesforce Help “Order Management” and “Omnichannel Inventory” guides. They cover order lifecycle, fulfillment orders, routing, returns, inventory availability, and reservations.
• Check the Order Management developer guide for the data model and APIs.

4. Consolidated or architecture-level material

• Salesforce Architects (architect.salesforce.com) has reference architectures, decision guides, and diagrams. These are the closest thing to a ready HLD.
• Trailhead has trails and modules for B2C Commerce, B2B Commerce, and Order Management. They are good for a feature overview.
• Release notes for each product, since feature lists change every release.

5. For a ready-made presentation or feature matrix

• Ask your Salesforce Account Executive or Solution Engineer. They can share official pre-sales decks, capability matrices, and product roadmaps that are not publicly available.
• If your company is a Salesforce partner, check the Partner Community for enablement material.

A practical tip: build one short document with a section per product (purpose, key OOTB features, architecture, integration points, and when to use it). Linking each section to the official page keeps it easy to update.

Hope this helps! If it does, please mark it as the best answer.

Hi Sreemanth — this one is almost always the sharing-settings step on the Inventory objects rather than a problem with your Commerce licenses. Things to try, in order: 

1) Set up the Inventory sharing manually instead of using Retry. Click the "Set up manually" link on the Inventory row, then go to Setup → Sharing Settings → Organization-Wide Defaults → Edit. Set Default Internal Access for Location and Location Group

to Public Read/Write, keep "Grant Access Using Hierarchies" checked, and Save. Sharing recalculation runs asynchronously, so wait for the confirmation email before going back to the assistant. 

2) Don't hit Retry while a sharing recalculation is still running.

If the assistant tries to change org-wide defaults while another recalculation is in flight, the step fails with exactly that generic "We couldn't set up all of the features" message. Wait until it finishes, then Retry so it can continue to steps 4–6. 

3) Check Setup → Deferred Sharing Maintenance and Setup → Background Jobs.

If deferred sharing calculation is suspended in the org, the assistant can't update org-wide defaults at all. 

4) Confirm the Inventory objects are actually provisioned.

Location and Location Group come with Inventory Management / Omnichannel Inventory, and a plain new Developer Edition org isn't always fully provisioned for Commerce. If those objects are missing, spinning up a Commerce-enabled trial org (B2B/B2C Commerce trial signup or Environment Hub) is the fastest route. 

5) Check the running user's permissions.

Make sure whoever runs the assistant has the Commerce Admin permission set plus Modify All Data / Manage Sharing. 

Once Inventory sharing is set manually, the assistant should treat the step as complete and let you finish the rest. If it still sticks at 3 of 6 after recalculation completes, check the Setup Audit Trail around the failure timestamp and raise a support case — the generic message doesn't tell you which object failed, but Support can see it. 

Hope that helps.

Hi @Frank Sweeney

We've seen a few payment implementations where the Merchant Account configuration looked correct, but the gateway mapping or environment specific setup caused similar behavior. 

Which payment gateway are you using? It would help narrow down whether this is a configuration issue or a platform limitation.