B2B Commerce Pricing in Salesforce: Price Books, Promotions, and Contract-Based Pricing

If you searched for how Price Books and Price Rules work in Salesforce B2B Commerce, here’s the short version: Price Rules, as a standalone feature, don’t exist in the platform anymore. Salesforce rebuilt B2B pricing around a layered system of price books, a pricing strategy setting, commerce promotions, and — for enterprise-grade needs — Advanced Pricing for Commerce powered by Revenue Cloud. The name changed because the job changed. Buyers now expect negotiated pricing, bulk discounts, and account-specific catalogs to show up correctly on the first page load, not after a support call.

This piece replaces our original 2024 article on the topic. Below is how B2B Commerce pricing actually works today, what to configure first, and where the old “Price Rules” concept lives now.

What Changed in Salesforce B2B Commerce Pricing Since 2024?

Two things shifted the ground under this topic.

First, Salesforce folded Commerce Cloud, B2C Commerce, and B2B Commerce into a single suite it now brands Agentforce Commerce, reflecting the platform’s growing dependence on AI agents for merchandising, guided shopping, and search. You’ll still see “Commerce Cloud” in older documentation and in Salesforce’s own admin screens, the underlying product hasn’t been renamed everywhere, but the direction is clear.

Second, and more relevant to this article, Salesforce restructured how B2B pricing logic gets applied. What used to be described loosely as “Price Rules” is now split across five distinct mechanisms, each with its own configuration screen:

1. Price books — where prices live
2. Pricing strategy — how conflicting prices get resolved
3. Commerce Promotions — where discount and segmentation logic lives
4. Qualification Rules — where product visibility and eligibility get controlled
5. Advanced Pricing for Commerce, powered by Revenue Cloud — where contract-based and procedural pricing get built for complex accounts

If your org was built before this split, or your admin team still refers to “the price rule for tier 2 buyers,” it’s worth mapping what you have against this structure, because a few of these mechanisms now do jobs that used to require custom Apex.

Price Books: The Foundation of B2B Commerce Pricing

A price book is still a catalog of products and their prices, but the hierarchy underneath it is stricter than it was two years ago. Every product must first have an entry in the Standard Price Book, there’s only one per org, before it can appear in any other price book. From there, you build custom price books tied to a buyer group or a store, and assign them accordingly.

• Buyer group price books hold negotiated or segment-specific pricing, a “Platinum Distributor” tier, a regional reseller rate, and a government pricing schedule.
• Store price books apply pricing across an entire storefront, useful when you’re running separate sites per region or brand.
• Currency is handled at the price book level, so a global manufacturer selling in USD, EUR, and INR maintains separate price books per currency rather than converting on the fly.

This part of the system hasn’t changed in spirit since 2024. What has changed is what happens when a buyer qualifies for more than one price book at once.

Best Price or Priority Price: How Salesforce Resolves Conflicting Prices

A buyer in a B2B store can belong to multiple buyer groups, and multiple price books can be attached to a single buyer group or store. That means the same buyer might technically qualify for three different prices on the same item. Salesforce resolves this with a store-level setting called pricing strategy, and you pick one of two modes:

• Best Price — the store automatically shows the lowest of all prices the buyer qualifies for.
• Priority Price — you rank price books in order, and the highest-ranked one wins regardless of which is cheaper.

Say a distributor belongs to both a “Fall Promotion” buyer group and a “Preferred Partner” buyer group, and each has a different price on the same SKU. Under Best Price, the buyer automatically gets whichever number is lower. Under Priority Price, an admin decides in advance that Preferred Partner pricing always takes precedence, even if the promotional price happens to be cheaper that week. Manufacturers running long-term contracts tend to prefer Priority Price, since it protects negotiated terms from being accidentally undercut by a seasonal promotion.

Tiered Pricing: Volume Discounts Without Custom Code

Bulk purchasing is the defining behavior of B2B buying, and Salesforce handles it natively through tiered pricing at the price book entry level. You set quantity breakpoints — buy 10, pay $45 each; buy 50, pay $38 each; buy 200, pay $31 each and the storefront applies the right tier automatically as the buyer adjusts cart quantity.

This is the part of the old “Price Books” feature set that survived largely intact. What’s new is that tiered pricing now interacts cleanly with the pricing strategy setting above it, so a volume discount and a buyer-group discount can both apply without conflicting logic buried in a workflow rule.

Strikethrough Pricing and a New EU Compliance Requirement

To highlight a discount, B2B Commerce still supports a strikethrough price book that displays the original list price or MSRP with a line through it next to the negotiated rate. Every store gets one by default.

One addition worth flagging for anyone selling into Europe: Lowest List Price Compliance. Under an EU pricing-transparency mandate, stores showing a promotional or reduced price must also display the lowest price that product was offered at over the prior 30 days. Salesforce built a dedicated component for this, and it applies to guest checkout in particular. If you sell to EU buyers and haven’t looked at this setting, it’s a compliance gap worth closing before an audit finds it for you.

Where “Price Rules” Logic Actually Lives Now: Commerce Promotions

Here’s the real answer to what happened to Price Rules. Segment-based discounts, promotional pricing, and order-value thresholds- the scenarios the old article described under “Price Rules”, now live inside Commerce Promotions, a purpose-built module rather than a set of conditional rules bolted onto a price book.

Promotions in B2B Commerce support:

• Percentage or fixed discounts on specific products, categories, or entire orders
• Coupon codes for controlled distribution
• Buyer-segment targeting, so a promotion only surfaces for the accounts it’s meant for
• Tiered promotion structures (“spend $5,000, save 10%; spend $10,000, save 15%”)
• A guided setup workflow, including an Einstein-assisted option that drafts promotion logic from a plain-language description

Separately, Qualification Rules now handle a job that used to get tangled up with pricing: controlling whether a buyer group can even see a product, independent of what price they’d pay for it. Keeping visibility and pricing as separate mechanisms makes both easier to audit, you’re no longer hunting through a pricing rule to figure out why a product is hidden, or vice versa.

MAP Enforcement and Contract Pricing: Advanced Pricing Powered by Revenue Cloud

The original article mentioned Minimum Advertised Price enforcement as a Price Rules use case. That capability, along with genuinely complex conditional pricing, now sits under Advanced Pricing for Commerce, powered by Revenue Cloud, the enterprise tier of this whole system.

This layer introduces:

• Pricing Procedure Plans, which let you build multi-step pricing logic (base price, then contract adjustment, then volume discount, then tax) without writing a trigger for each step
• Contract-Based Pricing, which ties a buyer’s price directly to an active sales contract, including volume-based adjustments that shift as the buyer’s committed spend changes over the contract term
• Apex hooks, for the edge cases no configuration screen anticipates
• Support for multiple pricing recipes, so a single org can run simpler standard pricing for smaller accounts and procedural pricing for strategic ones, side by side

This is the closest thing to what B2B teams used to try to force out of Price Rules — and it’s a meaningfully more capable system, because it’s built on Revenue Cloud’s pricing engine rather than storefront-level conditionals. Salesforce cites Forrester research showing B2B Commerce implementations improving manufacturers’ ROI by up to 289% and lifting sales margins by roughly 5%, largely on the back of this kind of pricing precision paired with self-service reordering (Salesforce, Spring ’26 B2B innovations).

If your business runs on negotiated contracts with volume commitments — distributors, manufacturers, and industrial suppliers most commonly, this is the layer to evaluate before trying to replicate contract logic with workarounds elsewhere.

Why Accurate Price Books Now Matter to AI Agents, Not Just Buyers

One shift worth planning for: pricing data in B2B Commerce is no longer read only by humans and your storefront’s own search index. Salesforce’s Agentforce Merchandising and Agentforce Guided Shopping agents pull directly from your price books and promotions to answer buyer questions and recommend products inside the store itself. And the buying journey is starting to extend past your storefront entirely, Salesforce has begun enabling merchants to sell through the Agentic Commerce Protocol inside ChatGPT and through Google’s AI-driven search, meaning a buyer’s question about pricing might get answered by an AI assistant that’s reading your catalog, not your sales team.

The practical takeaway: price book hygiene, accurate entitlements, current tiers, correctly scoped buyer groups is turning into an AI-readiness requirement, not just a storefront-accuracy one. A price book with stale entries or an overly permissive buyer group assignment doesn’t just risk showing the wrong price to a human buyer; it risks an AI agent quoting it confidently to a purchasing system on the other end.

Getting Your Pricing Architecture Right: A Practical Starting Point

Before configuring anything, most B2B Commerce projects benefit from settling three questions:

• How many genuinely distinct pricing tiers do you have? If the honest answer is two or three, standard price books plus a pricing strategy setting will likely cover it. Reaching straight for Revenue Cloud when you don’t need contract-based logic adds cost and complexity without adding value.
• Do prices depend on an active contract, or just a segment? Segment-based pricing (a distributor tier, a loyalty level) belongs in buyer group price books and promotions. Contract-dependent pricing that shifts with committed volume belongs in Advanced Pricing for Commerce.
• Who owns promotion creation day-to-day? Since promotions now live in a guided workflow rather than a developer-maintained rule set, this is often a good moment to hand routine discount management back to a commerce or marketing operations owner, freeing admin time for the structural work.

Cloud Odyssey’s Take

We still hear “Price Rules” in almost every discovery call for a B2B Commerce project, usually from a team that built their store a few release cycles ago and hasn’t revisited the pricing architecture since. That’s not a knock, Salesforce’s own naming took a while to catch up with the platform’s direction, and the old terminology stuck around in enough documentation and community content that it’s a reasonable place to still be.

The mistake we see most often isn’t using outdated terms, it’s outdated architecture. Teams that built promotional logic into custom price book entries or Apex years ago are now maintaining code paths that Commerce Promotions and Qualification Rules can handle natively, at less operational cost and with far easier auditing. On the other end, we’ve seen teams try to stretch a standard price book into contract-based pricing with volume commitments, which is exactly the scenario Advanced Pricing for Commerce was built to remove from the storefront layer entirely.

Our recommendation before any B2B Commerce pricing project: map your current pricing logic against the five mechanisms above first, then decide what to migrate versus rebuild. It’s a shorter project than most teams expect, and it usually surfaces compliance gaps — Lowest List Price Compliance is the one we flag most for EU-facing clients, that are worth catching before go-live rather than after.

If you’re evaluating whether your current setup needs a rework, our Salesforce Commerce Cloud implementation services team can audit the existing configuration against what’s available today. And if contract-based pricing or procedural pricing logic is on your roadmap, it’s worth a parallel conversation with our Revenue Cloud implementation practice, since Advanced Pricing for Commerce runs on that engine.

Frequently Asked Questions

Cloud Odyssey is a Salesforce Summit Partner and MuleSoft expert helping B2B and B2C businesses design, implement, and modernize their commerce platforms. Explore our Commerce Cloud implementation services or get in touch to talk through your pricing architecture.