Customer Groups & Price Lists

In B2B, a one-size-fits-all price is rarely the reality.

Overview

We configure customer-specific price lists, tiered pricing, and discount groups directly in Shopware 6 — optionally driven by your ERP. Every business customer sees their own conditions after login: their catalogue, their prices, their currency. Manual price coordination by email becomes a thing of the past.

The essentials at a glance

  • We configure customer-specific price lists, tiered pricing and discount groups directly in Shopware 6 – optionally driven by your ERP.
  • We put complex pricing into Shopware's price rule engine instead of manual upkeep, so tiered prices, time-based validity and customer-specific overrides apply automatically.
  • The ERP stays the master for prices and the shop only reads from it, so no divergence arises and the source of truth is unambiguous.
  • We scope catalogs per customer group, so each customer sees only their approved products and conditions after login – a genuine benefit for large B2B catalogs.
  • This way every business customer sees exactly their conditions after login and manual price coordination by email becomes a thing of the past.
Set Up B2B Pricing Logic

Sales staff must manually communicate prices on request because the shop shows the same public prices to all customers.

Customer-specific conditions only exist in the ERP and must be manually transferred to the shop whenever something changes.

Business customers see products in the shop that aren't relevant to them, or miss products that should only be available for their group.

Individual Price Lists

Shopware 6 allows you to store individual price lists per customer group or per individual customer. We configure tiered pricing, volume discounts, and customer-specific special prices so they apply automatically after login. Pricing rules can be time-limited, quantity-tiered, or tied to conditions.

ERP-Driven Pricing

When prices are managed in the ERP, we synchronise them automatically into the shop. Customer-specific conditions, framework agreement prices, and special arrangements come directly from your ERP — no manual maintenance in the shop. ERP updates appear in the shop promptly.

Catalogue Control

Not every B2B customer should see every product. We configure customer groups so that after login, only the approved products and categories are visible. New products automatically appear for the right groups as soon as they are released in the shop or PIM.

Purchase on Account & Limits

B2B customers frequently order on account with individualised payment terms. We configure payment method assignments per customer group and implement credit limits that automatically request alternative payment methods when exceeded. The logic runs directly in checkout without manual intervention.

Composition of a B2B pricing logic

In a typical B2B shop, price evaluation is made up of several rule layers. The weighting shows how much configuration effort falls on each level.

  • Customer-group price listsIndividual conditions per group or account
  • Tiered pricing & volume discountsAutomatic price scaling by quantity
  • Catalogue filteringProduct visibility per customer group
  • Time-limited validity & promotionsTemporary special conditions or campaigns
  • Invoice purchase & credit limitsPayment terms per customer segment

Relative complexity shares — not measured values.

Setting up customer-specific conditions

Implementation follows a fixed sequence: first clarify the data source, then build the rule logic, finally test and hand over. Each phase builds on the previous one.

  1. ERP analysis & data model

    Capture price fields, discount groups and catalogue tables from the ERP; define mapping to Shopware entities.

  2. Customer-group architecture

    Create groups, roles and assignment rules in Shopware 6; define inheritance logic between standard and special conditions.

  3. Price-rule configuration

    Store tiered prices, time-limited validity and customer-specific overrides in the Shopware rule engine.

  4. Set up ERP synchronisation

    Shop pulls prices read-only from the ERP — no manual maintenance; configure intervals and error handling.

  5. Acceptance & go-live

    Run through login scenarios per customer group; validate price display, catalogue and payment terms, then go live.

Typical project flow — phases can be parallelised.

What matters for Customer Groups & Price Lists

Complex pricing belongs in a rule engine, not in manual upkeep. Tiered prices, discount groups, time-based validity and customer-specific overrides simply cannot be managed reliably by hand. Shopware's price rule engine handles the evaluation logic automatically, provided it is cleanly configured and synced with the ERP rather than maintained on the side.

The ERP stays the master for prices, and the shop reads from it. The moment prices are also maintained manually in the shop, divergence sets in sooner or later and nobody knows which value is correct. An ERP-driven sync, where the shop never acts as the leading system, is the only variant that stays consistent over time.

Assortment scoping is not just protection but usability. When each customer sees exactly their range and conditions after login, the shop becomes clearer and the search more efficient. Especially with large B2B catalogues of thousands of items, that customer-specific restriction is a genuine benefit, not just a filter.

The real gain is that price negotiation by email disappears. When every business customer sees exactly their conditions after login, sales no longer has to communicate prices by hand and every change takes effect immediately and identically everywhere. That makes the process not only faster but also less error-prone, because the source of truth is unambiguous.

Pricing complexity requires a rule engine

Tiered prices, discount groups, time validity, and customer-specific overrides cannot be managed manually. Shopware's pricing rule engine handles the evaluation logic automatically — provided it is correctly configured and synchronised with the ERP.

Catalogue filtering reduces complexity

When customers only see the products relevant to them, the shop becomes clearer and search more efficient. Especially for large B2B catalogues with thousands of articles, customer-specific catalogue restriction is a genuine value-add.

ERP remains master for prices

When prices are manually maintained in the shop, divergences from the ERP eventually arise. The cleanest solution is ERP-driven price synchronisation where the shop always reads from the ERP and never acts as the leading system.

Every customer, their price

With us you're always at the cutting edge of technology and benefit directly from our developer expertise. Together we analyze your shop, identify key areas and develop tailor-made solutions. Your goals and expectations are at the center of our work.

  1. Developers, not resellers

    Your shop is built by developers who really understand the code. We pass nothing to subcontractors.

  2. Shopware down to the detail

    Architecture, API integration and performance from hundreds of project hours.

  3. One team, every discipline

    Development, design and marketing come from one team that works without friction at the handoffs.

  4. Built for growth

    We build measurably for conversion, load time and revenue.

  5. Partner, not vendor

    We stay on after launch and keep developing your shop continuously.

Ready for your successful online shop?

Profile picture of Paul Kalisch, Executive Partner
Paul Kalisch
Executive Partner

Related articles from our blog

Frequently asked questions

Can we store prices for individual customers rather than groups?
Yes. Shopware 6 supports pricing rules at customer group level and at individual customer level. We configure the prioritisation logic so customer-specific prices always take precedence over group prices, and both can be driven from the ERP.
How is it ensured that business customers see their conditions after login?
Shopware's pricing rule engine automatically evaluates after login which price lists and discount groups apply to the logged-in customer. We test this logic in various scenarios — tiered pricing, time validity, basket conditions — before it goes live.
What happens if a customer tries to buy products not approved for their group?
Products not approved for a customer group are simply not visible after login — not in search, not in categories. Direct URL access shows either a 404 page or a configured message that the product is not available.