Customer-specific B2B pricing: what goes wrong without the right pricing logic

A buyer at a large building materials wholesaler logs in to your B2B portal at half past seven in the morning. He expects his agreed gross prices excluding VAT, the credit his management reserved for this quarter, and the quote he aligned with your account manager yesterday. If he sees a list price, a price including VAT or the wrong volume tier, he does not call. He closes the tab and orders elsewhere.

This is the real playing field of B2B e-commerce. Not a catalogue with one price per item, but a system in which every visitor brings their own price list, their own discount structure and their own set of agreements. And yet in many projects customer-specific pricing is only put on the table as a requirement at a late stage. That is the moment platforms built for consumer markets start to crack.

Pricing in B2B is not a price list, it is a calculation rule

In B2C, pricing consists of a product price including VAT, perhaps a promotion, and that is the end of the story. In B2B the price is the outcome of logic. A customer has a contract price at item level, a group discount per category, a volume tier agreement from certain quantities onwards, and on top of that a temporary promotion that applies only to specific customer segments. The price the buyer sees is not a field in the database. It is a calculation at the moment he logs in.

The order in which those rules are applied is rarely random either. A typical hierarchy places a promotional price above the contract price, which sits above the customer-specific price, which sits above a group price, which ultimately sits above the gross catalogue price. Which rule wins and in what order determines the difference between a correct invoice and a commercial accident. A platform that does not treat that hierarchy as core logic pushes the problem on to custom work or to manual corrections after the fact.

The presentation differs as well. A business buyer looks at prices excluding VAT by default, because VAT is deductible for him and therefore not part of his actual cost price. A platform that only shows prices including VAT, or that cannot distinguish display per customer group, misses the basics. Some customers also expect their gross price next to their net price so they can verify their agreed discount. Price display is not a screen variant, it is part of the logic.

That has direct consequences for your architecture. A platform that stores prices in its own database has to synchronise those prices with your ERP at scale. If you have fifty thousand items, ten thousand customers and an average of five price rules per combination, you quickly reach hundreds of millions of price points. Every change in the ERP, every new contract period, every volume tier adjustment has to be pushed through. Synchronisation becomes a problem in its own right.

The alternative route is to retrieve prices from the ERP in real time. That sounds logical, but it only works if the platform and the integration can handle the response time, even with hundreds of simultaneous sessions and complex shopping cart calculations. This is where the roads part between platforms designed for B2B and solutions developed further from a B2C base.

Real-time pricing is also not an all or nothing choice. Good platforms offer two levels: only the product price from the ERP, while the cart calculation, promotions and order discounts stay on the platform. Or the entire calculation, including taxes and order surcharges, sits with the ERP. The first variant gives you flexibility for commercial promotions in the webshop, the second maximum consistency with your administration. Which one fits depends on how complex your prices are and how often you actually change them.

Why Shopify and Shopware are often not the right choice 

Shopify Plus and Shopware now offer B2B extensions. For simple scenarios, think of fixed price lists per customer group and a limited ERP integration, they can work perfectly well. The problem arises as soon as your pricing depends on multiple layers at once: contract plus volume tier plus promotion plus customer discount plus an active quote. The pricing engines of those platforms are not designed to execute that logic themselves, and the integrations that do are often custom built. Custom work that you have to maintain again with every release.

For a wholesaler or brand manufacturer with thousands of active customers, that is a structural risk. Not today, but two years from now when your ERP is replaced or your commercial department introduces a new discount model. A platform that treats customer-specific pricing as a core function handles those changes differently from a platform that solves it through plugins and apps. The difference lies in where the logic lives: in the core of the system or in a shell around it that you have to maintain yourself.

Quotes, contracts and budgets belong in the same layer

Pricing does not stand on its own. A professional B2B buyer works with quotes that are valid for months, contracts concluded at item or category level, and budgets reserved per buyer, cost centre or location. Anyone who keeps that separate from their webshop forces the customer to work outside the portal. Emails with PDF quotes, phone calls to check stock, an Excel sheet the buyer keeps himself to monitor his spending room.

A well-configured B2B platform captures that in one environment:

1. Accept quotes online and convert them into orders. The account manager builds the quote in the ERP or CRM, the customer sees it in his portal, accepts it digitally and the order flows back automatically.

2. Contract terms visible at every item. The customer sees not only his price, but also which contract condition applies, until when and at which minimum purchase.

3. Budget monitoring per user or location. If a buyer orders on behalf of a branch, the system shows the remaining budget and blocks it when exceeded, or routes it to an approver.

4. Tailored approval flows. Orders above a certain amount, or for specific categories, are automatically routed to the right person.

These functions belong on the platform, not as separate interfaces. Only then does the digital working environment emerge that a professional buyer expects from his supplier.

ERP as the source, the platform as the interface

The ERP remains the single source of truth for master data, prices, stock and order status. The B2B platform is the interface where that data is presented in context. Between the two sits the integration, and that is where investment often falls short. You do not make a platform choice based on demos, but based on how the system behaves under your data volume, your pricing logic and your peak moments.

So put the concrete question to every vendor: how does this platform handle a customer with one hundred thousand items in his assortment, fifty active contracts, three open quotes and a quarterly budget per branch? Do not ask for a nice slide, ask for a test setup with your own ERP integration and a sample of your real customer data. The answers tell you more than any feature comparison.

Pay attention as well to what happens the moment a price changes. How quickly does a new contract price take effect in active sessions? What happens to a cart the customer built yesterday? How do quotes deal with an interim adjustment of volume tier discounts? These are the scenarios where many projects run aground after go-live.