Guide · CPQ

What is CPQ and when does it need a visual configurator?

CPQ is the software that turns a product with options into a valid configuration, a price and a quote or order line. It sits between the CRM and the ERP. When the buyer has to understand the configuration without knowing product codes, the CPQ needs a visual layer on top.

Mori Maison team · Reading 7 min · Updated: November 2026

What CPQ is

CPQ stands for Configure, Price, Quote. It is the software that turns a product with options into a valid configuration, a price and an order line. It usually sits between the CRM, where the opportunity lives, and the ERP, where the order and the bill of materials land.

A CPQ is not a catalogue and not a store. It is the layer that decides which combinations are valid, what each one costs and which document comes out at the end. A product with sizes, finishes and modules needs that layer; a product with one size and one colour can live without it.

It has three parts. Configuration rules define what combines with what and which sizes are allowed. Pricing rules calculate the amount from the configuration, with surcharges and channel discounts. Quote generation produces the document and the order line that travels onward.

What it solves for a manufacturer with a configurable catalogue

It solves three concrete problems: a sales rep cannot sell an impossible combination, the price comes from factory rules instead of an estimate, and the order reaches the ERP without manual retyping. In a catalogue with many variants, those three failures cost more than the software.

The first is the configuration error. When the rules live in two people’s heads and in a spreadsheet, every rep interprets the limits differently. The CPQ writes them once and applies them to everyone.

The second is price. A price calculated by hand is calculated differently each time. With rules, the amount depends on the configuration, the channel and the volume, and it can be explained to the buyer line by line.

The third is the order. If the configuration is retyped into the ERP, typos appear and the factory has to send it back. An order line generated from the configuration removes that step.

CPQ, ERP variant configurator and 3D configurator: the differences

All three configure a product, but not for the same person and not with the same appearance. The CPQ is a form of lists and codes for the sales rep. The ERP configurator is an extension of the management system. The 3D configurator is a view of the product for the buyer.

The classic CPQ is a form. It works well for someone who knows the product and thinks in references, and poorly for someone who has to imagine how the combination looks. That is the gap the visual layer fills.

The ERP configurator has a different strength and a different limit: it is the truth of the system, but it is usually designed for internal use. Many ERPs include a variant configurator that works well when the catalogue is standard and exceptions are few.

CPQ, ERP variant configurator and 3D configurator
CriterionCPQERP configurator3D configurator
Who uses itSales and technical officeTechnical office and adminDistributor or end buyer
What it showsLists, codes and fieldsVariants and system referencesThe product in 3D, at scale
Where the rules liveInside the CPQIn the material and variant masterReads or mirrors the CPQ or ERP rules
What it outputsQuote and order lineReference and bill of materialsConfiguration with reference, options and price
When it is enoughThe rep knows the productThe catalogue is standard, with few exceptionsThe buyer has to see it before deciding

When a CPQ needs a visual layer

A visual layer is needed when the person configuring does not know the codes: distributors, specifiers or the end buyer. It is also needed when the product is bought for how it looks and a list of options is not enough. The clearest signal is the phone call to the factory to check whether a combination exists.

None of these signals forces you to replace the CPQ. The answer is almost always to add a view on top, not to remove the system that already calculates the price and produces the order.

  • Distributors call the factory to check combinations the system should already validate.
  • Orders arrive with combinations the factory cannot produce.
  • The product is bought for how it looks: sofas, kitchens, wardrobes, contract furniture.
  • Sales reps configure on behalf of the client, with the client in the room.
  • Option lists are so long that nobody finishes them on a phone.
  • Price depends on the configuration and the buyer wants to see it while choosing.
  • The catalogue grows and every season brings a new finish or module.

How a 3D configurator connects to the CPQ or the ERP

The connection runs through data, not a magic integration. The rules live in one place, usually the CPQ or the ERP, and the 3D configurator reads or mirrors them. When the buyer finishes, it returns the configuration as reference, options and price. What can be done depends on what the ERP exposes.

There are two routes. The first reads the rules in real time through an API: the configurator asks the CPQ whether a combination is valid and what it costs. The second mirrors the rules inside the configurator and syncs them when they change. The first avoids duplicating the truth; the second works when the source system has no useful API.

The exchange can also be a file. It is not elegant, but for a catalogue that changes twice a year it is enough, and it avoids opening the ERP to the internet. Either way, the configuration comes back with an identifier, the chosen options and the calculated price.

It is worth saying plainly: the integration depends on what the ERP or CPQ exposes. If the system only allows a nightly CSV export, the configurator works at that pace. If it exposes nothing, the configuration leaves as a PDF quote and someone retypes it, which is exactly what the project meant to avoid.

Where to start

Start with one product family, not the whole catalogue. Write down the rules that currently live in people’s heads, check the price against the factory and publish a pilot with one product. That pilot teaches more than a two-year plan.

Writing the rules is the first step of any project, with or without a CPQ. What combines with what, which sizes are allowed, what surcharge each finish carries, which lead time changes. If that list does not exist, the software only automates a confusion.

The pilot does three things: it shows whether the rules are complete, whether the price matches what the factory would quote, and how a real distributor uses it. Then you decide whether the visual layer extends to the rest of the catalogue or stays with that family.

Frequently asked questions

What does CPQ stand for?

Configure, Price, Quote. It is the software that validates a configuration, calculates its price and generates the quote or order line.

Are CPQ and a 3D configurator the same thing?

No. A CPQ works with rules, prices and documents, usually for the sales rep. A 3D configurator puts those same rules behind a view of the product for the distributor or the buyer. They can run separately or connected.

Do I need a CPQ if my ERP already configures variants?

Not always. If the ERP configurator covers the combinations and the team knows them, it may be enough. A CPQ adds value when there are channel pricing rules, complex quotes or many reps configuring.

Does a 3D configurator replace the CPQ?

No. The 3D configurator does not own the rules or the price: it reads or mirrors them and returns the configuration. The CPQ or the ERP remains the source that decides what is valid and what it costs.

Can it connect to any ERP?

It depends on what the ERP exposes. With an API the exchange is direct; with periodic exports it works with a delay; with no access, you are left with a PDF and manual retyping. Check before promising anything.

Where do I start if the rules are in spreadsheets?

Write those rules as an ordered list and validate it with the factory. That is the previous step for a CPQ and for a configurator. Without that list, any software inherits the contradictions of the spreadsheets.

Related service

A visual configurator on top of your rules, not instead of them

We design 3D configurators that read the rules of your CPQ or ERP, show the product and return the configuration as an order line. No monthly fee, and the code and models stay with you.