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

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.

If you're looking for a managed service for a B2B Commerce Cloud implementation

, I’d recommend choosing a provider that can handle ongoing support, integrations, performance improvements, and future enhancements not just the initial implementation. 

Providers such as Plumlogix can be worth considering alongside other Salesforce partners, especially if you need long-term Salesforce support and optimization. The key is to compare their B2B Commerce experience, integration capabilities, response times, and ongoing support model. Salesforce’s partner ecosystem also includes providers with dedicated B2B Commerce and managed-service competencies.

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.

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!

Hi, 

According to the documentation it seems that you're missing some attributes in the order item summary: name and type code. 

Hope that helps!