TL;DR:

  • B2B manufacturers are using AR product configurators to let buyers visualise and specify complex custom equipment before ordering, reducing costly change requests and production errors
  • The strongest use cases are high-value, high-complexity products: industrial machinery, modular process equipment, commercial vehicles, and data centre hardware
  • Delivery via WebXR is gaining ground over native apps, lowering the barrier to deployment significantly for both vendors and buyers

Product configurators have existed in web browsers for decades. What AR changes is the dimension of confidence a buyer can have before signing off a purchase order. When a procurement engineer can walk a scaled-down virtual version of a custom conveyor system through their actual facility in a headset, checking clearances against real columns and ceiling height, the conversation with the vendor changes. Errors that surface at installation start surfacing during the configuration session instead.

This is the use case that’s driving B2B manufacturing adoption of AR configurators, and it’s more mature than most coverage of spatial computing would suggest.

What B2B AR Configurators Actually Do

The core capability is straightforward: a buyer accesses a 3D model of a product that reflects the current configuration options, places it in their real environment via AR, and manipulates specifications while seeing the result in context.

In practice, the complexity sits underneath that simple description. Industrial equipment configurations often involve thousands of option combinations with interdependencies — specifying a motor capacity constrains compatible gearbox options, which in turn affects frame dimensions and mounting specifications. The configurator has to enforce those rules in real time, update the 3D model, and reflect changes in price and lead time. This is a solved problem in web-based CPQ (configure, price, quote) software. AR layers on the spatial visualisation without replacing any of that logic.

The integration between AR front-end and CPQ back-end is where most implementation effort goes. Vendors who treat the AR component as a standalone tool and try to retrofit it into existing quoting processes tend to have poor results. Those who build the AR interface as a new front-end for their existing product configuration data do better.

Where It’s Being Used

Capital equipment for manufacturing: Companies selling process machinery — mixers, conveyors, packaging lines, custom machine tooling — have the most compelling use case. These are large-ticket, long-lead-time purchases where buyers often cannot easily trial the equipment before committing. AR lets procurement and plant engineering teams verify spatial fit, operator access paths, and clearances before any metal is cut. Several European capital equipment manufacturers have moved AR configurators from pilot to standard sales tool status.

Commercial vehicle specification: Fleet procurement for specialised vehicles — refrigerated trucks, utility vehicles with custom upfitting, emergency service vehicles — involves extensive specification processes where small errors have large downstream costs. AR configurators for commercial vehicles let fleet managers see their actual spec (body length, load bay configuration, lighting, tool storage) on a vehicle model scaled to the real dimensions of their yard or depot.

Modular industrial infrastructure: Data centre operators configuring modular rack systems, process engineers specifying modular skid-mounted equipment, and facilities teams buying modular office infrastructure are all categories where AR configurators reduce the back-and-forth with vendors around spatial constraints. The buyer can answer “will this fit?” without a site survey visit.

B2B audio-visual and integration systems: Commercial AV integrators specifying display walls, speaker systems, and infrastructure for conference facilities have found AR configurators useful for communicating proposed installations to clients before any commitment. This is a step removed from manufacturing, but the underlying pattern is the same.

Delivery: WebXR vs Native Apps

Two years ago, most serious AR configurator deployments used native applications — iOS ARKit apps or Android ARCore apps that buyers had to download. The friction was significant, particularly in B2B contexts where procurement happens across heterogeneous device fleets with corporate MDM policies.

WebXR has changed this. A WebXR-based configurator runs in a supported browser on an AR-capable device. No app installation, no MDM approval, no friction at the point of demo. The buyer opens a link sent by the sales team, points their phone or tablet at the floor, and starts configuring.

The current practical limitation is that WebXR on headsets is less mature than native headset applications. For use cases where the buyer wants to use a HoloLens 2 or Vision Pro during a formal configuration session, native apps still win on experience quality. For the more common case where the buyer wants to use their existing phone during an on-site walk-through, WebXR is now good enough.

Most vendors are deploying both: a WebXR experience for initial qualification and broader reach, a native app experience for formal specification sessions with key accounts.

Integration and Data Considerations

The most common integration patterns:

CAD to AR pipeline: Manufacturers maintain product geometry in CAD tools (SolidWorks, CATIA, Creo). The AR configurator needs this geometry in a format suitable for real-time rendering, typically glTF or USDZ. Maintaining this pipeline, particularly for products that have frequent engineering changes, adds operational overhead. Teams that build automated export pipelines from CAD to their AR content management system do significantly better than those doing manual conversions.

CPQ integration: Configuration logic should live in the same system that drives sales quoting, not be reimplemented in the AR front-end. The AR interface should consume configuration options and constraints from the CPQ system via API. This is architecturally more complex but means configuration logic is only maintained in one place.

Analytics: AR configurator sessions generate useful data — which options buyers explore, where they spend time, which configurations they share, where they abandon. This data is typically more useful for product management teams than sales teams, but it rarely flows automatically to where it needs to go.

What Buyers and Sellers Get Out of It

On the buyer side, the measurable outcomes are shorter validation cycles and fewer surprises at installation. Organisations that have measured this find reductions in change orders after purchase of 20-40% for complex configured equipment. The mechanism is simple: the buyer catches fit problems and specification errors during the AR session rather than at delivery.

On the seller side, the primary value is earlier commitment and reduced sales cycle length. Configuration sessions with AR tools tend to produce more complete, more confident specifications. Buyers who have seen the product in their space are more ready to sign off. Secondary value comes from differentiating in a market where competitors are still doing static product sheets and 2D drawings.

Getting Started

For manufacturers considering AR configurators: the product with the most to gain is the one with the highest combination of customisation options, configuration complexity, and installation-fit risk. Start there, not with the simplest product in the catalogue.

The build-vs-buy decision depends heavily on your existing technology infrastructure. If you already have a modern CPQ system, vendors like Threekit, Cylindo, and Zakeke offer AR configurator platforms that integrate with CPQ. If your configuration logic lives in spreadsheets or legacy ERP, you are looking at more fundamental changes before AR adds value.

Budget for the content pipeline. Getting 3D product models AR-ready is the most common underestimated cost in these projects.