Visual CPQ: configure, price and quote in 3D

Selling a configurable product means answering the same question hundreds of times: “what does this build cost, and will it work?” Most manufacturers still answer it with a sales engineer, a spreadsheet and an email thread. Visual CPQ answers it while the buyer is still configuring.

What visual CPQ is

CPQ stands for configure, price, quote. Classic CPQ tools handle the commercial side well: rules, price lists, discounts and quote documents. But the buyer sees a form, a list of dropdowns and a PDF. They still do not know what the product looks like.

A product configurator does the opposite. It shows the product and the options, but often stops at “request a quote”. For a deeper split of the two, read our guide on CPQ vs product configurator.

Visual CPQ joins the two:

• The buyer configures the product in real-time 3D
• A rules engine blocks combinations that cannot be built
• Your pricing logic calculates the price at every step
• The finished configuration becomes a quote with every specification

The result is a quote that is complete, priced correctly and buildable, before anyone on your team touches it.

Why manual quoting stops scaling

Manual quoting works at low volume. A few requests a week, one price spreadsheet, one person who knows the rules. As volume grows, four problems compound.

Speed. Every request waits for someone who understands the product. In B2B, quote speed is often the tiebreaker between vendors of similar quality.

Accuracy. Pricing rules spread across spreadsheet versions and memory. A volume break gets forgotten. A surcharge is missed. You either lose margin or have an uncomfortable correction call.

Capacity. Your quoting capacity is capped by the number of people who can do it. Growth means hiring just to keep up with requests.

Data. Email quotes produce no structured data. You cannot see which configurations are popular, which options are requested most or where deals stall.

Configure-to-order vs engineer-to-order

Most manufacturers sell two kinds of product, and visual CPQ treats them differently.

Configure-to-order (CTO) products are built from known components with known rules. A conveyor with set belt widths, drive options and frame materials is CTO. Every valid combination can be encoded, so the CPQ handles the full quote automatically.

Engineer-to-order (ETO) products need custom engineering for each order. No configurator replaces your engineers here. What it can do is handle the front-end scoping: the buyer configures what is standard, and your team receives a structured brief instead of a blank intake form.

Most catalogs mix both. A good visual CPQ quotes CTO builds instantly and routes ETO requests with full context attached.

How the pricing logic works

Before quoting can be automated, the pricing model has to be explicit. In practice we map:

• Base price for each product or module
• Material and finish modifiers
• Dimension formulas, for example price per meter or per square meter
• Quantity and volume breaks
• Add-ons, accessories and installation options
• Customer or dealer pricing tiers
• Exceptions and special cases

Then the dependencies: which finishes exist for which material, which accessories need which base unit, which sizes trigger a different tier or a structural change. Once these rules are written down, they run the same way for every buyer, every rep and every region.

If the mapping shows that your pricing has too many one-off judgment calls, that is useful to know early. Those cases can still route to a person, with the rest of the quote already filled in.

What the quote contains and where it goes

A visual CPQ quote is structured data, not just a PDF. A typical output includes:

• Every selected option and dimension
• Component codes or part numbers
• Quantities and the calculated price, with the breakdown
• A visual of the configured product
• Buyer and account details

That data goes where your team already works. For B2B, it usually becomes a quote record in your CRM for review and approval, and later an order in your ERP with a ready bill of materials. No one re-types a spec, so no one introduces a typo into it. If you sell through dealers, the same flow gives them a self-service portal with their own pricing tier instead of a phone line.

Manufacturing vs ecommerce quoting

Visual CPQ is not the same as a consumer product configurator. The priorities differ:

	Manufacturing and B2B	Ecommerce
Main user	Sales reps, dealers, procurement	End consumers
Output	Quote, BOM, CRM and ERP record	Cart item and order
Rules	Technical compatibility, tiers	Mostly visual options
Pricing	Volume breaks, account pricing	Fixed retail price

The line is blurring, though. Industrial buyers now expect the same clarity they get when buying online. Our article on B2B 3D product configurators covers how 3D changes complex sales conversations. If you sell configurable products direct to consumers, a custom 3D configurator with live pricing and add to cart is usually the better fit than CPQ.

When visual CPQ makes sense

Visual CPQ is worth it when:

• Your products have dozens of options with real dependencies
• Quotes need a sales engineer today and take days
• Invalid or misquoted orders have cost you margin or rework
• You sell through dealers or distributors who call you for prices
• Your CRM or ERP data is re-typed from emails

It is probably too early if you quote a handful of standard products a week and pricing never changes. In that case, start by cleaning up the order process: our guide on eliminating manual quoting shows the first steps.

How Eyedex builds it

Eyedex builds visual CPQ as a done-for-you service, the same way we build ConfiguraThor. We model your product in 3D, encode your options, rules and pricing, connect the output to your CRM or ERP, then host and support it. When your prices or catalog change, we update the rules. One custom quote covers the build, hosting and monthly support.

Want to see it on your own product? Request a CPQ demo and bring one product family with its price list.