B2B Price Lists and Tier Pricing in Shopware

In B2C retail, the price is largely static: a product has one price, perhaps supplemented by a time-limited promotion. In B2B, by contrast, price resolution is the result of negotiated framework contracts, annual bonuses, quantity tiers and customer-specific special terms. A study by the Boston Consulting Group shows that 65 percent (Boston Consulting Group, 2025) of B2B revenue already flows through digital or digitally influenced channels - so the negotiated pricing logic must also work correctly online, otherwise a break emerges between field sales and the store.

Making matters harder, a substantial share of buyers prefer self-service: according to McKinsey, 35 percent (McKinsey B2B Pulse, 2025) of B2B buyers now complete orders worth 50,000 US dollars or more entirely digitally - precisely where customer-specific terms matter most. On top of that, B2B customers expect net prices, want VAT shown separately and require the reverse charge procedure for intra-community deliveries with a valid VAT ID. Prices are often valid only for certain periods, are tied to packaging units, and differ by customer group. A professional implementation of these requirements is the core of any serious B2B e-commerce consulting and determines whether buyers perceive a store as reliable.

Shopware open source ships with several mechanisms out of the box that can be combined to map a multi-layered B2B pricing logic. The first building block is customer groups: every customer belongs to a group that controls, among other things, whether net or gross prices are shown and which assortments are visible. On top of this, prices can be stored per customer group and per sales channel, so a reseller channel sees different terms than an open store.

The second building block is advanced prices directly on the product. This is where tier pricing is defined: from a quantity of 1, price A applies, from 10 price B, from 50 price C. These tiers can vary per customer group. The third building block is the Rule Builder, which lets you formulate conditions - such as cart value, customer group, order quantity or shipping country - that in turn trigger price and shipping rules. For customer-specific special prices from framework contracts, supplementary extensions or a direct connection to the ERP terms are added in practice, which we clarify in a personal conversation.

Tier pricing is the heart of B2B selling: it rewards larger purchase quantities and demonstrably raises the average order value. The German B2B e-commerce market recently grew to a volume of around 352 billion euros (BEVH, 2024), and a growing share of that arises from digital orders with stored quantity terms. For it to take effect, the quantity thresholds must be communicated transparently. A buyer who sees in the cart that increasing from 8 to 10 units lowers the per-unit price noticeably will often order the larger quantity. This visibility of the next tier directly on the product and in the cart is a powerful lever for increasing revenue.

Technically, different tier types must be distinguished. With the absolute tier, the reduced unit price applies to the entire order quantity once the threshold is reached. With the incremental tier, the discount applies only to the units above the threshold. In German B2B trade, the absolute tier is considerably more common and more intuitive, but it should be chosen consciously and documented. Add to this packaging units: if an item is sold only in packs of 12, the store must round quantities accordingly and calculate the tier on a packaging-unit basis.

The customer-specific prices that matter for B2B are maintained in the vast majority of companies not in the store but in the ERP system. That is where the master data of the terms lives: framework contracts, annual bonuses, customer-specific item prices and discount groups. In this architecture, the store is not a standalone pricing system but a display and ordering channel that consistently reflects the truth held in the ERP. A clean ERP integration is therefore the basic prerequisite for correct B2B prices in the store, as our project examples show.

There are two fundamental strategies for synchronization. With the batch sync, the price lists are transferred from the ERP to the store periodically - nightly or several times a day - and stored there. This is robust and performant but can cause delays for very short-notice condition changes. With the real-time query, the store queries the price directly from the ERP at the moment of display, or at the latest in the cart. This delivers maximum currency but places high demands on response times and on the resilience of the interface. In practice, a hybrid approach has proven effective, as described in detail in our API architecture.

The example shows a typical payload structure for the terms sync: per customer, a price list with a validity period is transferred, and individual items carry their tiers as a list of thresholds and prices. It is important to explicitly flag the value as a net price and to state the currency. This structured handover prevents room for interpretation between ERP and store and makes price resolution traceable - a central requirement when terms are later audited or discussed with buyers.

The correct display of net and gross prices is not a formality in B2B but a legal and commercial necessity. Business customers expect net prices as standard, with VAT shown separately. Shopware controls this display via the customer group, so the same catalog can appear net for resellers and gross for end customers. For pure B2B stores, net display is the normal case; for mixed models (B2X), the display must switch dynamically per customer type.

Tax becomes more demanding with cross-border transactions. For intra-community deliveries to companies with a valid and verified VAT ID, the reverse charge procedure applies, under which no German VAT is shown. The store must validate the VAT ID, take the delivery country into account and apply the correct tax rate or the exemption with the corresponding note. Consistency between the store tax logic and accounting is in turn ensured by a DATEV-capable interface, so that documents and bookings match - an aspect we address early in e-commerce consulting.

The best pricing logic is of little use if the buyer does not understand it. Transparency is a trust factor in B2B: in the B2B Future Shopper Report, 48 percent (Wunderman Thompson B2B Future Shopper, 2025) of buyers name transparent prices and terms as one of the most important reasons for choosing a digital supplier. Customers want to understand why an item has its price and which quantity advantages are still within reach. The product page should therefore show the applicable tier in full - including the next higher threshold and the savings there. In the cart, the individually best price is applied automatically and the discount used is clearly named.

Technically decisive is real-time price calculation without a page reload. When the buyer changes the quantity and thereby moves into a different tier, the new price must update immediately via AJAX - line price, quantity threshold and total. Conversion studies show that every avoidable friction in the order process raises abandonment; the Baymard Institute puts the average cart abandonment rate across industries at around 70 percent (Baymard Institute, 2025). A clear, instantly responsive price display noticeably reduces this friction. For more on how to optimize the entire order completion, see our article on the B2B checkout.

B2B assortments often comprise tens of thousands of items, and every customer group can have its own prices and tiers. If the price has to be recalculated from several sources for every display - special price, tier, discount group, ERP query - load quickly builds up that noticeably slows category pages and search. Since slow pages directly affect conversion and Google treats load time as a ranking factor (Google Search Central, 2025), the performance of price resolution is not a technical detail but a business factor.

The most effective levers are targeted caching of calculated prices per customer group, invalidated only on a change of terms, and holding synchronized ERP prices in the store rather than a live query on every page view. For real-time scenarios, asynchronous queries with a short timeout and a fallback to the last known price are recommended, so the page remains responsive even with a slow interface. How such optimizations can be implemented holistically is something we are happy to discuss in direct contact.

Price data is not a one-off project but an ongoing process. Terms change, contracts expire, new customer groups are added. Without clear responsibilities and maintenance processes, ERP and store sooner or later drift apart. Every pricing project therefore includes the question of who creates terms, who approves them and how changes are logged. Ideally the ERP is the leading source, the store mirrors exclusively, and every deviation is reported automatically.

For quality assurance, automated plausibility checks have proven valuable: a special price above the list price, a tier with rising rather than falling unit prices, or an expired validity period should trigger warnings before they become visible in the store. Such checks can be integrated into the sync process and catch errors that would otherwise only be noticed by the customer. Combined with clean product data - the topic of our article on PIM and data quality - this creates a robust data foundation for the entire price resolution.

Large B2B customers increasingly no longer order directly in the web store but through their own procurement systems. Using standards such as PunchOut and OCI, they connect their purchasing system to the supplier catalog, browse there with their individual terms and hand the finished cart back into their system. For this to work, the store's pricing logic must also take effect in the PunchOut context - the catalog must show the logged-in purchasing system exactly the prices stored for that customer. How such catalogs are connected is described in our article on PunchOut and OCI catalogs.

The interlocking of pricing logic and procurement integration is a good example of why prices must not be viewed in isolation. They are closely interwoven with customer groups, ERP terms, tax logic, search and procurement interfaces. A well-thought-out architecture ensures that the price defined once applies consistently across all channels - whether in the web store, the customer portal or the PunchOut catalog. It is precisely this consistency that buyers perceive as professional and trustworthy and that sets a Shopware project apart from the standard.

Those who think of their B2B price resolution as a coherent system from the start, rather than patching individual requirements afterwards, build a foundation that can grow with the business. New customer groups, additional markets or changed terms models can then be added without endangering the existing logic. The investment in a clean pricing concept and its technically sound implementation pays off over the entire lifespan of the store - in less support effort, higher data quality and a buying experience that business customers enjoy using. A look at comparable project approaches helps make the right decisions early.