Skip to main content
Featured group

* Salesforce Commerce for B2B & D2C *

Welcome! This group is dedicated to your success with Salesforce Commerce (B2B and D2C, built on Core). Join the conversation here to stay up to date on the product, learn best practices, and everything in between. Use this group to review resources, ask questions, help each other, and share experiences. --------------------------------------- This group is maintained and moderated by Salesforce employees. The content received in this group falls under the official Forward-Looking Statement: http://investor.salesforce.com/about-us/investor/forward-looking-statements/default.aspx

In the enhanced LWR site, the input fields are displayed much larger than expected. However, the same components work correctly in our older B2B Commerce LWR site that was developed a few years ago. Has anyone encountered this issue before, or is there any known change in the enhanced LWR framework that affects input field sizing?  

Thank you.  

@Tom Zarr

 

Enhanced LWR UI Issue: Large Input Fields

 

image.png

 

image.png

 

@* Salesforce Commerce for B2B & D2C *

 

 

#B2C Commerce

1 answer
0/9000

Hii Salesforce Community,. 

 

1. I need a complete, step-by-step guide for integrating Salesforce Payments with Salesforce Order Management (OMS). 

 

Please explain the entire implementation process, including: 

 

  • How to configure and integrate Salesforce Payments with Salesforce OMS from scratch.
  • The prerequisites, required licenses, and Salesforce features that must be enabled.
  • How to connect Salesforce Payments to OMS, including the objects, settings, and relationships involved.
  • The complete payment lifecycle, including Authorization, Capture, Void, and Refund.
  • How payment transactions are associated with Orders and Fulfillment Orders in OMS.
  • Whether payment capture is handled automatically by Salesforce OMS when an order is fulfilled, or whether custom automation (such as Flows, Apex, Platform Events, or APIs) is required.
  • The standard APIs, payment gateway adapters, and integration points involved in the process.
  • A complete end-to-end implementation example, from checkout through order creation, fulfillment, payment capture, cancellation, and refund.
  • Salesforce best practices, common implementation challenges, and recommended architecture for a production environment.

 

2. How does payment capture work in Salesforce Order Management (OMS) when an order reaches the Fulfilled status? 

 

  • I would like a complete, step-by-step explanation of the end-to-end payment capture process, including:

 

  • Whether Salesforce OMS automatically captures an authorized payment when an order is fulfilled, or if custom automation is required.

 

  • The complete implementation flow from payment authorization through order fulfillment to payment capture.

 

  • Which standard Salesforce OMS components, payment gateway integrations, and APIs are involved in the capture process.

 

  • If automation is required, please explain how to implement it using Flows, Apex, Platform Events, or other recommended approaches.

 

  • Include a practical example with the order lifecycle, payment transaction states, and best practices for production implementations.

 

@* Commerce Salesforce Order Management *@* Salesforce Commerce for B2B & D2C *@* B2C Commerce *

3 answers
  1. Yesterday, 10:41 AM

    Hi @Robert Musk

    Salesforce Payments is available for sandbox environment or Salesforce payments only available in product environmen only, but how to test the salesforce payments in sanbox regarding payment capture, refunding , payment failures? can we able to cpature the authorized payment in stripe test account  

     

    do you have any documentation about configuring and setuping the salesforce payment for stripe in sandbox ? 

     

0/9000

In the enhanced LWR site, the input fields are displayed much larger than expected. However, the same components work correctly in our older B2B Commerce LWR site that was developed a few years ago. Has anyone encountered this issue before, or is there any known change in the enhanced LWR framework that affects input field sizing?  

Thank you.  

@Tom Zarr

  

@* B2C Commerce * @* Salesforce Commerce for B2B & D2C *

Enhanced LWR Input Field Size Issue

 

image.png

 

image.png

  

#B2B Commerce

0/9000

Hi Everyone,

I’m looking for some guidance from anyone who has implemented a similar product recommendation use case.

Here’s the scenario:

  • We have historical Sales Orders containing Products + Value Added Products (VAPs).
  • Currently, this history resides in Snowflake, although I’m also considering a scenario where the complete sales interaction history resides in Salesforce.
  • The goal is to provide intelligent product recommendations during the sales process (for example, complementary products, commonly purchased together, next best product, etc.).

I’m intentionally keeping the question open because I’m interested in understanding how others have approached this problem rather than focusing on a specific Salesforce feature or product.

Some questions I have:

  • If your sales history is already in Salesforce, how did you model the recommendation solution?
  • Did you use Salesforce-native capabilities, Data Cloud, custom Apex/LWC logic, external ML services, or another approach?
  • If your interaction history resides outside Salesforce (Snowflake, data warehouse, etc.), did you build recommendations there or bring the data into Salesforce?
  • What kind of interaction data proved most valuable (orders, quotes, opportunities, views, carts, etc.)?
  • Were there any lessons learned around data preparation, model quality, or keeping recommendations relevant?

I’d really appreciate hearing from anyone who has implemented a similar B2B product recommendation solution, regardless of the technology stack used.

Thanks in advance!

 

@* Salesforce Commerce for B2B & D2C * 

2 answers
0/9000

Hi everyone,

I'm currently focusing on learning Experience Cloud and its development aspects (Experience Builder, external users, portals, Enhanced Messaging, etc.), and I've run into a challenge with managing Salesforce orgs.

I'm not referring to Trailhead Playgrounds, since they often have limited licenses or don't always include the features I need.

Here's what I've experienced so far:

  • I created a Developer Edition org for general learning, but later realized that Developer Edition doesn't support Sandboxes, so I couldn't keep a clean development environment.
  • While learning Enhanced Messaging for Guest Users, I found that it requires a Developer Edition org with Enhanced Messaging enabled, so I had to create another org specifically for that.
  • In some orgs, after experimenting with Experience Cloud users, licenses, and configurations, I eventually hit license limits or ended up with an org that's no longer clean for new experiments, which led me to create yet another Developer Edition org.

At this point, I have multiple Developer Edition orgs, each created for a different feature or learning scenario, and it feels difficult to manage.

My questions are:

  1. Is this the normal workflow for Salesforce developers who are learning Experience Cloud?
  2. Is there a better way to maintain a reusable development environment without creating a new Developer Edition org every time?
  3. Are there any recommended strategies, tools, or org types that make this process easier?

I'd really appreciate hearing how others handle this while learning or building portfolio projects.

Thanks in advance!

5 answers
  1. Eric Burté (DEVOTEAM) Forum Ambassador
    Jun 26, 5:03 PM

    Hello @Somya Jain, I use 2 or 3 dev editions, no more. 

    Make the username / name relevant enough to be able what its usage is about. 

    If you want to store work / projects that you have built in a dev edition, think about pushing the configuration (metadata and code) on a GitHub repository. 

    Eric

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 answer
0/9000

The Agentic Enterprise is here, and now you have the roadmap to build it.  

 

Introducing Trailhead Journeys! 🎉 

 

Move from fundamentals to advanced expertise with guided, step-by-step learning across Salesforce products. 

 

No guessing where to start.

No wondering what’s next. 

 

Now available for:

📺 Join us on LinkedIn Live on June 2 @ 9:30 a.m. PDT

Our experts will share the 'why' behind this innovation and guide you through the Data 360 Trailhead Journey as a live example of how to scale your expertise. 🚀

 

[Save Your Spot] 🔔

The Agentic Enterprise is here, and now you have the roadmap to build it.

 

#Trailhead  #Salesforce Admin  #Salesforce Developer  #Salesforce  #New Releases  #Trailblazer

Hello community: I wanted to ask how you handle B2B. We currently have MCE and need to send emails to B2B CRM accounts. Can we email the account itself, or is it mandatory to email the account contact?   Thanks!    @* Salesforce Commerce for B2B & D2C * 

1 answer
0/9000

Hi All,

We’re evaluating whether a client can discontinue the following licenses:

  • B2B Commerce Internal Users – Unlimited Edition
  • B2B Commerce Orders – Growth – LP

and retain only:

  • Customer Community Plus – Members

Key questions:

  1. Can B2B Commerce storefront (Aura template) and features like Buyer Groups, Entitlements, and Product Categories still work? What is the minimum license required?
  2. Any impact on Product visibility, Price Books?
  3. Will cart/checkout and order placement still function?
  4. Any impact on CMS-hosted product images?
  5. Can we still create and manage portal users normally?

We also noticed that with Identity license + Commerce Admin permission set, B2B objects are visible—does this mean functionality is supported or just limited access?

Appreciate any insights or real-world experiences.

Thanks!

1 answer
  1. May 2, 10:33 PM

    @Aarya red

    No. I would not assume B2B Commerce can keep working fully with only Customer Community Plus Members. 

     

    Some key pointers:

    • Customer Community Plus is an Experience Cloud user license, mainly for external buyer access. It is not the same as the B2B Commerce product/order entitlement. 
    • Salesforce’s B2B Commerce persona guidance shows buyers using Customer Community Plus with B2B Commerce User / Flow User, and buyer managers using Customer Community Plus with B2B Commerce Super User and delegated admin permissions. It also shows merchandisers needing the B2B and D2C Commerce license for commerce management work. 
    • Buyer objects such as Carts, Categories, Images, Price Books, Products, Product Media, Stores, Orders, and Order Summaries require the right object/field access, but permissions alone do not replace commerce licensing. 
    • The B2B Commerce Orders - Growth - LP SKU suggests order-based commerce entitlement. If removed, cart/checkout/order placement may be commercially or technically unsupported, even if some objects remain visible. Public Salesforce pricing references list this as a separate Commerce Cloud order SKU. 
    • Seeing B2B objects with an Identity license + Commerce Admin permission set only proves object visibility or permission access. It does not prove the user/org is licensed to run B2B Commerce functionality. 

     

    Your concerns:

    • Storefront / Buyer Groups / Entitlements / Product Categories: likely require active B2B Commerce entitlement, not only CC+. 
    • Product visibility / Price Books: may be visible with permissions, but storefront behavior depends on Commerce setup and licensing. 
    • Cart / Checkout / Order placement: highest risk if B2B Commerce Orders license is removed. 
    • CMS product images: may still exist, but storefront rendering/use depends on the commerce site remaining licensed and functional. 
    • Portal users: yes, you can still create CC+ users, but that does not mean they can transact in B2B Commerce.

    Check these few links for reference:

0/9000