AR product configurator

Put the configured product in the customer’s world.

An augmented-reality product configurator should show the same valid product your customer configured—not a disconnected demo model. Configurix connects governed choices, dimensions, materials, saved projects and commercial action with an optional AR preview for supported products, assets, devices and viewer paths.

Discuss your AR configurator Choose an AR path

Garden project · revision 6

Bioclimatic pergola

AR ready

Place at true product scale

Size

4.8 × 3.5 m

Finish

Anthracite

Project

CX-1842

Three ways to deliver augmented reality from a configurator.

“Supports AR” is not an architecture. The implementation must name the viewer path, supported devices, asset formats, state continuity and fallback before capability can be accepted.

Native viewer handoff

A customer configures in the browser, then opens the accepted model in a device-native AR viewer such as Scene Viewer or AR Quick Look.

Strength

Fast route to familiar placement controls with a clear 3D fallback when the implementation and device support it.

Boundary

The native viewer may not carry the full configurator interface, so the generated asset and configuration identity must be prepared before handoff.

In-browser WebXR experience

A compatible browser starts an immersive AR session while the application keeps more control over interaction, state and interface.

Strength

Can preserve a connected web journey and application-owned behavior on supported browsers and hardware.

Boundary

Support must be detected at runtime. A useful non-AR fallback is part of the product, not an optional error message.

Purpose-built mobile application

A managed sales, survey or specialist workflow needs native device capabilities, controlled hardware or deeper project interaction.

Strength

Appropriate when the business case justifies app installation, release management and a defined supported-device estate.

Boundary

An app does not remove product-data, asset, scale, testing or configuration-continuity work; it changes the delivery surface.

Interactive AR path planner

Match the delivery path to device reach and interaction.

This planner identifies a starting architecture. Final support still depends on the product, asset pipeline, target devices, browsers, viewer behavior and acceptance tests.

Device reach

Experience requirement

Recommended starting architecture

Use a governed cross-platform handoff

Prepare and validate the required viewer paths without creating separate product truth. Capability detection selects an accepted route while one configuration ID anchors every asset and next action.

One accepted configuration → viewer-specific derivatives → supported native AR → browser 3D fallback

GLB or glTF and USDZ derivative parity

Runtime capability detection

Viewer-specific launch and fallback tests

One saved configuration across every path

Preserve one configuration across 3D, AR and the sale.

The valuable part is not launching a camera. It is proving that the placed product is the exact saved revision that returns to the quote, cart, CRM or project workflow.

Configuration identity

Stable project ID and revision shared by browser 3D, AR request, quote and saved project.

Product identity

Product family, model, catalogue revision, market and availability context.

Accepted choices

Option and value IDs—not only labels, screenshots or material names.

Geometry state

Modules, dimensions, transforms, visibility, repetition and generated geometry inputs.

Material state

Stable finish IDs and AR-ready material bindings with tested color and texture behavior.

World scale

Declared units, conversion, model bounds, intended scale policy and placement origin.

Asset revision

GLB, glTF, USDZ or other delivery asset identity plus the pipeline revision that created it.

Viewer path

Detected capability, selected AR mode, fallback destination and viewer-specific parameters.

Commercial context

Price result, currency and quote revision remain related without treating AR as the pricing authority.

Journey events

Availability, launch, placement, return, edit, save and commercial action tied to consented analytics.

Prepare product assets for placement, not just presentation.

A good browser render can still fail in AR when scale, origin, materials, delivery format or the largest configuration was never tested in the intended viewer.

Scale and units

Export and validate physical dimensions in a known unit. Test a reference object and representative minimum, normal and maximum configurations.

Origin and placement

Place the origin intentionally at the floor, wall, ceiling or mounting reference that matches the product and the viewer path.

Runtime geometry

Remove hidden engineering detail, preserve visible silhouette and openings, control mesh count and verify the largest valid product on real devices.

Materials and lighting

Use physically based material inputs consistently, compress textures deliberately and review finishes under varied real-world lighting.

Configuration mapping

Every visible module and finish must trace to accepted product state so the AR result cannot drift from the saved project.

Format delivery

Validate the actual GLB, glTF, USDZ or generated derivative in each promised viewer; file extension alone is not acceptance evidence.

Use AR for context. Keep technical approval where it belongs.

The most trustworthy experience tells buyers what AR helps them understand and what a survey, engineer or installer must still verify.

Pergolas, verandas and carports

Place the configured structure beside a building or within an outdoor area to discuss footprint, finish and visual proportion.

AR does not verify foundations, wall condition, drainage, boundaries, utilities, wind loading or planning requirements.

Furniture and modular storage

Preview overall size, arrangement, material and relationship to surrounding furniture before saving or ordering.

Room scan quality, occlusion, clearances, access routes and wall fixing still require separate checks where relevant.

Outdoor kitchens and equipment

Compare layout, module sequence, finish and approximate working space in the intended environment.

Services, ventilation, heat zones, structural support and installation clearances need accepted technical review.

Doors, windows and wall products

Communicate style, color, panel arrangement, hardware and visual fit against a real opening or facade.

A visual overlay is not an opening survey, installation tolerance check, fire assessment or structural approval.

Industrial and commercial products

Help buyers and sales teams understand footprint, access envelope, orientation and context before technical design review.

Safety zones, loads, connections, guarding, compliance and commissioning remain governed engineering decisions.

Tabletop and consumer products

Show configured appearance, relative size and materials with a low-friction path back to cart, quote or saved design.

Small reflective, transparent or animated products need device testing because visual behavior can vary by viewer and environment.

Acceptance before launch

Test the product, device path and return journey together.

A successful viewer launch proves very little on its own. Acceptance follows the same configuration through preparation, placement, interruption, return and commercial action.

State parity

The AR model shows the same product, modules, dimensions, options and finishes as the accepted browser configuration.

Physical scale

Known reference dimensions remain within the agreed tolerance across representative supported devices and viewer paths.

Placement origin

Floor-, wall- or tabletop placement begins from the approved mounting reference and orientation.

Largest configuration

The heaviest valid product loads, places and remains usable on the lowest supported device tier.

Finish review

Representative light, dark, metallic, transparent and textured finishes remain understandable in varied environments.

Capability detection

The page offers AR only when an accepted path is available and explains or uses a tested fallback otherwise.

Journey return

Leaving native AR and returning to the website preserves the saved configuration and the next commercial action.

Revision trace

AR assets and events record the catalogue, configuration and asset revisions used at launch.

Unsupported state

Invalid, incomplete or review-required configurations cannot silently create an orderable AR result.

Orientation change

Portrait, landscape, interruption, backgrounding and session exit do not corrupt the project state.

Accessibility

Essential configuration and buying tasks remain available without entering an immersive camera experience.

Measurement boundary

Copy, workflow and approvals never present the visualization as an accepted survey or engineering measurement.

Measure the journey without inventing causation.

Tie AR events to the configuration and a defined funnel. Report availability, successful use and later actions separately so teams can compare like-for-like audiences instead of claiming that every AR-assisted order was caused by AR.

ar_available

An accepted AR path is available for this device, product and configuration.

ar_launch_requested

The user selected the AR action from a named journey location.

ar_launch_succeeded

The implementation received evidence that the intended path opened successfully.

ar_launch_failed

The path failed with a categorized reason and a usable fallback was offered.

ar_returned

The customer returned to the web journey with the same configuration revision.

configuration_edited_after_ar

An option changed after AR and created a new traceable project revision.

project_saved_after_ar

The customer saved or shared the project after entering AR.

commercial_action_after_ar

The same configuration later reached cart, lead, quote or approval within the chosen attribution window.

Privacy by named data flow

Document permissions, which viewer handles camera composition, what the site receives, what is stored and how consented analytics behaves.

An equivalent non-AR journey

Keep essential product choices, summaries, saving and buying actions accessible without an immersive session or camera permission.

Performance on real mobile hardware

Stage code and assets, test the largest valid product and measure transfer, decode, memory and interaction on the lowest supported device tier.

Where Configurix fits

AR stays connected to the product configuration.

Configurix is white-label 3D product configurator and visual CPQ software for manufacturers, product owners, dealers, retailers, showrooms and installers. It connects governed product choices, browser 3D, live pricing, saved projects, leads, quotes and structured handoff. Optional AR is scoped for accepted products, assets, devices and viewer paths.

Exact platform support, asset generation, measurement assistance, ecommerce action, analytics and operational outputs are confirmed against the working implementation. AR helps a customer understand context; it does not silently become survey, engineering or production evidence.

Scope an AR-enabled configurator

One governed journey

Customer creates a valid configuration in responsive browser 3D

Rules, dimensions, material IDs and saved revision remain authoritative

Capability detection selects an accepted AR path or useful fallback

The placed asset records the configuration and asset revisions used

Returning to the website restores the same project and next action

Quote, cart, CRM or project record receives structured configuration data

AR product configurator FAQs.

Direct answers for product, ecommerce, sales, marketing, 3D, engineering and IT teams evaluating augmented-reality product configuration.

An AR product configurator lets a buyer first create a valid product configuration and then preview that accepted state in a real environment through a compatible phone, tablet, headset or viewer. The configurator remains responsible for product identity, allowed choices, dimensions, materials, saved revision and commercial context. AR adds placement and visual context; it should not replace the rules engine, price service, project record or engineering approval.

Not always. A website can hand a model to a native viewer such as Scene Viewer or AR Quick Look, or use WebXR on supported devices and browsers. A purpose-built application can be appropriate for managed sales, survey or specialist workflows. Device support, interaction needs, fallback, update ownership and the desired buying journey should determine the architecture rather than an assumption that every AR experience needs an app.

WebAR is a broad industry term for augmented-reality experiences reached from the web. It may describe an in-browser WebXR session, a web page that launches a device-native viewer, or another browser-delivered path. Buyers should ask which implementation is used, which devices and browsers are supported, what format is delivered, whether configurator state remains connected and what happens when AR is unavailable.

They are device-native viewing paths with different ecosystems, formats, launch behavior and controls. Apple documents AR Quick Look for USDZ or Reality content on supported Apple platforms. Google documents Scene Viewer for interactive web-hosted 3D and AR on supported Android devices, including 3D fallback modes. A cross-platform configurator may prepare more than one derivative while retaining one governed configuration identity.

The required format depends on the chosen viewer path. Runtime web and Android pipelines commonly use glTF or GLB, while Apple AR Quick Look accepts USDZ and Reality content. Some libraries can generate or convert a derivative at runtime or during publishing. Format support must be verified with representative configured products, materials, animations, scale and target devices rather than inferred from a file extension.

It can when the selected architecture and viewer path support the required interaction, but implementations differ. A browser-owned WebXR experience can retain more application control. A native viewer handoff may instead receive a generated asset representing the already selected finish. The requirement should state whether options change before launch, during AR or after returning—and how each change creates a saved configuration revision.

AR can present a model using declared physical units and product dimensions, and scale is an important acceptance test. Real-world tracking, surface detection, device sensors, user placement and the environment still introduce uncertainty. AR is a decision aid for context and proportion; it is not a substitute for a site survey, manufacturing measurement, structural check or installation approval.

A scoped implementation may offer measurement assistance on supported devices, but a displayed measurement should not automatically become an accepted order dimension. Define the device, method, tolerance, user guidance, evidence and review path. For made-to-measure or safety-relevant products, keep survey and engineering responsibilities explicit even when AR helps collect preliminary information.

Test configuration parity, units, scale, origin, orientation, materials, largest valid geometry, asset delivery, capability detection, viewer launch, fallbacks, interruption, return journey, saved revision, analytics, accessibility and measurement boundaries. Use representative physical reference dimensions and real devices across the supported matrix. Record the catalogue, rules, asset pipeline, viewer path and application revisions with the evidence.

It can if large assets, textures, conversion code or AR dependencies block the initial buying journey. A staged implementation keeps indexable content and core controls useful, loads the browser 3D scene deliberately and prepares the AR path when intent and capability are known. Measure transfer, decode, GPU memory, first useful interaction and the largest supported configuration on representative mobile hardware.

An immersive camera experience cannot be the only way to understand or operate the product. Provide accessible HTML controls, text summaries, visible selected state, keyboard-operable configuration, clear errors, reduced-motion behavior and an equivalent route to save, quote or buy. Test the non-AR journey against the accepted accessibility standard and include AR instructions that are understandable without relying only on gesture or color.

Document which component receives camera or environment information, what the website can access, which permissions are requested, what analytics events are stored and whether images, scans or spatial data leave the device. The W3C AR module includes privacy and security considerations and states that its base AR module does not expose camera images directly to web content. Extra features and native paths need their own reviewed data flow and consent behavior.

Measure a defined funnel: AR availability, launch request, successful start, failure, return, edit, save and the later commercial action tied to the same configuration. Use explicit denominators and compare equivalent audiences. An AR-assisted order does not prove AR caused the order; device capability, product type, traffic source and customer intent can differ. Treat conversion claims as measured customer-specific outcomes, not universal promises.

Configurix can connect an implemented product's governed configuration state with an optional AR preview for accepted products, assets, devices and viewer paths. The scope defines product rules, dimensions, materials, runtime assets, supported platforms, fallback, saved-project continuity and acceptance tests. AR remains a visualization aid; exact availability and any measurement, ecommerce or production connection are confirmed against the working implementation and signed scope.

Primary platform and standards sources.

These official references support the delivery-path distinctions in this guide. Actual product support remains dependent on the implemented asset, device, browser, viewer and acceptance scope.

W3C WebXR Device API

The web interface for accessing immersive devices and sessions, including the security and low-latency context around WebXR.

Open source

W3C WebXR Augmented Reality Module

The candidate-standard module that defines immersive AR session behavior and real-world composition concepts for WebXR.

Open source

Google ARCore Scene Viewer

Official Android documentation for launching web-hosted models in native 3D or AR with mode and fallback behavior.

Open source

Apple AR Quick Look

Official guidance for previewing USDZ or Reality content and launching AR Quick Look from an application or web page.

Open source

model-viewer AR documentation

Reference documentation for prioritized WebXR, Scene Viewer and Quick Look AR modes and scale behavior.

Open source

Khronos glTF 2.0 specification

The official specification for an API-neutral runtime 3D asset delivery format used across web visualization pipelines.

Open source

Put the configured product in the customer’s world.

Three ways to deliver augmented reality from a configurator.

Native viewer handoff

In-browser WebXR experience

Purpose-built mobile application

Match the delivery path to device reach and interaction.

Use a governed cross-platform handoff

Preserve one configuration across 3D, AR and the sale.

Prepare product assets for placement, not just presentation.

Scale and units

Origin and placement

Runtime geometry

Materials and lighting

Configuration mapping

Format delivery

Use AR for context. Keep technical approval where it belongs.

Pergolas, verandas and carports

Furniture and modular storage

Outdoor kitchens and equipment

Doors, windows and wall products

Industrial and commercial products

Tabletop and consumer products

Test the product, device path and return journey together.

State parity

Physical scale

Placement origin

Largest configuration

Finish review

Capability detection

Journey return

Revision trace

Unsupported state

Orientation change

Accessibility

Measurement boundary

Measure the journey without inventing causation.

Privacy by named data flow

An equivalent non-AR journey

Performance on real mobile hardware

AR stays connected to the product configuration.

AR product configurator FAQs.

What is an AR product configurator?

What is the difference between an AR viewer and an AR product configurator?

Does an AR product configurator require a mobile app?

What is WebAR?

What is WebXR?

How do Apple AR Quick Look and Google Scene Viewer differ?

Which 3D file formats are used for product AR?

Can a configurable product change color inside AR?

Can AR show a made-to-measure product at the correct size?

Can customers measure a space with an AR configurator?

How does the AR model stay synchronized with the 3D configurator?

What happens when a customer's device does not support AR?

How should an AR product configurator be tested?

Does AR make a 3D configurator slow?

Is an AR product configurator accessible?

What privacy issues should an AR configurator address?

How should AR influence conversion reporting?

How does Configurix support augmented-reality product configuration?

Primary platform and standards sources.

W3C WebXR Device API

W3C WebXR Augmented Reality Module

Google ARCore Scene Viewer

Apple AR Quick Look

model-viewer AR documentation

Khronos glTF 2.0 specification

Continue the implementation path.

Visual product configurator

3D asset pipeline

Configurator for websites

Testing and QA guide