Product configurator: from options to a complete quote request

Key points

• Write the compatibility rules before the interface.
• Separate an indicative price from a confirmed quote.
• Send the configuration into your quoting system.

When a list of options becomes a sales problem

A customer asks for a custom product but does not mention the size, material or accessories. Your team comes back with questions, checks the combinations and redoes the quote. If these questions follow the same rules every time, a configurator can prepare the request before it reaches a salesperson.

Not every product needs a configurator. For simple variants, the options on the product page may be enough. The investment makes sense when the choice involves dependencies, calculations or information that significantly changes the quote.

Which rules need to be documented

Collect valid configurations, impossible configurations and exceptions your team has approved. Explain the dependencies: which accessory works with which variant, which size changes the material and which option needs a technical check. The person who knows the product must validate the rules.

Decide who updates them when the catalog changes. A configurator built on a file nobody maintains can offer discontinued combinations. Keep the version of the rules attached to each request, so your team can explain what the customer chose at that moment.

When you can show a price and when to ask for an evaluation

An automatic calculation needs a complete formula and current data. Separate product costs from delivery, installation or other work that depends on context. If some values cannot be calculated, make it clear that the price is indicative or still needs confirmation.

Do not use a precise-looking figure to hide an incomplete estimate. Customers should know which conditions can change the quote. For technical projects, a documented configuration sent for evaluation can be more useful than a wrong automatic price.

How to organize the choice on a phone

Ask for options in order of their dependencies and explain technical terms next to the field. When one choice invalidates another, say what changed and why. Do not silently clear the whole form. Show a summary the customer can review before sending.

Photos or drawings help when they clarify a real variant. An impressive visualization does not replace the product rules. Start with the steps needed for the decision, then add visuals if they improve understanding.

• Compatible options and validation messages.
• A configuration summary and the contact details needed.
• The conditions behind the price calculation.
• An identifier and version for the request.

What reaches your sales team

Send the configuration in a structured form, not just an email that is hard to interpret. Keep the choices, units and any files. Your colleague should be able to turn the request into a quote without re-entering everything.

Defining the handoff to your CRM or ERP is part of the project. Decide who picks up the request, where exceptions are checked and how the customer sees the next step. Confirming a request must not be confused with accepting an order.

How to scope a configurator with Webmate

Prepare one representative product, its rules and a few past quotes. Choose one product family for the first phase, so you can check the logic before including the whole catalog. Test normal combinations as well as invalid or incomplete ones.

Webmate can analyze the connection between the selection interface and your internal systems. The cost depends on the rules, catalog, calculation, presentation and integrations. A useful request for an estimate describes these components, not just the wish for a 3D configurator.

Frequently asked questions