Skip to main content

#B2B Commerce15 人がディスカッション中

Hi Everyone,

I have created variation products in Salesforce Commerce Cloud and configured the Product Attribute Set. I have also configured the Price Book and Entitlement Policy.

However, my variation products are not appearing on the storefront under the assigned category. I have also updated the search index, but the products are still not visible.

Could someone please help me identify what configuration I might be missing and how to troubleshoot this issue?

Thank you! 

 

#B2B Commerce Cloud  #B2B Commerce  #B2b Commerce Storefront

3 件の回答
  1. 昨日、9:58

    Hi @Pooja Wable

     

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

    parent and variants are set up, not because of a single missing switch. I haven’t seen your org, so treat this as a checklist in rough order of likelihood. 

    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

    ProductAttribute

    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.

0/9000

Hello, 

 

We are looking for Technical documents, HLD and Features available OOTB in all of the below platforms by Salesforce- 

Salesforce B2B Commerce Ligtning. 

Salesforce OMS & OCI 

Salesforce B2C commerce (Demandware).+ Storefront Next 

 

I know there are various help articles but we are looking for consolidated version in form a presentation or document will help. 

 

#B2C Commerce  #B2B Commerce

2 件の回答
  1. 10月12日 14:10

    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.

0/9000

is there any possibility to translate the complete contact record based on user's language in salesforce b2b commerce? 

We have a B2B store where we have given option to choose language to end users so that the site can translated to requested language. The change of the language is also happens on user's language field too.  

Now we want to translation happens to end user's contact record as well. 

 

#B2B Commerce  #B2B Commerce Cloud  #B2B Commerce Lightning  #B2b Commerce Storefront

3 件の回答
  1. 10月5日 10:26

    Hi @padmini panigrahi

     

     

    Yes, this is possible, but not automatically through the standard B2B Commerce language/translation configuration.

    The language selected by the user controls the storefront/UI and supported Commerce translations. It does not automatically translate the existing values stored on a Salesforce Contact record.

    For Contact field values, you would need a custom solution. For example:

    User Language → Identify Contact → Translate required field values → Display translated values

    This could be implemented using Flow/Apex + a translation service/API, or by maintaining language-specific values in custom fields/records if the number of languages is limited.

    So, if the requirement is specifically “the same Contact record should display its field values in the user's selected language”, I would recommend a custom translation layer rather than Translation Workbench alone.

    Hope this clarifies!

0/9000

*** Important Update: Associate a B2C Commerce instance to your Managed Runtime production environment(s) by Sep 29, 2026 ****** Important Update: Associate a B2C Commerce instance to your Managed Runtime production environment(s) by Sep 29, 2026 ***Salesforce is limiting how Managed Runtime (MRT) determines production enviSalesforce is limiting how Managed Runtime (MRT) determines production environments. Currently, you can set any environment to production, regardless of whether it’s connected to an instance. This creates a lot of traffic, which harms the accuracy of monitoring and incident response for everyone on the platform.

 

To reduce traffic and improve capabilities, Salesforce is limiting which environments can be flagged as production. Starting September 29, 2026, an environment can be flagged as production only if it’s associated with a Staging or Production B2C Commerce instance.

 

Log Center logs and Log Center metrics aren't affected by this change. Both stay independently configurable on any environment, regardless of instance tier.

 

To keep production monitoring and related features on these environments, associate each one with a Staging or Production B2C Commerce instance before September 29, 2026.

 

  1. Open Runtime Admin and go to the Environment Settings for the environments listed above.
  2. Associate the environment with a Staging or Production B2C Commerce instance.
  3. Confirm the production flag is still on after you save the association.
  4. Redeploy the current bundle in that environment. This ensures the change takes effect immediately rather than waiting for your next scheduled deployment.

If you don't associate an instance by the deadline, you will lose production monitoring. Your Log Center logs and Log Center metrics settings won't change.

 

Need help?

Contact Salesforce Customer Support if you have questions about which instance to associate.

 

#B2C Commerce #B2B Commerce

2 件のコメント
0/9000

anyone looking for a managed service offering for their B2B Commerce Cloud implementation? 

7 件の回答
  1. 9月22日 9:48

    We have a team with solid B2B Commerce Cloud development experience and are looking to expand into managed support services. We’d be interested in connecting with partners who have experience structuring and taking these kinds of offerings to market.

0/9000
1 件の回答
  1. 9月8日 16:21

    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.

0/9000

We're working on several new bi-directional Salesforce OMS / OCI integrations with Shopify, eBay, Walmart, Magento, BigCommerce, Amazon Seller Central, and Amazon Buy with Prime. If anyone is interested in collaborating on this, please let me know!  My email is jon@1440.io 

3 件の回答
  1. 8月13日 17:28

    This sounds like an interesting project, especially with the need for reliable bi-directional syncing across multiple marketplaces. I’d be interested to hear how you’re handling inventory, order status, and fulfillment synchronization between Salesforce OMS and each platform.

0/9000

TIA!  We just installed Salesforce payments so that our field techs can take credit card payments from the customer. In the payments app, it says everything is ok.  We have had a case open since Jan 27 and it has not been solved yet. 

Any ideas? 

When are in the work order and hit Take a Payment, we get this error message: 

 test 1. "amount":119,"currencyIsoCode":"USD","paymentMethod":"TAP_TO_PAY","merchantName":"Gulf Coast Window Cleaning of Sarasota, LLC - Stripe","merchantAccountId":"8zbR700000000ODIAY","payerAccountId":"001R7000008wuzhIAA","sourceObjectIds":["0WOR70000065pb7OAA"]}handleTakePayment: Failed to fetch PaymentGatewayId for the provided MerchantAccountId. The operation couldn’t be completed. (SalesforceSDKCore.RestClientError error 0.)

2 件の回答
  1. 7月28日 8:19

    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.

0/9000

Hi,

I'm wiring up webhooks for a Commerce Payments integration with Authorize.Net. The notify endpoint Salesforce gives me is:

 

/services/data/vNN.0/commerce/payments/notify?provider=<paymentGatewayProviderId>

The ?provider= is what routes the notification to my custom PaymentGatewayProvider. Problem: Authorize.Net's webhook config rejects any URL with a query string, so I can't register this URL as-is in their merchant interface. The value isn't a secret - it's just routing.

Questions:

  • Can the notify endpoint resolve the provider without the query param (path-based, header, or otherwise)?
  • If not, what's the recommended pattern for gateways like Authorize.Net whose webhook config won't accept query strings?

Thanks! 

 

 

 

#B2B Commerce

1 件の回答
  1. 6月12日 15:44

    Hey @Lili Stoyanova

     

    No, Salesforce can’t resolve the provider without that provider query param. It’s required to route the webhook to the correct PaymentGatewayProvider, and there’s no supported alternative like path or header. 

     

    Since Authorize.Net doesn’t accept query strings, you won’t be able to use the Salesforce notify URL directly. 

     

    Best practice here is to put a small middleware in between. Authorize.Net will call your clean endpoint (without query params), and then your middleware forwards the request to Salesforce by adding the ?provider=... internally.

    You can do this with MuleSoft, AWS Lambda, Azure Function, or even a simple custom API. 

     

    So basically, Salesforce side can’t change this behavior, the fix has to be on the integration layer. 

     

    Hope this works!

0/9000

Hi everyone,

I’m trying to add a product to an existing Order Summary in Salesforce Order Management using the Add Order Item Summary Flow action, but I keep getting a generic error with no useful detail.

Here’s what I already verified:

  • The Order Summary already exists for the order.
  • I can see an existing OrderItemSummary on the same order.
  • I’m passing:
    • OrderSummaryId
    • OrderDeliveryGroupSummaryId
    • Product2Id
    • PricebookEntryId
    • Quantity
    • UnitPrice
    • TotalLineAmount
    • Reason
    • Type

The values I’m using are valid picklist/API values in my org, and the flow interview shows the payload being built correctly, but the action still fails with:

I also checked that the order is not being blocked by the summary creation process, and I’m working on a test order with existing Order Summary data.

Has anyone successfully used Add Order Item Summary

in Flow? 

Are there any hidden prerequisites, special field requirements, or order status constraints that could cause this generic failure?

Any advice or examples would be really appreciated.

Thanks!

1 件の回答
0/9000