How to migrate B2B pricing tiers and customer groups into Shopware 6?

Question

Accepted Answer

Quick Answer

Migrating B2B pricing tiers and customer groups into Shopware 6 usually means rebuilding your pricing structure around Rule Builder, customer groups, and advanced prices. The hard part is not importing the data itself—it’s mapping old platform logic into Shopware’s pricing model without breaking tax handling, discounts, or customer visibility rules. The process below covers how to audit your current setup, structure pricing correctly, import customer assignments, and validate everything before launch.

Before You Start

✦ Full export of existing B2B pricing — you need current customer groups, tier logic, contract prices, and SKU mappings before building anything in Shopware.
✦ Clear tax strategy — B2B stores often migrate net pricing incorrectly, which creates checkout mismatches later.
✦ A staging environment — never test B2B pricing directly on production because indexing and cache rebuilds affect storefront visibility.

1

Audit existing pricing rules

Start by documenting how pricing currently works on the old platform. Most B2B stores have years of exceptions layered on top of each other—customer-specific prices, quantity breaks, ERP overrides, hidden categories, and negotiated discounts. If you skip this audit, you’ll rebuild bad logic inside Shopware instead of simplifying it. This is also the point where you decide which pricing rules should disappear entirely.

Export all customer groups and price lists
Identify duplicate or obsolete pricing rules
Map special contracts to real business cases

COMMON MISTAKE Teams often migrate every historic discount rule even when nobody still uses it. Clean this up first.

2

Build customer groups

Customers → Customer groups

Shopware 6 handles B2B segmentation through customer groups combined with Rule Builder conditions. Create groups based on actual commercial logic, not department names from the old system. For example, distributors, wholesalers, franchise partners, and VIP trade accounts should each have distinct pricing behavior. Keep the structure simple because every extra group adds maintenance overhead later.

Create groups for unique pricing behavior only
Assign tax display settings carefully
Separate B2B and B2C storefront visibility rules

IMPORTANT Mixing net and gross display settings across customer groups creates pricing mismatches at checkout.

3

Configure advanced pricing

Catalogues → Products → Advanced prices

Advanced prices are where most B2B pricing logic lives in Shopware 6. You can assign prices per customer group, quantity range, currency, or sales channel. This replaces many custom pricing plugins from Magento or WooCommerce. Keep your pricing hierarchy predictable. Customer-specific contract pricing should override group pricing, and quantity breaks should never conflict with promotional discounts.

Create quantity-based pricing tiers
Assign rules to the correct customer group
Test pricing priority order carefully

PRO TIP Build one master pricing matrix in a spreadsheet before importing anything. It saves hours during validation.

4

Import customer assignments

Settings → Import / Export

Once your pricing logic exists, import customers and map them to the correct groups. This step is usually automated through CSV imports or middleware connections from the ERP. Validate account assignments in batches instead of checking random users manually. Large B2B stores often have inherited account structures that no longer match real customer contracts.

Import customers into staging first
Validate customer group mappings
Check ERP sync behavior after import

IMPORTANT Incorrect customer-group assignment exposes the wrong prices publicly. This is one of the biggest B2B migration risks.

5

Validate storefront pricing

Final validation matters more than the migration itself. Log in as different B2B account types and test product pages, carts, quotes, and checkout totals. Pricing issues usually appear only when multiple rules overlap. Test edge cases like bulk quantities, VAT exemptions, and promotional discounts together. This catches the problems that tend to appear after launch weekend.

Test every major customer group
Validate quantity breaks and discounts together
Compare totals against the legacy platform

PRO TIP Keep screenshots of old-platform pricing during testing. It speeds up stakeholder approval dramatically.

Shopware B2B Migration Checklist

0 of 6 complete

Export all existing B2B price rules
Create simplified Shopware customer groups
Configure advanced pricing rules
Import customers into staging
Validate pricing for every account type
Compare totals against legacy platform

Mistakes Most Developers Make

! Migrating outdated pricing logic

What happens: Old pricing exceptions become impossible to maintain in Shopware.

Fix: Remove unused rules before migration starts.

! Mixing net and gross pricing

What happens: Customers see one total on product pages and another at checkout.

Fix: Standardise tax display settings across all B2B groups.

! Skipping real account testing

What happens: Hidden pricing conflicts appear only after customers place orders.

Fix: Test pricing using actual migrated customer accounts.

Key Takeaway

The short version: successful B2B pricing migration into Shopware 6 depends on simplifying your old pricing structure before importing anything. Use customer groups and advanced pricing for predictable rule handling, then validate every pricing combination in staging before launch. Most problems come from overlapping discounts, bad tax settings, or incorrect customer assignments. Clean up your pricing model first, then migrate the data second. Start with Step 1—that one alone handles most of it.

Magento (Adobe Commerce)

How to migrate B2B pricing tiers and customer groups into Shopware 6?

Audit existing pricing rules

Build customer groups

Configure advanced pricing

Import customer assignments

Validate storefront pricing

Shopware B2B Migration Checklist

Related Answers