Product Configurator Cost: What Drives the Price?
What a product configurator costs depends mostly on the rules and data behind it, less on the interface. On top come 3D models, integrations, the output of quote or order, maintenance and the choice between licence and build. The article shows how to read a proposal and gives our starting price of €500 as the only figure.
Quick answer
How much does a product configurator cost? We do not publish a general market range because we have no reliable source for one. A configurator or calculator starts at €500 with us; the final price depends mostly on the pricing logic, less on the interface, and we state scope and price in writing before work begins. The €500 is a starting point, not an average and not a market figure. Six factors set the price: rules and data, presentation (calculator, 2D or 3D with models), integrations, output of quote or order, operation and maintenance, and the choice between licence and build.
Why prices online are hard to compare
Whoever searches for costs finds ranges from providers, agencies and blogs. The ranges we looked at name neither source nor method, often come from providers who sell something themselves, and mix items, for example renderings (finished images) and interactive 3D. A figure without a statement of what it includes is not usable as a budget. So we do not publish a market range. We explain what the price depends on and show how to check a proposal against those factors.
Six factors that set the price
The breakdown is ours. Each factor can be requested as a separate item in a proposal.
Rules and data
Number of options, dependencies between them, price source and the effort of capturing the rules. The biggest factor, and one you cannot see on a surface.
Presentation
Calculator, images and layers, or 3D. With 3D, models are added, a separate item.
Integrations
Shop, ERP, CRM, production: each interface is a sub-project with failure cases of its own.
Output
Display on screen only, or a record, a PDF quote with calculation, handover to order or production.
Operation and maintenance
Hosting, changes to prices and rules, new products, updates.
Licence or build
Two kinds of cost: an ongoing fee plus setup versus a one-off effort plus operation.
Rules and data: the item you cannot see
Number of options and their dependencies
A list of independent options takes little effort. Every rule of the form "if A, then not B" has to be formulated, implemented and tested. The effort grows with the number and entanglement of the rules, not with the number of buttons.
Price source
Where does the truth about the price live: in a price list maintained by hand, in the ERP or in the manufacturing parameters? If the configurator calculates from parameters instead of a copy of the price list, the calculation logic is more work but stays correct when prices change. That is why we capture the calculation first.
Preparing the data
Prices, dimensions and parts lists often sit in Excel files and in the heads of individual employees. Capturing them is work that arises in every case, whether plugin, rental or custom build. It just sometimes does not appear in the proposal.
Special cases
Exceptions that are clarified by phone today are further rules. That is why we test the calculation logic against quotes your team has already calculated by hand; if the results differ, the rule is clarified first.
Presentation: calculator, 2D or 3D
Calculator
Numbers in, price out. Presentation costs least here; the effort lies in the pricing logic.
2D: images and layers
The images have to be produced and maintained. Their number grows with the product of the option values for single images, and only with the sum for independent layers. How many images you need can be counted before the proposal.
3D: an item of its own
Each product needs a model prepared for the browser. With us, preparing the 3D models is not included in the entry price of €500. The number of products and variants determines this item, and it recurs with every new product. On top come tests on real devices and a fallback for devices where 3D does not start. The interface is rarely the main driver of cost, but 3D models are an item of their own and should appear separately in the proposal. When 3D pays off at all is explained in our article on WebGL.
Integrations and output: what happens after the click?
Integrations
Shop, ERP, CRM, production: each interface is a sub-project of its own with failure cases of its own, for example when the ERP rejects a price the configurator has calculated. Count the systems before you request proposals.
Output
If the configurator only shows a number, that is the smallest variant. If it is to produce a record, output a quote as a PDF with calculation and layout, or hand over by API to CRM, order management or production, each is additional effort. But it saves retyping, which is where errors arise later. Ask in the proposal: what is the result, and where does it go?
Licence or build: two kinds of cost
Licence or rental
You pay on an ongoing basis for the platform or plugin. Setup (capturing rules, loading data, adapting the interface) still arises. Calculate over the term rather than with the monthly price, and clarify before the contract whether rules, prices and models can be exported completely and where the data is stored. The input form often collects personal data: hosting location and data processing agreement belong to data protection.
A build to your rules
You pay once for implementing your rules and afterwards for operation and maintenance (hosting, changes, new products). Ask to what extent your team can change prices and rules itself and who owns code, models and data.
Which model is cheaper?
Neither in general. This is a consideration, not a measurement: it depends on the term, on how often rules and prices change, and on whether a standard product models your rules. Which model fits when is in the article on plugin, software or custom build.
Where the costs arise
-
One-off
- Capture and test rules and pricing logic
- Interface, plus models for 3D
- Integrations and output (PDF, CRM, production)
- Setup for rented software
-
Ongoing
- Licence or rental (for rented software)
- Hosting and operation
- Changes to prices, rules, products
- Updates of shop, plugin and browsers
Thought example: two configurators, two different prices
Configurator A
Three independent options, price from base price plus surcharges, result as an e-mail to sales. Few rules, one price list, no interface to other systems, no image.
Configurator B
Dimension input, dependencies between options, 3D layout, price from manufacturing parameters, quote as PDF and handover to the ERP. Many rules, several data sources, models, two interfaces.
What the comparison shows
Both are called "configurator", but they differ in each of the six factors. A single price for "a configurator" says nothing about that. This is a thought example without a price. Our closet configurator demo (dimensions, 3D layout, price, PDF quote) resembles B in presentation and output; it is not connected to an ERP or production, and its prices are sample values, not a price reference.
How to read a proposal: eight questions for the provider
1. What is included in the price?
Rule capture, data preparation, interface, 3D models, integrations, tests: each item separately, otherwise proposals cannot be compared.
2. What scope does the proposal assume?
Number of options, rules and products, and what an extension costs.
3. Where does the price in the configurator come from?
Price list, ERP or manufacturing parameters, and who reconciles them when prices change.
4. What is one-off, what is ongoing?
Ask for both columns separately and the term over which the provider calculates.
5. Who owns rules, models and data?
And in which format do you get them back if you change provider.
6. Who changes prices and rules after launch?
Your team in an interface or only the developer, and what a change then costs.
7. What happens when an interface rejects?
For example when the ERP does not accept a price: who sees the error, and what happens next?
8. How is the calculation logic tested, and when is the price in writing?
Ideally against quotes your team has already calculated by hand, and before work begins.
Try it in the browser
- Demo - not a client project 3D ring configurator in the browser 3D example: a ring configurator on WebGL with two models, three metals, five stones and three carat weights. Its prices are sample values, not a price list. What the demo shows and what it does not
- Demo - not a client project 3D closet configurator in the browser 3D example, closet configurator: enter dimensions, see the 3D layout, calculate the price, output a quote as a PDF with calculation and layout. Prices, catalogue and dimensions are sample values, not a price list. What the demo shows and what it does not
- Demo - not a client project 3D terrace configurator in the browser 3D example, terrace configurator: enter dimensions, see the 3D layout, calculate the price, output a quote as a PDF with calculation and layout. Prices, catalogue and dimensions are sample values, not a price list. What the demo shows and what it does not
Where proposals get more expensive later
Note on sources
We have no statistics on this. The list names places where assumptions in a proposal remain untested.
Incomplete rules
If a rule is missing in the proposal, it shows up during testing and someone has to add it.
Missing data
Prices or dimensions that nobody can supply delay the start until someone collects them.
3D added later
Whoever starts with a calculator and later wants 3D orders models and a new interface. Decide this up front.
Wish lists
A custom build is justified by rules and data that a standard cannot model, not by wish lists. Every feature without a rule behind it is effort without benefit.
Next step: write the rules down, then compare proposals
Write down for one product on one page: options with values, rules in the form "if A, then not B", price formula with its source, systems to be connected and the handover target. Give this page to every provider and ask for a proposal with the items from the six factors, split into one-off and ongoing. Then compare item with item, not total with total. A configurator or calculator starts at €500 with us; for your rules we state scope and price in writing before work begins. The overview of what a configurator is and which route fits you is in the article "What is a product configurator?".
Key takeaways
- We do not publish a general market range; we lack a reliable source for one. Our starting point: from €500 for a configurator or calculator, not an average.
- Six factors set the price: rules and data, presentation, integrations, output, operation and maintenance, licence or build.
- The biggest factor lies in rules and price source, not in the interface; 3D models are an item of their own.
- Ask for proposals with individual items, split into one-off and ongoing, and compare items, not totals.
- Without written rules every proposal is an estimate; the rules page is your yardstick.
FAQ
How much does a product configurator cost?
What influences the cost most?
What does 3D in a configurator cost?
Is a plugin cheaper than a custom build?
How long does it take to develop a configurator?
What should a proposal for a configurator contain?
Write the rules down first, then compare proposals.
We go through with you how your price comes about today and which of the six cost factors is decisive in your case.
We reply from the same address or phone number you leave here.
Or write to us directly: info@itcarrot.com +49 176 74358651