Customer-Specific Pricing

In B2B commerce, every account gets its own price. A product at $14.50 for Account A might be $12.80 for Account B. Customer-specific pricing is the ability to show different prices for identical products based on negotiated agreements, purchase volume, customer segment, or contract terms. This is the defining difference between B2B and B2C pricing: B2C posts one public price; B2B maintains a pricing matrix where every customer account pulls its unique price from the ERP.

How It Works

Implementing customer-specific pricing requires bidirectional ERP integration. The eCommerce platform must authenticate the customer, retrieve their account record from the ERP, apply pricing rules, and display the correct price at order time. The system must handle complex scenarios: tiered discounts based on volume within a single order, multiple pricing agreements that apply to different product categories, and contract-managed prices with specific start/end dates and minimum order values.

Pricing data lives in your ERP, which is the source of truth for all pricing. Legacy ERPs may lack modern APIs, or your custom pricing logic might exist as custom fields or in external pricing engines. Building the integration layer between ERP pricing and eCommerce is non-trivial—but it’s non-negotiable for B2B success. Without this integration, you either expose your lowest negotiated rate publicly (destroying margin) or force every transaction through manual quoting (eliminating self-service).

Strategic Impact

Customer-specific pricing directly protects margin. A 10% pricing error across your customer base can represent millions in lost revenue. It also creates opportunities for strategic pricing: you can reward loyal customers with better rates, use pricing to shift product mix or seasonal demand, and customize prices based on customer profitability.

In the AOV (Average Order Value) framework, customer-specific pricing is a key lever. When customers see prices calibrated to their account, they buy more per order and buy more frequently—because the platform reflects their negotiated reality. However, this sophistication requires clear governance: documented pricing rules, audit trails to prevent errors, and customer communication strategies to manage expectations.

Best Practices

Start with the simplest customer-specific pricing that serves your business model. A wholesale distributor might use basic tiering: Tier A resellers get 20% off, Tier B gets 15%, Tier C gets 10%. As complexity grows, add conditional logic: volume discounts that compound, category-specific pricing, or seasonal adjustments. The mistake is over-engineering pricing systems before you understand your actual business requirements.

Real-time pricing lookup is ideal but not always possible with legacy ERPs. Many organizations use scheduled sync (every 15-60 minutes) to pull current pricing into the eCommerce cache, then serve cached prices. Always validate that cached pricing hasn’t aged beyond acceptable limits. Build error handling to fall back to most-recent-known pricing if sync fails.

Price as a Spectrum — and When It Stops Mattering

B2B price sensitivity isn’t binary. When a buyer needs a product to solve a problem, price often doesn’t matter as long as it falls within a “reasonable range.” That range is defined by context: the last price they paid, what the rep quoted, what a competitor showed them, or what their budget allows. No single anchor dominates — it depends on the situation.

What matters more than the absolute price is price consistency. A buyer who sees $14.50 online but remembers being quoted $13.80 by their rep doesn’t just push back on the price — they lose confidence in the platform entirely. Inconsistency signals that the system isn’t trustworthy, that the ERP integration isn’t working correctly, or that the rep relationship is more reliable than the website.

“Price is both a big deal and not a big deal. When you need a product to solve a problem, often price doesn’t matter as long as it is within a reasonable range. But when price is inconsistent — people don’t trust the online system anymore.”
— Justin King, KB Capture, 2026-03-25

This is why ERP pricing integration isn’t just a technical requirement — it’s a trust requirement. A cached price that’s 24 hours stale can be the difference between a customer adopting the platform and abandoning it permanently.

Pricing Tiers in Practice

B2B pricing complexity goes beyond account-level contracts. Multiple overlapping tiers are common:

• Volume tiers — price drops at quantity thresholds within a single order
• Location-based pricing — different prices by ship-to region or branch
• Geography — pricing that varies by market or distribution zone
• Branch-level pricing — pricing set at a specific branch level, not company-wide

Each tier layer adds integration complexity and another potential source of inconsistency between what the rep knows and what the platform shows.