Free tools Windows power users keep installed
One-click scans. No signup required.
Salesforce B2B Commerce is a configurable storefront and ordering platform for business buyers. It connects buyer accounts and groups with product access, price books, search, carts, checkout, and payment; the way those pieces behave depends on the Salesforce org, subscription, configuration, and integrations. Here is how the platform’s buyer model, pricing, checkout, and payment options fit together.
What is Salesforce B2B Commerce?
Salesforce describes B2B Commerce as a platform for building customer-facing business storefronts. Merchants can configure storefront pages with templates and Experience Builder, set up search, carts, checkout, and payment, and import commerce data such as accounts, products, price books, and entitlements. Salesforce also describes support for a direct-to-consumer channel in the same org. See Salesforce’s B2B Commerce overview.
As an Amazon Associate I earn from qualifying purchases.
The overview lists Developer, Unlimited, and Enterprise editions as supported. That list is not by itself a purchasing recommendation: confirm current feature entitlements, availability, and subscription fit with Salesforce for the target org.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →What buyers can do
A configured store can provide responsive storefront pages, product search and recommendations, cart and checkout services, quote management, and buyer and product management. Salesforce Trailhead also describes promotions, saved carts or order templates, split shipments, cart sharing, and delivery estimates as available B2B store capabilities. These depend on configuration and release. If a buyer needs negotiated pricing, the buyer can request a quote for a merchant to edit and approve. See Trailhead’s overview of B2B Commerce storefronts.
#1 Best Overall
How do buyer groups and entitlements shape access?
The core model links buyers and their organizations to product access and pricing. Salesforce’s training material describes buyer, buyer group, entitlement policy, and price book objects as tools for tailoring the store to business segments. A merchant can use these relationships to offer tiered or buyer-specific pricing and to limit products or prices according to negotiated contracts.
In practice, a buyer group helps define which segment a buyer belongs to; entitlement policies determine what that segment can access; and a price book supplies applicable product prices. This allows different business customers to see different assortments or terms in the same storefront experience, subject to the org’s configuration.
How does Salesforce B2B Commerce pricing work?
Store setup includes selecting a price book and pricing strategy, with the option to use a custom price-check provider. Salesforce’s setup documentation notes a specific catalog configuration: physical products need a price book entry without a Product Selling Model for prices to appear on category and search pages. That requirement applies to the documented configuration; it should not be treated as a universal rule for every catalog or pricing model. See Salesforce’s B2B store pricing setup guidance.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For a straightforward catalog, a price book and pricing strategy may be sufficient. If prices vary by customer or negotiated agreement, buyer groups, buyer-specific price books, entitlements, or a custom provider may be part of the design. The right approach depends on how the business maintains its contractual prices and product rules.
How does B2B Commerce checkout work?
Salesforce characterizes checkout as a state-driven process that turns a shopper’s cart into a permanent order. Its Commerce APIs checkout guide describes calculations for pricing, promotions, tax, shipping, and inventory that can run asynchronously as checkout information becomes available.
Typical API implementation sequence
- Add products to the active cart.
- Start checkout, creating or reusing a checkout session.
- Poll checkout status while asynchronous work proceeds.
- Update checkout details, such as customer and delivery information.
- Process payment.
- Place the order.
This sequence is described in Salesforce’s checkout implementation overview. The exact calculator behavior depends on the cart state and configuration.
When calculations run
In standard checkout, adding an item to an active cart runs pricing and promotion calculations. A checkout cart can also run inventory calculations; a shipping address can trigger shipping and tax calculations. Starting checkout creates or reuses a session and runs relevant calculators. Entering or changing delivery details can run shipping and tax calculations again. Payment authorization occurs before order validation and creation. Salesforce explains this sequence in How Standard B2B Commerce Checkout Works.
The Commerce Checkout APIs collect cart, customer, shipping, and payment information and connect to payment, shipping, and tax calculation services. For registered buyers, the APIs can return saved addresses and payment methods. A saved shipping address may cause shipping and tax calculations to run when checkout starts.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Can Salesforce B2B Commerce use third-party payment gateways?
Yes. Salesforce’s custom checkout instructions cover Salesforce Payments and third-party provider packages. If the required adapter is not listed, an implementation can use an AppExchange adapter or create one. Payment-provider choice is therefore an implementation decision, not a single fixed gateway built into every store. See Salesforce’s payment gateway connection guidance.
Before publishing a store, Salesforce directs implementers to test gateway behavior and review PaymentGatewayLogs for failures. A successful configuration should be validated in the target org and checkout flow rather than assumed from the provider’s availability.
How should teams customize checkout and integrations?
Salesforce introduced Commerce extensions for pricing, inventory, shipping, tax, and other services in Winter ’24. Its documentation says the checkout integrations framework remains supported, while recommending extensions for more targeted customization and broader Commerce-domain availability. Check current Salesforce guidance and compatibility for the target org before choosing a path. Details are in Salesforce’s checkout integration documentation.
AppExchange’s Commerce Cloud collection includes examples across payment gateways and connectors, tax calculation, multi-carrier shipping and returns, search and recommendations, and SAP ERP connectivity. Listings and their terms change; marketplace presence alone does not establish suitability or endorsement.
Who implements a B2B Commerce store?
Salesforce’s implementation lifecycle distinguishes developer, org admin, and store admin responsibilities. Developers handle technical work such as implementing Buyer Experience APIs, creating custom Lightning Web Components, extending Buyer Experience SDK interfaces, and packaging deployments. Admins handle org and store configuration. The exact division varies by project, but the role model shows why a B2B Commerce rollout can involve both configuration and development or integration work. See Salesforce’s implementation personas.
Quick Recap
What should a team decide before building?
- Which buyer segments need distinct product access, pricing, or contract terms?
- Whether standard price books and strategies cover pricing rules, or a custom price-check provider is needed.
- Which checkout services must calculate tax, shipping, and inventory, and when those calculations should run.
- Whether Salesforce Payments, an available third-party package or adapter, or a custom adapter fits payment requirements.
- Which implementation work belongs to admins and which requires developers or external integrations.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
