3D product visualization software · Viewer · Configurator · Visual CPQ
Visualize configurable products in 3D—and keep every choice connected.
Configurix connects interactive 3D product visualization to governed options, dimensions, materials and accessories. Buyers can understand the product, create a valid configuration and continue the same saved state into live pricing, a quote, cart, lead, approval or structured handoff.
Visual configuration state
Outdoor system · VC-2046
Current view
Customer perspective
System
Bioclimatic
Frame
Anthracite
Roof
Motorized
Screen
South side
Visual
synced
Specification
12 values
Next action
Quote ready
Direct definition
3D product visualization software connects the picture to product data.
3D product visualization software lets a person inspect a digital product and see approved variants or configuration choices update in context. The category includes viewers, visualizers, configurators and visual CPQ. What separates them is not visual polish but the product state each system validates, saves and sends downstream.
When a user changes a finish, dimension, module or accessory, the interface should update the relevant geometry or material and record the exact product identity behind that decision. If the scene looks different but the business cannot reproduce what was selected, the experience is closer to a visual effect than a connected configurator.
Configurix can connect this visual state to scoped pricing, quotes, carts, CRM records and agreed order or BOM handoffs. Those outputs require their own rules and acceptance tests. A convincing preview alone does not prove price accuracy, component availability, structural compliance, manufacturing data or site suitability.
Choose the right category
Customizer, viewer, configurator, visual CPQ and CAD solve different problems.
Vendor labels overlap. Compare what the working system creates, validates, saves and sends downstream.
Image or colour customizer
Swaps prepared images, colours, text, artwork or decorative layers on a base product.
Useful for appearance-led personalization when the purchasable variants and production method are already defined.
It may not validate dimensions, dependencies, price, availability or a structured specification.
Interactive 3D viewer
Lets a user rotate, zoom, inspect hotspots, play animation or open a prepared model in AR.
Useful for product understanding, spatial inspection and richer ecommerce presentation.
Viewing a model does not prove that choices create a valid, saved product variant.
Visual product configurator
Binds permitted choices to visible geometry, materials, dimensions, modules and accessories.
Useful when buyers must understand and create a valid product instead of only inspecting one.
The implementation must prove that visible state and structured configuration stay synchronized.
Visual CPQ
Adds governed pricing, account context, discounts, proposals, revisions and approvals to visual configuration.
Useful for made-to-measure, dealer, showroom and assisted-sales journeys with commercial complexity.
Commercial authority and downstream ownership must be defined; a visual alone cannot prove the quote.
CAD or engineering tool
Creates or edits technical geometry for design, analysis, detailing and engineering release.
Useful when qualified users must work outside a fully predefined commercial solution space.
It is not automatically a guided, responsive or customer-safe selling experience.
Interactive capability planner
Start with the decision, not the 3D feature list.
Choose what changes, what the user must achieve and where the experience runs. The result identifies the minimum capability boundary and the evidence a working system should provide.
Recommended capability boundary
Rules-based 3D product configurator
Use one governed configuration state to drive geometry, materials, dimensions and accessories. Rules must validate what can be built or sold within the accepted product scope.
Minimum persistent record
Configuration ID · rule revision · scene revision
Require this evidence
Required, dependent, excluded and dimensional choices are tested at boundaries.
Visible geometry and the structured specification describe the same configuration.
Saved projects retain enough revision context to be reopened or migrated safely.
Connected visual architecture
Eight layers keep what people see connected to what the business sells.
Each layer has different owners and failure modes. Treating a 3D file as the entire system hides the decisions that make configuration reliable.
Catalogue identity
Give every product family, model, option, material, component and accessory a stable identity that can survive beyond the screen.
Product rules
Control required choices, dependencies, exclusions, ranges, increments, derived values, warnings and review conditions.
Geometry binding
Map configuration values to visibility, dimensions, transforms, modules, openings, repetitions and parametric geometry.
Material binding
Map approved finish codes to base colour, texture, scale, roughness, metallic response, transparency and other rendering inputs.
Interaction model
Define cameras, orbit limits, zoom, hotspots, annotations, selectors, undo, reset and alternatives to complex gestures.
Commercial context
Keep the visible product connected to quantities, scoped price logic, availability messages and the permitted next action.
Saved revision
Preserve configuration, scene, catalogue, rule and price references so a reopened project can reproduce its agreed state.
Structured handoff
Pass stable identifiers and accepted values to quote, cart, CRM, ERP, ecommerce or another named destination without reading pixels.
Visual state contract
Define the product state before polishing the scene.
A reproducible visual result needs identity, versions, bindings and meaning. These fields make the scene testable and let another channel continue the same project.
Configuration identity
Configuration ID, revision, product family, model, catalogue version and rule version
Scene identity
Scene or asset revision, renderer version, product root and supported fallback
Geometry state
Visible nodes, dimensions, transforms, module count, openings, dependent parts and animation state
Material state
Finish IDs, colour space, texture set, scale, UV behavior and material parameters
View state
Camera, target, zoom limits, selected hotspot, exploded state and optional saved viewpoint
Meaning
Human-readable option labels, measurements, warnings, accessibility text and current validity
Commercial link
Quantity, price revision, market, currency, role and permitted quote, cart or consultation action
Evidence
Snapshot, specification, timestamp, device context and references used by the next document or system
One accepted state
The scene and the record should tell the same story.
Choice
screen:south
Visual
node visible
Summary
South screen
Record
cfg-r7
Presentation modes
Use the visual mode that helps the decision.
2D, real-time 3D and AR are not a maturity ladder. Each mode has a purpose, cost, device footprint and evidence requirement.
2D and composed imagery
Prepared views and layered images can deliver fast, controlled representation for products whose choices can be shown from known angles. They can also provide a useful fallback when a device cannot run the full scene.
Fast initial understanding
Controlled camera and composition
Useful low-capability fallback
Interactive real-time 3D
A browser scene can expose rotation, zoom, animation and configuration-driven geometry or materials. Runtime assets should be optimized for delivery instead of publishing authoring files directly.
Inspect from useful angles
See choices update in context
Reuse one governed configuration
Augmented reality
AR can place a supported product representation in a physical environment. Device support, tracking, scale, lighting and site-survey boundaries must be stated and tested rather than assumed.
Optional spatial preview
Supported-device fallback
No substitute for technical survey
Visual fidelity
Accuracy is a review process, not a style word.
“Photorealistic” does not say whether a configurable product is dimensionally or materially correct. Approve the attributes that matter for the buyer decision.
Proportion
Overall form, clearances, repetitions and component relationships match the governed dimensions.
Geometry
Profiles, joints, openings, edge treatment and configurable modules are detailed to the level required for the decision.
Materials
Approved finish identity drives texture, scale, reflectance, transparency and surface response consistently.
Lighting
A neutral, repeatable environment reveals the product without hiding geometry or creating a misleading finish impression.
Camera
Useful perspectives, field of view, orbit limits and target prevent distortion and keep the product readable.
Context
Room, garden, house or installation context clarifies scale without presenting illustrative surroundings as surveyed reality.
3D web performance
Make the product useful before every asset is perfect.
Khronos defines glTF as a runtime asset delivery format, not an authoring format. The wider page should also be measured through real-user loading, responsiveness and stability—not only a powerful desktop demo.
Page shell
The heading, value proposition, product summary and primary controls should remain understandable while 3D assets load.
First useful product
Measure when the representative product becomes visible and the user can perform the first meaningful configuration action.
Option response
Measure from an accepted choice to the updated visual and textual state—not only to the click handler.
Asset transfer
Track geometry, textures, environment maps, fonts and code separately; compress and cache according to change frequency.
Device pressure
Test GPU memory, texture resolution, draw calls, polygon count, thermal behavior and recovery on representative mobile hardware.
Resilience
Provide loading, retry, no-WebGL, reduced-motion and low-capability paths without losing the product definition or next action.
Accessible interaction
The canvas cannot be the only way to configure.
W3C guidance requires keyboard access and alternatives to difficult gestures. A robust product journey keeps labelled controls and a textual summary available outside the rendered scene.
Every product choice is available through labelled HTML controls, not only by clicking an object inside the canvas.
Keyboard users can reach, operate and leave the configurator without a trap, and focus remains visible after state changes.
Orbit, zoom, carousel and drag behaviors have simple button or single-pointer alternatives where the action is not inherently path-dependent.
Selected state is conveyed through text and programmatic state as well as colour, outline, texture or animation.
Live price, validity, loading and error changes are exposed as useful status messages without repeatedly interrupting the user.
Motion, auto-rotation and animated transitions respect reduced-motion preferences and can be paused when they are not essential.
Touch targets, labels, contrast and control spacing are tested at representative mobile widths and browser zoom levels.
A textual product summary and specification communicate the current result when the visual scene cannot be perceived or operated.
Search and answer-engine clarity
Rendered pixels do not explain the product catalogue.
The surrounding page must state what Configurix is, what the product supports and which boundaries remain. Semantic, crawlable content helps buyers, search engines and AI systems interpret an otherwise visual experience.
Indexable definition
Explain in semantic HTML what the configurator is, who it serves and how it differs from a viewer, customizer, CPQ and CAD.
Product meaning
Publish the product families, option concepts, materials, dimensions, use cases and decision boundaries represented by the experience.
Visible state summary
Reflect important selections in text near the scene so people and machines do not need to interpret rendered pixels.
Stable discovery routes
Give major product families and buyer intents crawlable URLs, meaningful titles, canonical rules and useful internal links.
Structured data
Use accurate schema for the surrounding software, product, FAQ or article content; do not mark invisible or unsupported facts.
Performance evidence
Measure real-user loading, responsiveness and stability because a large 3D payload can weaken the surrounding page experience.
One engine, role-specific journeys
Keep product truth shared while the experience changes by channel.
Public website
Guided choices, safe public catalogue, customer-facing price or enquiry action and easy saved-project continuation
Ecommerce
Purchasable configuration, inventory or review boundaries, cart-safe identity and order-line traceability
Showroom and sales
Expanded product knowledge, customer record, controlled discounts, revisions, quotes and presentation views
Dealer portal
Assigned catalogue, account pricing, margin permissions, co-branding, approval limits and persistent opportunity data
Technical review
Measurements, exceptions, attachments, reviewer decision and approved revision without exposing authoring complexity to buyers
Multilingual markets
Translated labels and documents while stable product, material and configuration identifiers stay language-neutral
Implementation blueprint
Build one complete product journey before expanding the library.
A representative product reveals how catalogue, rules, assets, interaction, pricing and outputs behave together. Reuse the accepted pattern after the difficult decisions are explicit.
Decision
Name the buyer decision
Define what a user must understand, choose and do after the visual experience: enquire, save, quote, buy, book or submit for review.
Product
Choose one representative system
Use a product with real dimensions, dependencies, materials, accessories, edge cases and a meaningful commercial destination.
State
Define the configuration contract
Specify stable IDs, values, validity, revisions, derived quantities, scene mappings and downstream fields before polishing the interface.
Assets
Build the runtime asset system
Create geometry, materials, cameras, variants, levels of detail and publishing rules for repeatable browser delivery.
Experience
Design interaction and fallbacks
Plan responsive controls, labelled choices, summaries, loading, errors, accessibility, low-capability devices and optional AR.
Outputs
Connect the next action
Keep the exact visible product linked to its price, saved project, cart, quote, lead, approval or structured handoff.
Acceptance
Test state and pixels together
Verify expected geometry, materials, text, validity, prices and outputs for normal, boundary and exception configurations.
Operations
Govern visual change
Assign owners for catalogue, rules, models, materials, translations, performance budgets, device support and regression evidence.
Measurement model
Measure understanding, valid state and continuation separately.
Agree the baseline, denominator, segment, exclusions and owner before launch. Engagement with a 3D scene is not automatically evidence of a better commercial outcome.
First useful configuration
Time until a representative user can see the product and complete the first meaningful choice
Visual update latency
Time from an accepted option change to consistent geometry, material, text and commercial state
Valid completion rate
Started sessions reaching the defined valid configuration state, segmented by product and device
Recovery rate
Sessions that recover from invalid choices, loading failures or interrupted saved projects
Configuration-to-action rate
Valid projects continuing to the defined quote, cart, consultation, save or review action
State mismatch rate
Detected cases where visible product, specification, price, document or downstream record disagree
Real-user performance
LCP, INP and CLS plus scene-specific loading and update measures at the agreed percentiles
Change regression rate
Released catalogue, asset or rule changes causing accepted visual, functional or output regressions
Working acceptance checklist
Test product state, visible state and next action together.
Give each supplier the same representative product, devices, reference states and expected outputs. Require evidence from a working implementation.
Every visible option maps to a stable catalogue identity and every selected identity has a human-readable summary.
Required, dependent, excluded, range, increment, derived-value and review rules match approved product examples.
Geometry visibility, dimensions, transforms and repetition match expected values for normal and boundary configurations.
Material identity, texture scale, colour treatment and transparency match the approved reference under the test environment.
The screen, textual specification, saved configuration and downstream payload reference the same product revision.
Back, undo, reset, save, reopen and revise preserve or intentionally change state according to the documented behavior.
Keyboard, touch and pointer users can complete the core journey through labelled controls without becoming trapped in the 3D scene.
Loading, network failure, unsupported graphics, asset failure and low-capability devices expose a useful fallback and recovery path.
Representative mobile devices keep controls readable, targets usable and the product visible without unintended overlap or layout shift.
Price, availability, quote, cart or lead actions use the accepted configuration identity instead of reconstructing choices from labels.
An out-of-date saved project is migrated, rejected or opened in a clearly identified historical state—never silently reinterpreted.
Analytics records product, configuration revision, event, role, channel, device context and outcome without leaking unnecessary personal data.
Primary references
Ground the visual experience in open specifications and measurable behavior.
Khronos 3D Commerce asset guidelines
The official 3D Commerce registry for real-time product-asset creation guidance across geometry, materials, textures, scale and publishing targets.
Khronos glTF 2.0 specification
The primary specification for an API-neutral runtime 3D asset delivery format covering scenes, nodes, meshes, materials, cameras and animations.
Khronos glTF overview and PBR
Official guidance on efficient 3D delivery, physically based material properties and the broader glTF ecosystem.
W3C WCAG 2.2
The W3C Recommendation covering perceivable, operable, understandable and robust web content, including keyboard and input requirements.
W3C input modalities guidance
Official accessibility guidance for pointer gestures, dragging, target size and concurrent input methods relevant to interactive 3D controls.
Google Web Vitals
Official guidance for field measurement of loading, interactivity and visual stability through LCP, INP and CLS.
Google model-viewer
Official open-source reference for displaying interactive 3D models on the web and offering supported augmented-reality paths with fallback behavior.
W3C WebXR Device API
The web API specification for access to augmented and virtual reality devices, sensors and immersive sessions.
Related Configurix guides
Continue from the visual layer into rules, assets and commercial workflow.
Product configurator software
Define the category, rules, outputs, roles and implementation scope.
Read the guide3D product customization software
Connect text, logos, artwork, materials and customer assets to governed designs and outputs.
Read the guide3D product simulator
Compare interactive simulation with viewing, configuration, CPQ and CAD.
Read the guideVisual CPQ software
Connect the visual product to pricing, quotes, revisions and approvals.
Read the guide3D asset pipeline
Govern source models, runtime assets, materials, publishing and regression tests.
Read the guideAR product configurator
Preserve configuration identity, scale, materials and commercial continuity across supported augmented-reality paths.
Read the guideWebsite configurators
Embed a governed experience with semantic content, analytics and lead continuation.
Read the guideCompare configurator software
Use one representative product, scorecard and acceptance test pack.
Read the guideVisual product configurator FAQ
Questions buyers, product teams and technical reviewers should ask.
These answers separate visual presentation from governed product configuration, commercial workflow and operational responsibility.
Start with your representative product
See whether the visual state and product state stay connected.
Bring one product, its options, dimensions, edge cases and expected next action. We will map the visual experience, data contract and acceptance evidence around the real catalogue.