Codewerk.
Get a quote
Home/Blog/B2B pricing in Shopware 6 without losing your mind

B2B pricing in Shopware 6 without losing your mind

Customer groups, scale prices, contract prices, rule builder — four mechanisms that overlap. Here is which one to reach for, and when.

Photo: free stock photography (Unsplash licence) — see imprint

Start from where the price truly lives

In almost every B2B company the authoritative price sits in the ERP, not in the shop. Decide this explicitly: is Shopware the master of prices, or a display layer? Shops that never answer this end up with two prices for the same product and an angry sales team.

Customer groups are coarse — use them coarsely

Customer groups work well for a handful of tiers (retail, reseller, key account). The moment you have 400 customers with individually negotiated prices, groups are the wrong tool: you want contract prices synced from the ERP, keyed by customer number.

Rule Builder is powerful and dangerous

The Rule Builder can express nearly any condition, which is exactly the problem. Twenty overlapping rules become impossible to reason about and slow down the cart. Keep rules few, name them clearly, and put complex logic in code where it can be tested.

Show net, gross and the right one

B2B buyers want net prices, tax notes and their own currency. Getting this wrong does not just look unprofessional — it creates invoice disputes. Tie the display mode to the customer group and test it with a real customer login before launch.

Key takeaways
  • Name one master for prices: shop or ERP.
  • Groups for tiers, contract prices for individuals.
  • Few rules, clearly named, tested.

We do this for a living — Shopware, Node.js, React, ERP integration and automation for B2B.

Talk to an engineer

// Keep reading

Related articles