Scenarios and feasibility
Business goals, user groups, use cases, constraints and success criteria.
Configurators and CPQ on your product data.
Selection tools, configurators and quotes built on your product data and connected to PIM, ERP and CRM.
When a shop is not enough
A complex product cannot be sold with a list of variants.
When the choice depends on technical parameters, compatibility, conditions of use or quoting rules, the user needs guidance. We design the logic that turns product knowledge into a repeatable selection process.
- Sales reps spend hours explaining options and checking compatibility.
- Customers choose wrong combinations and orders come back.
- Filters in the online catalogue cannot express dependencies between options.
- Custom products can only be presented through a configurator.
- Quotes are built by hand in spreadsheets.
Our work in numbers
300+ projects, from stores to configurators.
Figures from our own projects.
- 70+PIM and e-commerce implementations
- 10M+SKUs in our clients' systems
- 300+projects delivered
- 2010operating since
- 35+PIM implementations
- 30+experts and consultants
- Pimcore Platinum Partnerone of two Platinum partners in Poland
- Ergonode partnerand we implement Akeneo
Sources: LemonMind, November 2026
How it works
From product data to a valid offer.
The tool reads products from the PIM and prices from ERP. The rule model decides which options fit together.
Data
ERP
price lists, discounts, terms
PIM
products, parameters, components
into the rules
Rules
Rule model
what fits together and what does not
- parameters
- dependencies
- compatibility
- exclusions
valid options
Selection
Configurator or CPQ
questions, steps, a valid configuration and a price
prices and terms from ERP, orders back to ERP
ends as
Result
- Product list
- Quote
- Order
- CRM record
orders back to ERP
prices and terms from ERP
Compare
Selection program, configurator or CPQ?
The three tools differ in what the user gets at the end. Many projects start with one and grow into the next.
| Criterion | Selection program | Product configurator | CPQ |
|---|---|---|---|
| Result | A list of matching products or components | One configured product, often with dimensions or a visual | A configuration with a price and a quote |
| Typical user | End customers and installers | End customers, trade professionals and designers | Sales reps and dealers |
| Data it needs | Product features and compatibility rules | Components, relations, dimensions and rules | Rules plus price lists, discounts and terms |
| Typical output | Product list, PDF, request for quote | PDF design, e-mail, order | Quote, order, CRM record |
Comparison prepared by LemonMind, October 2026. More in our e-commerce and CPQ articles.
Which tool does your product need?
30 minutes, no obligation. We look at your products, rules and users and tell you where to start.
Scope
What a configurator project covers.
Product and rule model
Parameters, dependencies, compatibility, exclusions and variants, and the rules for building a valid configuration.
Selection UX
Questions, steps, hints, validation and the way results are shown, fitted to the users' knowledge; experts and newcomers can get separate paths.
Configuration and quoting
Configuration rules, the data needed for pricing, and the result as a specification, a PDF or a quote.
Integrations
Connections with PIM, ERP, CRM, e-commerce and product documentation.
Tests, launch and growth
Test scenarios, rule validation, launch, and how data and logic are maintained afterwards.
How the project runs
Four steps from scenario to a working tool.
- 01
Feasibility and scenarios
Users, decisions, rules, data sources and the expected result.
ResultAgreed scenarios and expected results. - 02
Rule model and prototype
The product model, the selection logic and a prototype of the main user paths.
ResultA rule model and a tested prototype. - 03
Implementation and integrations
We build the tool, connect it to your systems and test it on real scenarios.
ResultA working tool on real scenarios. - 04
Launch and growth
Rules validated, team prepared, and a plan for maintaining data and logic.
ResultValidated rules and a maintenance plan.
Case studies
Product data that drives the choice.
Product selection tool
Heatpex
An online selection tool for the Heatpex Aria ventilation system: engineers design a system, save projects and download a PDF, and Heatpex gets B2B leads.
Read case study
Product websites and shop
Flowair
A website and online shop for the Slim air curtain and a dedicated website for the Rooftop Cube, both built on Pimcore for an HVAC manufacturer.
Read case study
Product configurator
Laguna
An online configurator for Laguna sliding door systems, built on a PIM and a headless CMS, for carpenters and designers.
Read case study
PIM and composable commerce
VOX
Pimcore as the foundation for product data management and a composable commerce architecture.
Read case studyFAQ
Before we start a configurator project.
What is the difference between a selection program, a configurator and CPQ?
A selection program leads the user from needs and parameters to a list of matching products or components. A configurator builds one product from compatible options, often with dimensions or a visual. CPQ (configure, price, quote) adds prices, discounts and a quote for the sales team or dealer. More in how CPQ benefits your business and sales team.
When is a normal online shop enough?
When products can be chosen with filters, without dependencies between options. When the choice depends on technical parameters, compatibility or quoting rules, the user needs guidance, and a selection program or configurator gives it.
Do we need a PIM before building a configurator?
Not always, but the configurator is only as good as its data. With many components and relations, a PIM keeps them in one place and the configurator reads them through an API, as in the Laguna configurator. We often build configurators on Pimcore, which stores components, relations and price lists and serves them through an API.
Which systems can a configurator connect to?
PIM, ERP, CRM, e-commerce and product documentation. A typical flow takes product data and rules from the PIM, prices from ERP, and sends the result as a quote request, an order or a PDF.
Can we start with one product family?
Yes, and we recommend it. A first version for one product family shows the value and the effort for the rest of the range.
How long does building a selection program or CPQ take?
It depends on the number of products, rules and integrations. We give a timeline after a feasibility analysis, which defines the users, rules, data and the scope of the first version. Background: the evolution of CPQ technology.
Olgierd MrozikCEO, LemonMind
Start with a scenario
Let's check whether a configurator solves the right sales problem.
A short feasibility analysis defines the users, rules, data, integrations and the scope of the first version before full development starts.
30 minutes. The calendar opens in a new tab.
- 2010 founded
- 300+ projects
- 70+ PIM and e-commerce implementations