How to Customize Your Salesforce B2B Commerce Storefront Without Rebuilding It
Your storefront has four layers you can change: branding, page components, buyer-specific catalogs and prices, and checkout. This guide shows what each layer controls, which tool changes it, and where configuration stops and custom code starts. It is based on Salesforce's current B2B Commerce documentation.
Key Takeaways
- Four layers: you customize a Salesforce B2B Commerce storefront through its look (theme and branding), its pages (Experience Builder components), what each buyer sees (catalogs, entitlements and price books) and how they buy (checkout, payments and extensions).
- New stores run on LWR. Since Summer '23 every new B2B store is built on the Lightning Web Runtime. Branding there flows through the Theme panel and
--dxpstyling hooks, and custom components are Lightning web components. - Most of the storefront is configuration: logo, colours, fonts, navigation, quick order, reorder, multiple carts, wishlists, purchase orders, buyer-group pricing, tiered prices, promotions, languages and SEO-friendly URLs.
- Code starts at the edges: custom Lightning web components, checkout extensions for pricing, tax, shipping and inventory, ERP integration, and fully headless front ends built on the Commerce APIs.
- Some claims need other products: request for quote and configurable products need Revenue Cloud add-ons. Native fraud scoring, credit terms and split payments are not documented features.
To customize a Salesforce B2B Commerce storefront, you work through four layers, in this order: brand the store in the Theme panel, arrange pages and components in Experience Builder, control what each buyer sees with buyer groups, entitlement policies and price books, and shape checkout with Commerce extensions. Most of that is configuration. Custom code is needed only where a standard component or extension point stops.
This guide is for growing and mid-market companies that sell to other businesses: manufacturers, distributors and wholesalers that want buyers to order online without losing their negotiated prices. It replaces our earlier feature list with a practical map of what you can change, the tool for each change, and the limits other guides leave out.
How Much of a B2B Commerce Storefront Can You Customize?
Almost everything a buyer sees, and most of it without code. Branding, page layout, navigation, product cards, cart, account pages and checkout pages are configured in Experience Builder. Who sees which products and prices is configured with buyer groups, entitlement policies and price books. Code is for custom components, external pricing, tax or shipping logic, and integrations.
Configuration covers it when you need your brand, your navigation and your catalog in a store that works like a well-designed B2B portal: account-specific prices, volume tiers, quick order by SKU, reorder from history, saved and shared carts, purchase order numbers at checkout, and several languages or currencies.
Plan for development when prices, inventory, tax or freight come from an ERP or another external system, when a page needs behaviour no standard component offers, when buyers need product configuration or quotes, or when you want a fully custom front end. Each of these has a documented extension path, and each needs design up front.
What Is Salesforce B2B Commerce Today?
Salesforce B2B Commerce is the Salesforce platform for selling online to business buyers, built on the same org as your CRM. You create a store from a template, customize it in Experience Builder, and run checkout and payments with standard Salesforce functionality. Salesforce now brands it "Agentforce Commerce for B2B", although the product and its documentation still say B2B Commerce in many places.

Three facts shape every customization decision:
- It is CRM-native. Buyers are contacts on business accounts. Products, price books and orders are Salesforce records, so account teams see web orders next to the rest of the relationship.
- One platform, two channels. The same platform runs direct-to-consumer (D2C) stores, and Salesforce says B2B and D2C can operate from one org with shared data and processes. Salesforce B2C Commerce is a separate product with its own storefront technology.
- It is supported on Enterprise, Unlimited and Developer editions of Salesforce, and licensed separately as B2B Commerce (see editions and pricing).
The store is the hub of the data model. Each store connects to exactly one catalog, which can hold up to 3 million products in categories up to five levels deep, plus price books, buyer groups and entitlement policies. Salesforce's B2B Commerce overview in Salesforce Help is the reference for each part.
LWR or Aura: Which B2B Store Are You Customizing?
Check this first, because it decides how every customization is built. Since Summer '23, all new B2B stores are built on the Lightning Web Runtime (LWR). Orgs enabled for Commerce before Spring '23 may still run Aura stores. Salesforce recommends LWR for new stores and suggests that Aura store owners consider migrating.
| Question | LWR B2B store | Aura B2B store |
|---|---|---|
| Who has it | Every B2B store created since Summer '23, from the Commerce Store template | Older stores, and orgs enabled for Commerce before Spring '23 |
| Component model | Lightning web components only | Lightning web components and Aura components |
| How styling works | Theme panel properties drive --dxp styling hooks across standard and custom components | Custom CSS classes on components |
| Structured data for SEO | JSON-LD on product detail pages, through expressions in head markup | Not supported |
| High Scale Orders | On by default for new LWR B2B stores since Summer '24 | Not supported |
| Salesforce's direction | Recommended for new stores | Consider migrating; no retirement date published |
Sources: Salesforce Help (store components, SEO structured data, checkout) and the B2B Commerce Aura-to-LWR migration guide, 22 October 2026.
A migration is not a switch you flip. Salesforce's migration guide describes creating a new store from the LWR template, refactoring custom components into Lightning web components, and moving store configuration across. Small details change too: in LWR the cart is a named page rather than a record page, so any component that navigates to the cart needs updating. If you run Aura today, treat your next round of customization as the moment to decide on migration, not as work to stack on the old store. Our Experience Cloud services page sets out how we weigh LWR against Aura for Salesforce sites in general.
The Four Layers of B2B Commerce Storefront Customization
Each layer has its own tool, and choosing the lowest layer that solves the problem keeps the store easy to upgrade. Start in the Commerce app's Website Design workspace, move to Experience Builder for pages and components, write custom Lightning web components only for genuine gaps, and go headless only when you need a front end Salesforce does not host.
Website Design workspace
Inside the Commerce app: add the logo, and set fonts, colours and button styles. This is where a store gets its basic brand in minutes.
Experience Builder
Drag components onto pages and set their properties, build navigation menus, edit header and footer, configure product cards, cart, account and checkout pages, and add markup to the head of every page.
Custom Lightning web components
Build components in an SFDX project and deploy them to Experience Builder. Salesforce publishes a Public Commerce LWR Library of storefront components to clone and adapt, so you rarely start from nothing.
Headless with the Commerce APIs
The Commerce Connect REST APIs cover search, products, carts, checkout, promotions, orders and wishlists. You get full control of the front end, and you host and scale it yourself.

Salesforce's developer guide compares the two front-end routes directly: Experience Builder stores use prebuilt templates that Salesforce hosts and scales, while a headless architecture gives full UI control but moves hosting and the integration layer to you. For most B2B stores, layers 1 to 3 are enough.
How Do You Brand a B2B Commerce Storefront?
On an LWR store, you brand once in the Theme panel and the whole store follows. Theme properties map to --dxp styling hooks, which are CSS custom properties that every standard component reads. Change the brand colour and every component using that hook updates, including custom Lightning web components built to use the same hooks.
What the Theme panel controls
| Theme panel tab | What you set | Example styling hook |
|---|---|---|
| Colors | Colour palettes per section of the site | Brand Color → --dxp-g-brand; Background Color → --dxp-g-root; Text Color → --dxp-g-root-contrast |
| Images | Logo and favicon, chosen from a Salesforce CMS workspace | — |
| Text | Fonts, heading styles, links, buttons, and font sizes for mobile and desktop | Text and button hooks |
| Site Spacing | Maximum content width, padding and spacing | Spacing hooks |
Source: Salesforce Developers, branding LWR sites and the styling hooks map, 22 October 2026.
Brand rules that save rework
- Style custom components through the hooks, not your own classes. Lightning web components use shadow DOM, so hard-coded classes do not follow theme changes. Components that read
--dxphooks stay on brand when marketing changes the palette. - Treat header and footer as components. LWR B2B stores ship with responsive header and footer components. A developer can build a custom header or footer and assign a custom layout per page when the standard ones are not enough.
- Keep content in the CMS. Guided store setup creates an enhanced CMS workspace and a channel connected to the store. Banners, images and rich content managed there can be reused across channels and translated, rather than pasted into pages.
- Put the store on your own domain before launch. Salesforce recommends a custom URL on a custom domain served through the Salesforce CDN for LWR B2B stores going live.

Which Standard Components Make a Storefront Work for B2B Buyers?
The components that matter most are the ones that speed up repeat buying. LWR stores include dozens of standard Lightning web components. For business buyers who order the same products again and again, the high-value ones are Quick Order, Reorder, multiple saved carts, wishlists and purchase order capture. All are configured in Experience Builder, without code.
Quick Order
Buyers enter SKUs and quantities to add many products to the cart at once, without browsing the catalog.
Reorder and Order List
A Reorder button and an order list that buyers can filter and sort, so last month's order becomes this month's cart in a click.
Multiple and Shared Carts
Buyers keep several carts, set a default, and share a cart with colleagues on the same account with view, edit or checkout access.
Wishlists
Saved product lists with a list badge in the header, useful for standard order guides per location or project.
Purchase Order
Collects a PO number at checkout. A Dual Payment component lets the buyer choose card or purchase order.
Multilevel Navigation
Menus up to five nested levels, which can be built from product categories, plus a country selector for multi-region stores.
Two details catch teams out. First, the Einstein Recommendations component is deprecated as of Summer '26. Product recommendations now use the Carousel component with the Product Recommendations data source, so older build guides need adjusting. Second, product cards on search and category pages come from the Results Grid and Product Card components, where you set columns, spacing and pagination or "Load More".
When no standard component fits, a developer builds a custom Lightning web component for the store, often starting from Salesforce's Public Commerce LWR Library of pricing displays, variant selectors, quantity rules, add-to-cart buttons and search filters. Custom component properties can be marked translatable, so they work in multilingual stores.
How Do You Show Each Buyer the Right Catalog and Price?
With three linked records: buyer groups, entitlement policies and price books. A buyer group collects accounts that share terms. An entitlement policy decides which products that group can see. Price books attached to the group decide what they pay. This is how one storefront shows a distributor, a dealer and a direct customer different products and different prices.
| What you want | How B2B Commerce does it | Limit or rule to know |
|---|---|---|
| Contract or tier pricing | One buyer group, entitlement policy and price book per tier | An account can belong to up to 20 buyer groups |
| Restricted catalog | Entitlement policy on the buyer group controls product visibility | One catalog per store, with categories up to five levels |
| Buyer in several groups | Pricing strategy: Best Price (lowest wins) or Priority Price (your order wins) | Set once per store; test it with real overlapping accounts |
| Volume (tiered) pricing | Price adjustment schedules with percentage, amount or override tiers | Override tiers need Advanced Pricing; overlapping tier ranges make pricing fail |
| Strikethrough prices | A store strikethrough price book alongside the standard one | Every product needs a standard price book entry first |
| Promotions and coupons | Promotions with segments, qualifiers, discounts and coupons | Tiered promotions support up to 10 tiers |
| Regional prices and currencies | Markets per locale, each with its price book, entitlement policy, currency and ship-to countries | Up to 25 active locales per store; markets for signed-in B2B buyers must be enabled |
Sources: Salesforce Help on buyer groups, entitlements and price books, pricing strategies, tiered pricing, promotions and markets; Trailhead B2B Commerce data model. Read 22 October 2026.
Design this layer before you touch the theme. The buyer group structure decides how pricing is maintained for years: one group per customer is precise but heavy to manage, while one group per tier is lighter but cannot express one-off contract prices. Most B2B stores end up with a mix: tiers for the majority of accounts, and buyer-specific groups only for key accounts.
How Do You Customize Checkout in a B2B Store?
B2B stores use custom checkout, which you lay out in Experience Builder and extend with Commerce extensions. Managed checkout is not available for B2B. You choose an accordion or one-page layout, add payment and purchase order components, set up shipping, and connect external pricing, tax, shipping or inventory logic through extension points written in Apex.
Payments
Salesforce Payments is the native option. For B2B Commerce it supports credit cards, digital wallets, bank debits, bank redirects and buy now, pay later, with methods depending on the gateway: Stripe, Adyen or PayPal. It handles tokenization and authorization, supports 3D Secure, and lets contacts on the same account share saved payment methods. Salesforce Payments is not available to customers contracting with Salesforce in Brazil, India or Japan, so those stores use a third-party gateway. Purchase orders are handled through the Purchase Order and Dual Payment components.
Shipping, tax, pricing and inventory: extension points
| Extension point | Salesforce default | Typical reason to extend |
|---|---|---|
| Pricing calculator | Salesforce price books | Contract prices held in the ERP |
| Inventory calculator | Omnichannel Inventory | Stock levels from a warehouse system |
| Shipping calculator | No charge | Carrier rates or freight rules |
| Tax calculator | Salesforce tax service | A dedicated tax engine |
| Promotions calculator | Standard store promotions | Discount logic from another system |
| Create order, place order validation, split shipment | Standard checkout | Credit checks, order rules, multi-address delivery |
Source: Salesforce Developers, available Commerce extensions, 22 October 2026. Release status varies by extension.
Commerce extensions arrived in Winter '24, and Salesforce recommends them over the older checkout integrations framework, which is still supported. A provider class extends a base Apex class and is mapped to an extension point, so the standard checkout keeps working and calls your logic only where it is registered. Shipping can also be configured without code, through shipping profiles, zones and rates by order value or weight.
How Do You Tune Search, SEO and Languages?
Search is tuned in the store's search settings, SEO in page properties and URL slugs, and languages in Translation Workbench. B2B buyers search by SKU more than by browsing, so start with SKU and partial-SKU search, synonyms and sort rules. Then make the public catalog crawlable with URL slugs and sitemaps, and translate the store for each market.
- Search: searchable fields, filters, sort rules, one-way and two-way synonyms, suggestions, SKU and partial SKU search (B2B only), and merchandising rules that pin products on category pages. Rebuild the search index after catalog changes.
- SEO-friendly URLs: URL slugs replace record IDs, so a product lives at
/product/{slug}. Slugs need Translation Workbench and active languages, allow 150 characters and one slug per language, and can be loaded in bulk by CSV. - Sitemaps and structured data: sitemaps refresh weekly, or manually once every 24 hours, and include products visible to guest users. LWR stores can add JSON-LD structured data to product detail pages.
- Languages: LWR sites support up to 40 languages, including standard component text, rich content and SEO page properties. Right-to-left support in standard components is limited.
- Currencies: multiple currencies are activated for the whole org. Product prices can carry three or more decimal places, while line, cart and order totals round to two.
One rule connects search and SEO: sitemaps list the products your guest buyer group is entitled to. If the public catalog is hidden from guests, it cannot rank. Decide early which products, if any, should be visible before login.
How Does the Storefront Connect to ERP and Order Management?
Decide where an order lives after checkout before you connect anything. B2B Commerce creates unmanaged orders by default, which suits companies that fulfil and invoice in an ERP. To manage fulfilment in Salesforce Order Management instead, checkout must create managed order summaries, and Salesforce notes that the lifecycle type cannot be changed later.

- ERP-led fulfilment (unmanaged orders): orders are created in Salesforce and sent to the ERP, which owns fulfilment, invoicing and often the contract price. Prices and stock can flow back through the pricing and inventory extension points.
- Salesforce-led fulfilment (managed orders): Salesforce Order Management handles fulfilment, changes and post-order payment tasks with Salesforce Payments. The B2B Growth Edition includes Order Management Lite, and Advanced includes full Order Management.
- Data loads: CSV import handles up to 10,000 products with nine images each per session, and Salesforce recommends Data Loader for larger imports. Ongoing catalog sync from a product information or ERP system is an integration job, not a manual one.
For the integration layer itself, we use the platform's own tools or middleware such as MuleSoft, depending on how many systems are involved. Our pages on Salesforce and NetSuite integration and MuleSoft integration cover the order-to-cash patterns in more depth.

What Can Agentforce Do in a B2B Storefront?
Salesforce documents two Agentforce capabilities for B2B stores: guided shopping for buyers and merchandising for your team. The guided shopping agent helps buyers discover products, view past orders, reorder and check order status. Agentforce Merchandising helps merchandisers manage the store in plain language. Both consume Einstein Requests, which Salesforce charges for separately.
- Agentforce for Guided Shopping (B2B): created in Agentforce Studio from a B2B template with standard subagents. Salesforce's setup notes list current limits: the product details subagent does not support custom branding, and cart management supports simple products only.
- Agentforce Merchandising for B2B Stores: English only, with usage that consumes Einstein Requests and possibly Data 360 credits.
- Announced in June 2026: Salesforce announced a B2B Buyer Agent that works over WhatsApp and SMS, and a Merchant Agent for catalog organization and sort rules, as generally available. The B2B pricing page lists Merchant Agent in both editions. Check your org's release notes for setup prerequisites before planning around them.
The practical sequence is unchanged by AI: an agent can only guide buyers to products they are entitled to and prices that are right. Clean catalog data, correct entitlements and working search come first. Our overview of AI in Salesforce covers readiness more broadly.
What Does B2B Commerce Not Do Out of the Box?
Many feature lists, including the earlier version of this post, credit B2B Commerce with capabilities that need another product, a partner or custom work. Check these against your requirements before you scope the project.
In What Order Should You Build and Customize the Store?
Data model first, look and feel last. Salesforce's Commerce Setup Assistant can create a basic store in about 30 minutes, but a store buyers trust depends on accounts, entitlements, prices and checkout being right. Branding is the easiest layer to change later. Pricing structure and order lifecycle are the hardest.

Salesforce Help's B2B Commerce section follows a similar order, from buyer access to products and pricing, checkout, search, SEO and website design, ending with publishing and activation. A live store benefits from a periodic review too: a Salesforce health check finds the permission, data and automation issues that build up around commerce over time.
How Much Does Salesforce B2B Commerce Cost?
Salesforce does not publish a list price for B2B Commerce. Both editions, Growth and Advanced, are "Contact for Pricing". Salesforce charges a percentage of gross merchandise value (GMV), meaning storefront revenue minus tax and shipping. The editions differ mainly in how many storefronts you can run and how much order management is included.
| Included | B2B Growth Edition | B2B Advanced Edition |
|---|---|---|
| Price basis | Contact for pricing; % of GMV | Contact for pricing; % of GMV |
| Storefronts | 6 | 10 |
| Inventory locations | 20 | 20 |
| Order management | Order Management Lite | Full Order Management |
| Data Cloud credits | 250K | 500K |
| CRM Analytics users | 3 | 5 |
| Merchant Agent | Included | Included |
Source: Salesforce B2B Commerce pricing, 22 October 2026. Orders from other channels processed in Order Management are charged separately. Premier Success is 30% of net license fees.
The total cost of a storefront is mostly in the project, not the license: the data model, integrations and extensions above. That is why the decisions in sections 7, 8 and 10 deserve the most attention in a budget.
How Twopir Consulting Helps With B2B Commerce Storefronts
Twopir Consulting is a Salesforce Partner and HubSpot Partner. We help growing and mid-market companies solve complex CRM, integration and business system challenges: we implement, rescue, optimize, and integrate complex CRM and revenue systems. For a B2B storefront, that means designing the account, entitlement and pricing model with you, connecting the store to the systems that hold your prices, stock and invoices, and customizing the storefront so it stays upgradeable.
- LWR sites and components: theme, page and custom Lightning web component work, through our Experience Cloud services.
- Manufacturers and distributors: how Salesforce fits dealer, distributor and direct sales models, on our Salesforce for manufacturing page.
- ERP and order-to-cash: NetSuite, SAP Business One and MuleSoft integration.
- Selling to consumers as well? Our B2C Commerce page covers Salesforce's separate consumer storefront product.
Plan Your B2B Storefront With an Architect
On a 30-minute discovery call, a Twopir Salesforce architect will review your buyers, pricing and ERP landscape, and tell you which parts of your storefront are configuration, which need extensions, and what to build first.
Schedule a Discovery CallThe Bottom Line
Customizing a Salesforce B2B Commerce storefront is less about design tools than about getting four layers right in the right order. Brand and pages are quick to change on an LWR store. What each buyer sees and pays, and how an order travels after checkout, are the decisions that last. Configure first, extend through documented extension points, and write custom components only for genuine gaps.
- 1
New B2B stores run on LWR. Brand them through the Theme panel and
--dxpstyling hooks. - 2
Experience Builder and standard components cover most B2B needs: quick order, reorder, shared carts, wishlists and purchase orders.
- 3
Buyer groups, entitlement policies and price books decide what each buyer sees and pays. Design them first.
- 4
B2B checkout is custom checkout, extended with Commerce extensions for pricing, inventory, shipping and tax.
- 5
Quotes and configurable products need Revenue Cloud add-ons; fraud scoring and credit terms come from other systems.
Frequently Asked Questions
Yes, for most of it. Logo, colours, fonts and buttons are set in the Website Design workspace and Theme panel, and pages, navigation, cart, account and checkout pages are configured in Experience Builder. Buyer-specific catalogs and prices are set with buyer groups, entitlement policies and price books. Code is needed for custom components, checkout extensions and integrations.
Since Summer '23, all new B2B stores are built on the Lightning Web Runtime (LWR), which supports Lightning web components only and styles them through --dxp styling hooks. Older Aura stores support Aura components too, but not features such as structured data or High Scale Orders. Salesforce recommends LWR for new stores and suggests Aura store owners consider migrating.
Put accounts that share terms in a buyer group, link the group to an entitlement policy for the products they may see, and assign price books for what they pay. An account can belong to up to 20 buyer groups, and the store's pricing strategy decides whether the lowest price or the highest-priority price book wins. Volume tiers use price adjustment schedules.
Yes. The Purchase Order component collects a PO number at checkout, and the Dual Payment component lets buyers choose a card or a purchase order. Card and other online payments can run through Salesforce Payments with Stripe, Adyen or PayPal, or through a third-party gateway. Credit limits and net terms are usually managed in the ERP.
Yes, through integration rather than a built-in connector for every ERP. Orders are unmanaged by default, which suits ERP-led fulfilment, and Commerce extensions let checkout call external pricing, inventory, shipping and tax logic. Catalog and price sync is typically handled by middleware such as MuleSoft or by a direct API integration.
Yes, with an add-on. Buyers can request a quote directly from their cart, but Salesforce requires Advanced Pricing for Commerce, powered by Revenue Cloud, for request for quote. The quotes are then managed in Sales Cloud or Agentforce Revenue Management.
Salesforce lists both B2B Commerce editions, Growth and Advanced, as contact for pricing, charged as a percentage of gross merchandise value: storefront revenue minus tax and shipping. Growth includes 6 storefronts and Order Management Lite; Advanced includes 10 storefronts and full Order Management.
Twopir Consulting
Twopir Consulting works with growing, mid-market, and enterprise organizations that need help with complex CRM implementations, integrations, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems on Salesforce and HubSpot, for clients across the US, UK, Australia and New Zealand, the UAE and Canada.