Skip to main content

#Commerce Cloud DEV101토론 중인 항목 4개

Pooja Wable 님이 #B2C Commerce에 질문했습니다

Hi Salesforce Community,

I am currently learning Salesforce Commerce Cloud and would like to understand the licensing requirements for B2C Commerce.

Could someone please clarify the following?

  1. Which licenses are required to create and manage a B2C Commerce storefront?
  2. Is a separate B2C Commerce license or subscription required?
  3. Can we develop and test a B2C Commerce storefront using a Developer Edition org, or do we need a separate B2C Commerce sandbox/realm?
  4. Which licenses are required for shoppers and internal users?
  5. Is there any trial or developer environment available for learning and practice?

Any guidance or documentation would be greatly appreciated.

Thank you!   

#B2C Commerce #B2C Sandbox #B2B Commerce #Commerce Cloud DEV101

답변 1개
  1. 10월 21일 오전 10:29

    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.

0/9000
답변 1개
  1. 9월 8일 오후 4: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