Manufacturers and wholesalers that built on the Shopware B2B Suite face a turning point in 2026: the plugin is now in maintenance mode only. With B2B Components and Individual Pricing (available since version 6.7.8), Shopware has created a successor that promises modern pricing logic. But what does that mean in practice for customer-specific price books, tiered discounts and negotiated prices? And how do you make the switch without stalling day-to-day sales?
This article lays out four actionable steps to move your B2B pricing logic to the new platform in a structured way. Acting now buys you predictability and avoids expensive last-minute fixes.
Why the Shopware B2B Suite is no longer being developed
For years, the Shopware B2B Suite was the standard tool for manufacturers and dealers that needed differentiated pricing models in a B2B context. It enabled customer-specific price books, flexible discount tiers and negotiated prices that are indispensable in wholesale. But as Shopware 6 evolved, the technical architecture changed fundamentally. The old Suite no longer fits the modular, API-first structure Shopware relies on today.
Since the start of 2026 it has been clear that the B2B Suite will receive no new features. Security updates and critical bug fixes are still shipped, but strategically Shopware has set the course toward B2B Components. For companies this means: anyone still working on the old Suite risks operating with outdated technology over the medium term. New features, integrations and performance improvements remain out of reach. The question is no longer whether to migrate, but when and how.
What changes in pricing logic with B2B Components
Moving to B2B Components brings not just a new interface but a fundamentally different architecture for pricing logic. The Shopware B2B Suite used its own pricing module that operated largely separately from the platform's standard pricing rules. B2B Components, by contrast, integrate directly into the core pricing system of Shopware 6 and extend it with B2B-specific functions.
The new Individual Pricing module takes the central role: it still allows customer-specific prices, tiered discounts and fixed prices, but based on Shopware's native data structure. That has advantages, but it requires translating your existing pricing logic. Percentage discounts that were stored as a standalone rule in the old Suite now have to be modelled as a price rule in the new system. Negotiated prices that used to be maintained manually can now be synced directly from the ERP via API interfaces.
Anyone who relied on complex discount chains or special conditions for customer groups must remodel that logic. The good news: B2B Components offer more flexibility and better performance. The challenge: the switch requires clean data migration and clear testing processes so that no pricing errors occur in live operation.
4 concrete steps to migrate your pricing logic
1. Take stock: which pricing rules are you using today?
Before you migrate, get a complete overview of your existing pricing logic. Document all customer-specific price books, tiered discounts, fixed prices and special conditions. Check which rules are actively used and which have grown historically but are no longer relevant. A clean inventory saves migration effort later and prevents outdated logic from being carried into the new system.
2. Mapping: translate your pricing logic into the new structure
Create a mapping table that links each existing pricing rule to the corresponding function in Individual Pricing. Tiered discounts from the old Suite become quantity-based pricing rules, customer-specific prices become customer-specific prices. Percentage discounts can be modelled as price rules with a percentage modifier. This step requires technical understanding but should be done together with sales and controlling to ensure the business logic is transferred correctly.
3. Test environment: migrate a sub-section first
Set up a test environment with Shopware 6.7.8 or higher and migrate only a representative slice of your pricing logic first. Choose a customer group or product category that covers typical pricing scenarios, and test all relevant processes: ordering, discount calculation, invoicing. Involve your sales team and have them run through real ordering scenarios. That is the only way to uncover discrepancies before they cause damage in the live system.
4. Go-live planning: migrate step by step, not all at once
Plan the migration in stages rather than as a big-bang project. Start with a pilot customer group, monitor price calculation closely and gather feedback from sales. Only once all processes run stably should you extend the migration to further customer groups. Keep capacity available for adjustments in the first weeks after go-live and communicate transparently with your customers if delays occur.
Conclusion: act now, before the pressure mounts
The Shopware B2B Suite has had its day. Anyone still relying on it will lose touch with new features over the medium term and risks security gaps. The move to B2B Components and Individual Pricing is not an end in itself but an investment in a future-proof platform. With a structured inventory, clean mapping, thorough testing and a step-by-step migration, pricing logic can be transferred safely.
Companies that act now can plan and test the switch calmly. Those who wait until the old Suite no longer receives updates will end up under time pressure and have to budget for higher costs. Use the remaining time to put your B2B pricing logic on a solid footing. Your customers and your sales team will thank you for it.
Recommendation: Have your existing pricing logic analysed by an experienced Shopware partner and draw up a concrete migration roadmap. That way you keep control of costs, timeline and risks.
