Checkout failures from store integration and payment setup
Key Takeaway
B2B stores use custom checkout, which doesn't set up every service for you. Add the native shipping service so zone rates appear, don't offer express payment options when Omnichannel Inventory is integrated, and handle PlaceOrderFailed exceptions with the Process Exception object and the Retrigger Place Order flow.
Checkout in a B2B store depends on several connected services: payments, tax, shipping, and sometimes inventory and Order Management. If one service is missing, set up wrong, or in conflict with another, buyers can't finish checkout. In some cases, their orders fail after they submit. To fix a checkout problem that blocks launch, an administrator checks each service and how the services work together.
Why B2B checkout needs manual setup
B2B stores can only use custom checkout. Managed checkout brings in Salesforce merchant services and automatic updates to the checkout UI, but managed checkout doesn't support customizations.
With custom checkout, you choose how to handle payments, tax, and shipping. You can use Salesforce's native merchant services, extend them, or replace them with third-party apps. You design the checkout page in Experience Builder.
Custom checkout doesn't set up every service for you. You must add the native shipping service to the store manually. You must also enable saved payment methods manually. So when checkout breaks before launch, first look for a service that was never added or turned on.