Guide · 3D configurators

What is a 3D product configurator?

A 3D product configurator is a web tool where buyers choose sizes, materials, modules and finishes and see the result instantly. It only allows combinations the factory can build, calculates price when needed and returns the configuration as an order line. It is built for manufacturers with a wide catalogue and rules of their own.

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

What a configurator does, and what it does not

A configurator answers one question: what can a buyer order, and what does that combination cost? It is not a 3D viewer and it is not a catalogue of photographs. The difference is the rules — which combinations exist, which can be built, and which are simply not for sale.

A viewer shows a model and lets you spin it. A configurator also knows that a 240 cm sofa does not take a certain fabric, that a corner module moves the price, and that one finish adds two weeks to lead time. That logic turns a nice model into a sales tool: the buyer decides inside the factory’s limits and nobody has to correct the order afterwards.

Which is why the hard part is not the 3D. An optimised model looks fine anywhere. The cost sits in writing the rules with your product team, checking them against the shop floor and making sure the price and lead time on screen match what the ERP produces.

What can be configured

You configure whatever changes the reference, the price or the lead time: sizes, materials, colours, modules, extras and finishes. The limit is set by manufacturing, not by technology. If an option cannot be produced, it should not appear on the website.

  • Sizes: widths, heights and depths within the ranges the factory accepts, with a warning outside them.
  • Materials and finishes: fabrics, woods, lacquers, metals, stone, with their texture and gloss variants.
  • Modules and composition: parts that add up, rotate or drop out depending on the total size.
  • Extras: legs, arms, handles, lighting, mechanisms, drawers or accessories.
  • Compatibility rules: what pairs with what, and which combinations fall outside the catalogue.
  • Price and lead time: calculated per configuration, with surcharges explained before ordering.

The three technologies behind it

There are three ways to show a configured product: pre-rendered images, real-time WebGL in the browser, and pixel streaming from a cloud GPU. They differ in realism, page weight and cost per user.

Images win when there are hundreds of combinations and studio lighting matters, or when the audience browses from older machines. WebGL is the natural choice when the buyer needs to open, turn and combine without waiting. Pixel streaming is reserved for materials that demand a game engine and a context that can carry it: automotive, marine, or a large screen at a trade fair.

The three can coexist in one project: images for the catalogue and the product page, WebGL for the configurator, pixel streaming for the hero piece. Choosing one is not a marriage.

The three technologies of a 3D configurator
CriterionPre-rendered imagesReal time (WebGL)Pixel streaming
What the buyer seesPhotographs of the product in each combinationThe product rotating and changing liveInteractive video at game-engine quality
RealismMaximum: offline render with physical lightHigh: PBR materials, no complex reflectionsMaximum in motion, with engine lighting
Page weightHundreds of KB per viewTarget under 5 MB per productAlmost nothing on the device: it arrives as video
MobileWorks on any phoneTarget 60 fps on a mid-range phoneDepends on network and coverage
Cost per userZero: they are filesZero: the work happens on the deviceOne cloud GPU per connected user

What it needs to work

A configurator needs geometry, rules and an output. Geometry comes from CAD or is built from drawings and photos; rules come from your product team; the output is an order reference, a JSON payload or an ERP line. If one of the three is missing, the project stays a demo.

Typical inputs: STEP, IGES, SolidWorks and Rhino. We also work from existing render models when the geometry is good enough to avoid rebuilding. With no 3D at all, we build it from drawings, photographs or a physical unit. Output is glTF for the web, plus USD or FBX when the destination is another engine or a print pipeline.

Our performance targets are explicit: 60 fps on a mid-range phone and under 5 MB per product including textures. When a model cannot get there, we say so before the project starts and propose a simplified version, images, or fewer options on screen. A configurator that takes eight seconds to open loses the sale before it shows the product.

How the configuration reaches the factory

The configuration has to leave the website with everything the order needs: reference, sizes, finishes, extras and price. If that gets copied by hand, the configurator has only improved the presentation. Integration with ERP, CPQ or a store is what removes the transcription error.

There are three levels. The simplest builds an article reference from the configuration and sends an email or PDF with the breakdown. The middle one posts a JSON payload into your CPQ or ERP and generates the order line. The fullest writes directly into the system, with stock and lead-time validation.

The level is decided with your technical team in the first phase, not at the end. Changing it mid-project is the most expensive way to rebuild a configurator. It is also worth deciding up front who maintains the rules: if new fabrics arrive every season, someone needs to update them without calling a developer.

When it pays off, and when it does not

It pays off when the catalogue holds more combinations than a PDF can explain, when price depends on the configuration, or when orders are transcribed by hand. It does not pay off if the product has three variants, if buyers need advice in person, or if nobody will maintain the rules.

The opposite case is real too. A manufacturer with twelve fixed references and a sales force that sells on visits does not need a configurator: it needs clear spec sheets and good renders. Saying that early saves a six-figure project and a year of maintenance.

  • More than 50 variants per product, each changing price, lead time or material.
  • Pricing follows rules: modules, non-standard sizes, extras.
  • The configuration ends in an order, an ERP line or a CPQ.
  • Sales teams close deals with screenshots and email threads.
  • Size is the first cause of returns or complaints.
  • Distributors need to configure without calling the factory every time.

How long it takes and what you bring

A configurator for one product with material variants usually runs four to eight weeks. A wide catalogue with manufacturing rules and ERP integration runs ten to fourteen. The calendar depends more on your data and your rules than on programming.

On your side you need three things: models or drawings, the list of options with their rules, and one person with the authority to settle what can be configured. If that person does not exist, the project moves on assumptions, and assumptions are paid for at review.

The work runs in four stages: import and optimise geometry, write the combination and pricing rules, build the interface on top of your site, connect the output to your system. Each stage ends with something you can look at and test, not with a document.

How to choose without getting stuck

Choose on rules and ownership, not on the flashiest demo. Ask how many combinations it handles, how the rules get updated, what happens to the code if you change supplier, and what each user costs. A pretty demo on a closed engine can be the start of an expensive dependency.

  • Ask for the demo to use your product, not a showroom piece.
  • Ask who owns the code and the models at the end.
  • Check the real page weight on a mid-range phone.
  • Ask how a new fabric is added, and how long that takes.
  • Review which integrations already exist and which need building.
  • Get a closed scope in writing, including what is out of it.

Frequently asked questions

What is the difference between a 3D configurator and a 3D viewer?

A viewer shows a model and lets you rotate it. A configurator adds rules: which combinations exist, how price changes and what can be manufactured. The viewer is one part of the configurator, not the whole thing.

Do I need my product in 3D to start?

No. If CAD exists, we start there. If there are only drawings, photographs or a physical unit, we build the model. We also work from existing renders when the geometry is enough for the level of detail the web needs.

How many variants can a configurator handle?

There is no clear technical ceiling; the limit is performance and logic. Thousands of combinations work with images or with well-written rules. What does not scale is a separate mesh per variant: geometry is optimised and materials and modules change instead.

Does it work on mobile?

Yes. The target is 60 fps on a mid-range phone and under 5 MB per product. If the model cannot reach that, we say so before starting and propose images, a simplified version or fewer options visible at once.

Does it integrate with my ERP or online store?

Yes. The configuration can leave as an order line, an article reference or JSON into your CPQ. We work with whatever API you have; if there is none, we define the format with you and document it so your team can maintain it.

Who maintains the configurator when the catalogue changes?

Your team can, because the code and models are yours, or we can under a separate agreement. The important part is deciding early: if new fabrics arrive every season, someone has to update the rules without waiting for a development cycle.

Does a configurator replace the sales team?

No. It takes repeated questions — sizes, fabrics, lead times — off the salesperson and leaves the part that needs judgement: projects, contract work, specification. For many manufacturers the main gain is that distributors stop calling the factory.

Sources and references

Related service

Custom 3D configurators for manufacturers

We design and build the whole configurator: geometry, rules, pricing, ERP or CPQ integration. No monthly fee, and the code and models stay yours.