New

Google AI Mode and AI Overviews opened in Türkiye on 18 February 2026. Check how your brand shows up in those experiences in three minutes. Start the check →

03.2 · 3D Product Configurator

Let customers see the product in their own configuration — and stop your sales team re-drawing it.

With high-variant products the real cost is not imagery but misunderstanding. A configurator makes options concrete in the customer's eyes and measurably reduces pre-quotation question traffic.

Direct answer

A 3D product configurator is an interactive experience where a visitor changes colour, material, size and module options in real time and sees the product in the browser. Built correctly, choices are bound to valid variant rules and the output feeds directly into a quotation or enquiry form.

Scope

  • Variant tree and rule definition (which option is valid with which)
  • Web-optimised 3D model (GLB/GLTF, LOD)
  • Material and colour system (PBR)
  • Real-time viewer and camera setup
  • Product code or configuration summary generation
  • Connection to the quotation/enquiry form
  • Dealer portal use and shareable configuration links
  • Mobile and low-memory device behaviour
  • AR viewing (USDZ/GLB) — where in scope
Product twin production flowFrom engineering file to sales asset: outputs derived from one master model. 01CAD / productSTEP, IGES, photos02SimplificationSurfaces, topology03Master assetPBR materials, rig04DerivationRender, animation05ChannelWeb, catalogue, fair
From engineering file to sales asset: outputs derived from one master model.

Required inputs

  • CAD files for the product family, or a verified 3D master model
  • Variant list and validity rules (which combinations can be built)
  • Material and colour references (RAL, fabric codes, finishes)
  • Product code logic and any pricing or code generation rule
  • Where the enquiry should land (form, e-mail, CRM)

Output

  • An embeddable configurator (component or page)
  • Web-optimised model set and texture package
  • Variant matrix document
  • Shareable configuration links
  • Configuration summary (PDF or form field)
  • Static derivatives: a catalogue image per variant

Process

Variant analysis

Which options actually sell, and which are valid together, is settled.

Model preparation

The master model is simplified and parts are grouped to the option logic.

Material system

A colour and texture library is built and bound to each option.

Interface

Selection flow, mobile behaviour and the loading experience are designed.

Integration

The configuration output is wired to a form, e-mail or dealer portal.

Performance test

First-render time is measured on a low-memory mobile device.

Typically six to fourteen weeks. The main driver is how clear the variant rules are: undocumented rules stretch the analysis stage.

The ERP/PIM boundary

If live stock, real-time pricing or order creation is required, the project becomes a systems integration and is planned separately. The MORFAXIS standard scope is visualising the configuration, summarising it and converting it into an enquiry. The boundary is separated in writing before any proposal.

Who it fits, who it does not

A good fit

Companies with dozens of valid combinations, sales teams fielding many pre-quotation questions, dealer networks, and e-commerce operations struggling to produce variant imagery.

Not a fit

Companies with two or three options, variant rules that do not yet exist, or web infrastructure that cannot meet the performance targets.

How the investment is determined

The main drivers are variant count and rule complexity, whether geometry changes (a colour variant is cheap, a size variant is not), the breadth of the product family, integration scope, language count and AR requirements.

Investment range. System build-outs generally work with six-figure budgets in Turkish lira terms. Single-product render or animation packages can be handled at a smaller scope. The exact investment depends on the number of products and markets, technical complexity, languages, integrations and delivery scope. Scope and a commercial proposal follow the fit call.

Questions answered on this page

How is a 3D configurator added to a website?

It is built as a standalone page or an embeddable component; the existing site does not need rebuilding. The condition is that the page can serve the model quickly: the model stays under three megabytes compressed, the scene never autostarts, and loading begins after the user asks for it.

What kind of model does a configurator need?

An engineering model cannot be used directly. Polygon count is reduced, internal geometry is cleaned, textures are compressed with KTX2/Basis and LOD is set up. The target is under three megabytes compressed and under 250k triangles. Skip this and the configurator will not open on mobile.

Why do variant rules matter so much?

Because not every combination is buildable. If a given body size does not work with a given module, the configurator has to prevent it. Without written rules a customer builds a configuration you cannot manufacture and sales has to walk it back — worse than having no configurator at all.

Configurator or 360-degree viewer?

If there is nothing to choose, a 360 sequence is enough and far cheaper: it shows the product from every angle. A configurator earns its cost when there is a real choice. The test is simple: if the customer is selecting, build a configurator; if they are only looking, build a 360 sequence.

Can it show prices?

Price or product code generation can be defined in scope. Live pricing and stock require ERP/PIM integration, which is a separate scope. For most manufacturers the right start is binding a structured configuration summary to an enquiry rather than publishing a price.

Can our dealers use it?

Yes. The most valuable feature for dealer use is the shareable configuration link: the dealer builds a configuration, sends the link to the customer, and the quotation is prepared from the same summary. It removes the errors caused by variants described over the phone.

Does a configurator hurt SEO?

Not when built correctly. The critical rule is that product information must not live only inside the 3D scene: variant names, specifications and descriptions belong in the page HTML. The 3D experience is an enhancement, not the content itself.

How long until launch?

Six weeks where variant rules are clear, up to fourteen for complex families. The most common cause of delay is not modelling but settling internally which combinations are valid.

Let's settle your scope together →

Opportunity Analysis

Let customers see the product in their own configuration — and stop your sales team re-drawing it.

With high-variant products the real cost is not imagery but misunderstanding. A configurator makes options concrete in the customer's eyes and measurably reduces pre-quotation question traffic.

Outcomes vary with the market, competition, existing brand authority, technical infrastructure and continuity of execution. MORFAXIS does not guarantee search rankings, AI recommendation or commercial results; it builds a measurable improvement system.