#B2C Commerce15 personnes en discutent

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

Here's the current process for Salesforce B2C Commerce Partners regarding On-Demand Sandbox credits as of 2026:

Purchasing or Topping Up Credits

• Partners can typically purchase or request additional On-Demand Sandbox credits through their Salesforce Partner Manager or Account Executive. This may require a formal request or order.

What Happens When Credits Are Exhausted

• If your allocated credits are exhausted, your existing sandboxes will continue to run. Salesforce will automatically move your account into overage billing for any usage beyond your entitlement, so sandboxes are not immediately shut down.

How Overage Is Billed

• Overage is billed monthly based on contract terms and the number of sandboxes or usage hours beyond your allocation. The billing is charged to your partner account, and no immediate action is needed to keep sandboxes running, but it’s important to monitor your usage and billing statements.

Requesting Additional Credits

• You can request additional credits directly from your Partner Manager or Account Executive, who will guide you through the process.

Confirmation for 2026

• The process remains as described above, but always confirm with your Partner Manager or Account Executive for any recent updates or changes to contract terms.

For more details, review your latest partner agreement or connect with your Salesforce Partner Manager.

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.

Hello @Palak Bohra

Please find url:

Fill out the form to get free trial org of Commerce cloud. 

Thank you

Hi @Mayra Janeth Gómez de los Santos, in B2C Commerce you can include the price attribute as a standard attribute in your custom sorting rules (https://help.salesforce.com/s/articleView?id=cc.b2c_creating_sorting_rules.htm&type=5). The price attribute uses the information stored in your price books. So you could use a standard/base price book and a sales/promotional price book depending on how you create and structure your price books. Please note that promotional prices as a result of the promotion engine are not reflected in the sorting rules. Promotional prices based on our promotion engine are highly dynamic and are not considered in search to avoid performance impact.

@Giovanni Marchetto

, 

I don’t think a previous call is changing the POST to GET. This usually happens when the frontend code and controller route are not from the same SFRA version.

Since this started after upgrading from SFRA 6.0.0 to 6.2.0, I’d compare all ConsentTracking-related files, not just the controller.

Check these:

1. Search your cartridges for ConsentTracking-SetConsent, ConsentTracking-SetSession, and SetConsent.
2. See if your custom cartridge is overriding ConsentTracking.js or any consent popup JS/ISML.
3. Compare those files with the SFRA 6.2.0 version.
4. Clear cache and redeploy static assets.

Most likely, the browser is calling the newer GET-based consent endpoint, but your controller/custom override is still expecting POST. So it looks like a version mismatch rather than the method being overridden.