Salesforce B2B Commerce: Pricing, Checkout, Payments

Salesforce B2B Commerce is a cloud-based digital commerce platform that lets businesses sell to other businesses through a branded online storefront, with built-in tools for managing complex pricing, multi-step checkout, and diverse payment methods. It is part of the Salesforce Customer 360 ecosystem and is designed to handle the unique needs of B2B transactions, such as negotiated contracts, volume discounts, and purchase orders. This article explains how buyers, pricing, checkout, and payments actually work within Salesforce B2B Commerce, including configuration options, common challenges, and how it compares to other B2B ecommerce platforms.

Background: What Is Salesforce B2B Commerce?

Salesforce B2B Commerce (formerly known as Salesforce Commerce Cloud B2B, and before that, CloudCraze) is a headless, API-first commerce solution built natively on the Salesforce platform. It is often used by manufacturers, distributors, and wholesalers who already use Salesforce for CRM, sales, or service. The platform provides a storefront that can be customized with Lightning Web Components, and it integrates directly with Salesforce data, so customer records, pricing rules, and order history are all shared.

Unlike B2C commerce (where a consumer buys a single item at a fixed price), B2B commerce involves multiple buyers per account, negotiated price books, credit limits, and complex approval workflows. Salesforce B2B Commerce addresses these with features like account-based pricing, quote-to-order integration, and support for multiple payment terms.

How Buyers and Accounts Are Structured

In B2B Commerce, the buyer is not just an individual; they are a user associated with an account (the company). Each account can have multiple users with different roles and permissions. For example, a purchasing manager might see prices and place orders, while an accounts payable user might only view invoices and payment history.

Buyers log in through a self-service portal or are authenticated via Salesforce Communities (now called Experience Cloud). The platform supports:

• Account hierarchies – Parent and child accounts, so a large enterprise can have subsidiaries with separate buying rules.
• User roles – Custom permissions for viewing prices, submitting orders, or approving purchases.
• Buyer groups – Assign different catalogs, price books, and payment terms to different groups within an account.

This structure means that pricing and checkout are not one-size-fits-all; they are dynamically determined by the logged-in user’s account and role.

Pricing: How It Works in Detail

Pricing in Salesforce B2B Commerce is driven by Salesforce’s standard price books, which are essentially lists of products with associated prices. But for B2B, you need more than a single list price. The platform supports:

• Price books – Multiple price books can exist, and a buyer sees the one assigned to their account or buyer group.
• Price adjustments – You can apply discounts based on quantity, contract terms, or promotional rules.
• Contract pricing – Specific negotiated prices for a customer, often set up in the associated CRM opportunity or contract object.
• Cost and margin calculations – For sellers, the platform can show cost, margin, and profit at the line-item level.

When a buyer adds an item to the cart, the system calculates the price using the following logic (simplified):

1. Find the price book entry for the user’s account.
2. Apply any price adjustments (e.g., quantity discount tiers).
3. Apply any contract-specific prices if they exist.
4. Apply taxes and shipping charges at checkout.

One common misconception is that Salesforce B2B Commerce natively supports complex pricing like “tiered by total order value” out of the box. It does not fully; you often need to use Price Rules (which are part of Salesforce’s catalog and pricing engine) or custom Apex code to achieve advanced logic. For example, a rule like “10% off when order total exceeds $5,000” can be built with Price Rules, but it requires configuration.

Checkout: Steps and Configurations

The checkout process in Salesforce B2B Commerce is fully customizable, but the default flow includes several steps that are typical for B2B:

1. Cart review – Buyer sees line items, quantities, and prices.
2. Shipping address – Often multiple addresses are allowed, and each line item can ship to a different location.
3. Shipping method – Real-time carrier rates can be integrated, or flat rates can be set.
4. Payment method – Choose from credit card, purchase order, or invoicing.
5. Review and submit – Final summary, then order submission.

Key B2B features during checkout include:

• Approval workflows – If an order exceeds a certain amount, it may require a manager’s approval before submission.
• Quote integration – A buyer can convert a sales quote into a cart, ensuring prices match the negotiated quote.
• Order templates – Reorder frequently purchased items quickly.

Checkout can be configured to be a single page or multi-step, and you can add custom fields (e.g., PO number) or custom validation. The platform also supports guest checkout, but it is rarely used in B2B because pricing and payment terms are tied to the account.

Payments: What Is Supported and How It Works

Salesforce B2B Commerce does not process payments itself; it integrates with payment gateways and processors. The most common setup is to use a payment gateway like Stripe, Adyen, or CyberSource, which are available as managed packages or via custom integration. The platform supports:

• Credit card payments – Authorized and captured at checkout or at order fulfillment.
• Purchase orders (PO) – The buyer enters a PO number, and the seller invoices them later.
• Terms (Net 30, Net 60) – Typically handled outside the platform, but the order record can store the terms.
• Tokenization – Card details are stored securely by the gateway, not in Salesforce.

For PO and terms payments, the platform does not automatically sync with an ERP like SAP or NetSuite; you need middleware or a custom integration to send invoices and payment status. This is a common pain point for companies that expect full financial automation.

Another important aspect is that payment capture can be deferred until fulfillment. For example, if you ship partial orders, you can capture only the shipped amount. This requires the payment gateway to support multiple captures, and the integration must be configured accordingly.

Common Problems and Misconceptions

Several issues frequently arise when implementing or using Salesforce B2B Commerce:

• Complex pricing is not fully native – As mentioned, advanced pricing rules often require Apex or additional apps.
• Performance with large catalogs – If you have millions of SKUs, the default search and browse may be slow; you may need Salesforce Search or a third-party search tool.
• Integration with ERP is not built-in – You need to connect to your ERP for inventory, pricing, and order management.
• Checkout customization is code-heavy – While the platform is flexible, significant changes to the checkout flow require Lightning Web Components and Apex development.

A common misconception is that Salesforce B2B Commerce is a “plug-and-play” solution. In reality, it is a platform that requires configuration and development to meet specific business needs. The total cost of ownership can be high, especially for complex implementations.

How to Choose Between B2B Commerce and Other Options

Salesforce B2B Commerce is not the only option. Here is a brief comparison:

• Salesforce B2B Commerce vs. B2C Commerce (CloudCraze vs. Demandware) – B2C Commerce is designed for high-volume consumer retail, not B2B. B2B Commerce is built on the Salesforce platform, so it integrates with CRM natively.
• Salesforce B2B Commerce vs. Shopify Plus – Shopify Plus is easier to set up and cheaper, but it lacks native CRM integration and complex B2B features like account hierarchies and contract pricing.
• Salesforce B2B Commerce vs. SAP Commerce Cloud – SAP is more powerful for large enterprises with complex ERP needs, but it is also more expensive and harder to implement.

Choose Salesforce B2B Commerce if you already use Salesforce for CRM and need deep integration with sales processes. Choose a simpler platform if your B2B needs are basic and you do not have a large development budget.

Frequently Asked Questions

Does Salesforce B2B Commerce support multiple currencies?

Yes, it supports multiple currencies through Salesforce’s multi-currency feature. However, you need to enable it in your Salesforce org, and each price book must have entries for each currency. Buyers see prices in their preferred currency, and the platform handles conversion rates.

Can I use Salesforce B2B Commerce without a Salesforce CRM?

Technically, you can, but it is not recommended. The platform is built on the Salesforce platform, so you need at least a Salesforce org. Many features, such as account hierarchies and price books, rely on standard Salesforce objects. If you do not use Salesforce for CRM, you are paying for a platform you are not fully utilizing.

How does tax calculation work in B2B Commerce?

Salesforce B2B Commerce does not have a built-in tax engine. You integrate with a third-party tax service like Avalara or TaxJar, or you can calculate taxes manually with custom Apex. The tax is calculated during checkout and can be shown as a separate line item.

Is it possible to accept ACH or bank transfers?

Yes, but it requires a custom integration with a payment gateway that supports ACH. The platform itself does not handle ACH natively. You would typically use a gateway like Stripe or Adyen that offers ACH processing, and then configure the checkout to show it as a payment option.

Can a buyer place an order without a credit card?

Yes, if you enable purchase order payments. The buyer enters a PO number, and the order is placed without immediate payment. The seller then invoices the buyer later. This is a standard B2B feature, but it must be configured per buyer group or account.

How long does it take to implement Salesforce B2B Commerce?

Implementation time varies widely. A basic setup with standard features might take 2-3 months, while a complex integration with ERP, custom pricing, and approval workflows can take 6-12 months. The timeline depends on the size of your catalog, the number of integrations, and the level of customization.

Related

• Send Personal Notes to Yourself on Slack
• Skype Offline Installer: Full Setup Guide
• Handwriting Recognition in OneNote: How to Use It