In 2026, many manufacturers and wholesalers are revisiting a familiar question: should the product configurator be built directly into the online shop – or is a separate CPQ tool (Configure, Price, Quote) the better choice? Since Shopware rolled out native B2B features such as individual pricing, customer-group hierarchies and exploded-view drawings in June 2026, integrating configuration and quoting into commerce platforms has become considerably easier. At the same time, the market for specialised CPQ solutions that model complex product logic, broad variant ranges and rule-based price calculations continues to grow strongly.
For managing directors and sales leaders in mid-sized B2B companies, this is not a purely technical decision. It has a direct impact on sales efficiency, maintenance effort, time-to-market and total cost of ownership. This article offers five concrete criteria to help you choose between a shop configurator and a separate CPQ tool – factual, practical and to the point.
Criterion 1: Complexity of the product logic
The first question is: how complex is the product configuration? Is it about simple variants (colour, size, material) or about multi-level rule sets with dependencies, exclusions and dynamic calculations?
Shop-integrated configurators are ideal for manageable product variants. When customers choose from three to five options and the price is calculated linearly, the native functionality of modern shop systems is often sufficient. Shopware, Magento and Shopify Plus now offer solid base features for B2B use cases. The advantage: the customer stays in the familiar shop environment, the user experience is consistent, and checkout is seamless. The article Configurators in B2B: from enquiry to price in under 60 seconds shows what such a flow looks like in practice.
Separate CPQ tools play to their strengths as soon as the product logic becomes multi-layered. Examples include machines with hundreds of components, technical systems with dependencies between parts, or products whose price is composed of material costs, production time and logistics effort. CPQ systems offer rule engines, constraint solvers and 3D visualisations that standard shops cannot replicate.
Practical tip: if more than 20 percent of enquiries require individual clarification or manual recalculation, that argues for a separate CPQ tool. If the rate is lower, a shop configurator is often enough.
Criterion 2: Depth of integration into ERP and PIM
The second decision dimension concerns the system landscape. How deeply must the configurator be integrated into existing ERP, PIM and CRM systems – and how flexible are those systems?
Shop configurators usually work via standard interfaces (REST APIs, webhooks) and can be connected to common ERP systems relatively quickly. For mid-sized companies running SAP Business One, Microsoft Dynamics or JTL-Wawi, this is often the more pragmatic route. Product data flows from the PIM into the shop, and orders move back into the ERP. As long as the data structure is not too complex, this runs stably.
Separate CPQ tools offer deeper integration options, especially for complex product hierarchies, bills of materials and manufacturing parameters. They can access ERP data directly, check availability, calculate delivery times and transfer quotes to the CRM automatically. This increases data quality and reduces manual errors – but also requires more effort during initial integration. The article Shopware for B2B: 12 requirements you should check summarises which requirements Shopware covers in such scenarios.
Practical tip: if the ERP already manages detailed product configurations and bills of materials, a CPQ tool that builds directly on top of it is worthwhile. If the product data is well maintained in the PIM and the ERP logic is simple, a shop configurator will do.
Criterion 3: Maintenance effort and responsibilities
Who maintains the configuration logic – and how often do product variants, prices or rules change?
Shop configurators are usually looked after by the e-commerce team or the marketing department. Maintenance happens via the shop back end, often without IT support. That is efficient as long as the changes remain manageable. New variants can be created quickly, prices adjusted, images replaced. For companies with flat hierarchies and short decision paths, this is a clear advantage.
Separate CPQ tools generally require more technical know-how. Rule sets, dependencies and price calculations are often maintained by product managers or technical experts. This increases accuracy but also demands clear processes and responsibilities. Who maintains what? Who approves changes? Without clean governance, a CPQ tool can quickly become a bottleneck.
Practical tip: if product changes are frequent and short-notice (e.g. seasonal variants, promotional prices), a shop configurator is more flexible. For complex, long-term stable products with few changes per year, a CPQ tool is the better choice.
Criterion 4: Total cost of ownership
The fourth dimension is cost – not just at purchase, but across the entire lifecycle.
Shop configurators are usually cheaper to set up. Many shop systems offer native configurator features or low-cost plugins. Ongoing costs remain manageable, as there is no separate licence, no additional hosting and no dedicated maintenance. For mid-sized companies with a limited budget, this is often the decisive factor.
Separate CPQ tools incur higher initial costs (licence, implementation, integration) and ongoing fees. In return, they offer more functional depth, better scalability and often support from specialised vendors. In the long run, they can significantly increase sales efficiency and eliminate manual processes – which amortises the higher costs. The article CPQ in B2B: 49% more quotes through Configure-Price-Quote shows how large this efficiency lever can be.
Practical tip: calculate total cost of ownership over three years. Account not only for licence and integration costs, but also for internal resources (maintenance, training, support) and the value of manual work saved. A CPQ tool pays off when it saves at least half a full-time position in sales per year.
Criterion 5: Time-to-market and agility
The fifth criterion concerns speed: how quickly must the solution go live – and how flexibly must it respond to market changes?
Shop configurators can usually be implemented faster. A simple product configurator can be set up within a few weeks if the product data is clean. For companies that want to generate first sales quickly, this is a clear advantage. Agility stays high: adjustments can be made at short notice, and A/B tests are easy to run.
Separate CPQ tools take longer to implement – often three to six months, depending on complexity and integration depth. In return, they are more stable and scalable in the long term. Once the product logic is modelled cleanly, new variants and markets can be opened up faster. For companies with international expansion plans or a rapidly growing product portfolio, this is a strategic advantage.
Practical tip: if first sales are needed within six weeks, starting with a shop configurator is advisable. If a long-term, scalable solution for complex products is required, investing in a CPQ tool is worthwhile – with enough time planned for implementation.
When each solution is the right one
The choice between shop configurator and separate CPQ tool depends on five factors: product complexity, integration depth, maintenance effort, total cost of ownership and time-to-market. There is no universal solution – but there are clear patterns.
A shop-integrated configurator is the right choice when:
The product logic is manageable (fewer than 50 variants, simple pricing rules)
Integration into ERP and PIM works via standard interfaces
The e-commerce team can handle maintenance independently
The budget is limited and quick results are required
The focus is on agility and short iteration cycles
A separate CPQ tool is the better choice when:
The product configuration is complex (multi-level dependencies, rule-based calculation)
Deep ERP integration and automated quoting processes are needed
Product managers or technical experts maintain the configuration logic
Long-term scalability and international expansion are planned
The ROI from manual work saved justifies the higher costs
Hybrid approaches as a third way
A third option that is gaining importance in practice is the combination of both worlds. Modern CPQ systems now offer APIs that integrate seamlessly into shop front ends. The customer configures in the familiar shop environment, while the CPQ engine handles the complex logic in the background.
This hybrid approach combines the advantages of both solutions: consistent user experience, fast time-to-market and, at the same time, the power of specialised CPQ software. However, it requires clean interfaces and clear responsibilities – both technical and organisational. This is especially true where custom items such as spare parts are mapped via interactive exploded-view drawings.
Practical tip: with a hybrid approach, clarify from the start which system leads (master data management). As a rule, the PIM should manage the product data, the CPQ tool the configuration logic, and the shop the customer interaction. Only then can data inconsistencies and unnecessary maintenance effort be avoided.
The role of Shopware and other platforms
With its June 2026 release, Shopware has raised the bar for native B2B features considerably. Customer-specific prices, hierarchies, exploded-view drawings and extended variant logic are now built in. For many mid-sized companies, this makes separate CPQ tools unnecessary – at least for standard products. The article Individual Pricing in Shopware 6.7.8: scaling negotiated prices describes how negotiable prices can be modelled at scale.
Other platforms such as Magento (Adobe Commerce), Shopify Plus and SAP Commerce Cloud are following suit. The trend is clear: commerce platforms are increasingly integrating CPQ features to map the entire B2B quoting process. At the same time, specialised CPQ vendors remain relevant – especially for highly complex products and international group structures.
For mid-sized companies, this means: the choice of shop platform influences the CPQ decision. Those who rely on Shopware, Magento or Shopify Plus should first exhaust the native features. Only when these reach their limits is it worth looking at separate CPQ tools.
Decision guide: a checklist for practice
To structure the decision, a simple checklist helps.
Arguments for a shop configurator:
Fewer than 50 product variants, simple pricing logic
Standard ERP integration is sufficient
The e-commerce team can take over maintenance
Limited setup budget
Go-live required in under three months
Arguments for a separate CPQ tool:
More than 100 product variants, complex dependencies
Deep ERP integration and bill-of-materials management needed
Technical experts available for configuration maintenance
Higher budget with a clear ROI focus on process efficiency
Long-term scaling and internationalisation planned
Arguments for a hybrid approach:
A mix of standard and custom products
A fast start desired, but long-term scaling important
An existing system landscape with ERP, PIM and CRM
A team with the technical competence for interface management
Flexibility in budget and timeline
The checklist does not replace an individual analysis, but it provides orientation for the first conversations with service providers and internal stakeholders. The decisive step is to assess your own product logic, system landscape and sales strategy honestly – and only then to talk about technology.
