Tag: product visualization

Visual CPQ: How Visual Product Configuration Works

Visual CPQ combines interactive product visualization with configure, price, quote (CPQ) logic. A user selects dimensions, materials, components or accessories and sees the configured product change in a 2D or 3D view. Behind the interface, a product model validates the choices, calculates technical and commercial results, and may generate a bill of materials (BOM), CAD output, quotation or manufacturing handoff.

In manufacturing, visual CPQ is more than a sales image or product selector. A useful implementation connects the visual representation to the same configuration data and rules used for engineering, pricing and production. For example, configuring an industrial pump may change the pump casing, impeller, motor, coupling, baseplate and dimensions in the visualization. The system may also check flow and pressure requirements, calculate price, create a configurable BOM and pass approved data to enterprise systems.

This guide explains how visual product configuration works, what systems it requires, where it fits in the sales-to-engineering process, and what manufacturers should verify before implementation.

What is visual CPQ?

Visual CPQ is a manufacturing CPQ capability that lets users configure a product through an interactive 2D, 3D or augmented visual representation while the system applies product rules, engineering logic, pricing and quoting processes.

Traditional CPQ may present a sequence of forms, dropdowns and checkboxes. Visual CPQ adds a visual layer that represents the selected product configuration. Depending on the platform and implementation, the visual layer may show:

Product options, such as motors, valves, seats, handles or control panels.
Dimensional changes, including length, width, height, capacity or mounting positions.
Material and finish selections.
Optional assemblies and accessories.
Product exclusions or unavailable combinations.
Configuration status, warnings and missing information.
Product-specific images, drawings or three-dimensional models.

The visual component does not replace the configuration engine. It provides an interactive representation of the product model. The configuration engine remains responsible for determining whether choices are valid and what technical, commercial and manufacturing data should result.

Manufacturers should therefore distinguish between a visual product configurator and a complete visual CPQ solution. A visual configurator may change images or display selected options without generating a valid BOM, calculating engineering values or supporting downstream production. Visual CPQ connects visualization to those broader processes, although the exact capabilities vary by product and implementation.

How visual product configuration works

A visual CPQ workflow normally contains several connected layers: the user interface, product model, rules engine, visualization data, engineering calculations, commercial logic and enterprise integrations.

1. The user selects product requirements

The process begins with a guided configuration experience. A salesperson, dealer, engineer or customer may specify requirements such as load, flow rate, operating temperature, voltage, dimensions, capacity, environment or intended application.

In an industrial machinery example, the user might choose:

Machine type and operating capacity.
Working width and overall length.
Drive motor and gearbox.
Material grade and surface treatment.
Safety enclosure and access doors.
Control system and electrical supply.
Installation location and required accessories.

The interface can expose direct options or ask requirement-based questions. The latter is often called guided selling. Guided selling recommends or narrows products based on user needs; it is not the same as a rules engine. The system still needs configuration rules to validate the final engineered combination.

2. The configuration engine evaluates rules

Each selection is evaluated against the product model. Rules may determine which options are available, which components are required, which combinations are prohibited and which values must be calculated.

Common rule types include:

Rule type	Manufacturing example	Purpose
Compatibility rule	A high-temperature seal is required for a specified process temperature.	Prevents incompatible selections.
Dependency rule	A variable-frequency drive requires a compatible motor and control cabinet.	Adds required components.
Exclusion rule	A particular mounting arrangement is unavailable with a large motor.	Blocks invalid combinations.
Calculation rule	Frame dimensions change when conveyor length exceeds a threshold.	Derives technical values.
Selection rule	A pressure class is selected based on operating pressure and temperature.	Automates engineering choices.
Commercial rule	Dealer discount or freight treatment depends on market and configuration.	Controls price and terms.

Rules may be implemented as decision tables, constraints, formulas, scripts, object relationships or a combination of these methods. A constraint-based configuration approach describes valid and invalid states across many variables. A rules-based approach often expresses explicit conditions and consequences. In practice, manufacturing systems frequently use both.

For a deeper explanation of product models, dependencies and validation, see the manufacturing product configuration guide.

3. The visual model responds to configuration changes

After a valid selection or an in-progress selection, the visual layer updates the representation. A component may appear, disappear, move, change colour or change geometry. Dimensional labels may update when a parameter changes.

There are several common approaches:

Image-based configuration: The system switches product images or assembles layered images. This can be practical for products with a limited number of visual variants.
Parametric 3D configuration: A three-dimensional model changes dimensions, components or geometry based on configuration variables.
Component assembly: The viewer combines reusable 3D parts into an assembly. This is useful when options correspond to modular components.
CAD-driven visualization: Configuration data is passed to a CAD or engineering automation process that produces a product-specific model or drawing.
Web-based 3D visualization: A browser-based viewer displays models using web-compatible formats and communicates with the CPQ application through APIs.

The visual output may be immediate, while a detailed CAD regeneration happens later. This distinction matters. A lightweight viewer can provide fast interaction, but it may not represent every manufacturing detail. A CAD-generated output can be more authoritative, but it may require more processing time and engineering data.

4. Engineering calculations and validation are applied

Visual changes should not be treated as proof that a configuration is manufacturable. The system may need to perform engineering calculations such as:

Motor sizing and power requirements.
Pump duty-point or pressure calculations.
Structural load and deflection checks.
Thermal or airflow calculations.
Electrical load, voltage and enclosure calculations.
Clearance, reach and interference checks.
Material quantity and dimensional calculations.
Weight, centre-of-gravity or transport calculations.

Some CPQ platforms provide calculation features; others call external engineering services, CAD systems or custom applications. Manufacturers should verify whether a claimed calculation is a formal engineering validation, a simple sizing formula or only a recommendation.

5. The configured product produces commercial and manufacturing outputs

Once the configuration is valid, the CPQ application can calculate price and generate quote content. In manufacturing, the output may also include structured product data.

A typical result can contain:

Configured product identifier and revision.
Selected options and parameter values.
Technical specifications.
Pricing, discounts, surcharges, taxes or freight assumptions.
Configurable BOM or order-specific BOM.
Engineering notes and approval status.
Product images, rendered views or drawings.
CAD files or references to generated CAD outputs.
Data for enterprise resource planning (ERP), customer relationship management (CRM), product lifecycle management (PLM) or manufacturing execution systems (MES).

A BOM is not automatically the same as a CAD assembly. An engineering BOM (EBOM) describes the product from an engineering perspective. A manufacturing BOM (MBOM) structures components and operations for production. A configurable BOM may contain rules or options that resolve into an order-specific structure. The required output depends on whether the next step is quotation, engineering review, purchasing or manufacturing release.

The relationship between BOMs, pricing and quote generation is covered in the BOM, pricing and quoting guide.

Visual CPQ architecture

A practical visual CPQ architecture commonly includes the following components:

Layer	Responsibility	Typical data
Experience layer	Provides the configuration interface and visual interaction.	Questions, options, dimensions, views and user permissions.
Product model	Defines products, variants, components and attributes.	Features, materials, components, revisions and option relationships.
Rules and constraints	Validates combinations and derives values.	Dependencies, exclusions, formulas, constraints and approvals.
Visualization engine	Displays the configured product.	Images, 3D meshes, assembly metadata, camera views and annotations.
Engineering services	Performs calculations or generates technical outputs.	Parameters, sizing inputs, CAD templates, drawings and calculations.
Commercial engine	Calculates costs, prices and quote terms.	Price lists, cost models, discounts, currencies and approval thresholds.
Integration layer	Moves approved data between systems.	Product IDs, BOMs, configurations, orders, documents and status.

These layers may be delivered by one platform or distributed across CPQ, CAD, PLM, ERP and custom services. A manufacturer should evaluate the complete data flow rather than assuming that a single visual interface owns every product record.

How visual CPQ connects CAD and engineering automation

CAD means computer-aided design. In a visual CPQ workflow, CAD can be used in three different ways.

CAD as a visualization source

Existing CAD models can be simplified, converted or published for browser-based visualization. This approach provides a visual representation without regenerating the full engineering model for every interaction.

CAD as a parametric output engine

Configuration parameters can be passed to a parametric CAD template. The CAD process then changes dimensions, suppresses features, selects components or creates a product-specific assembly. The resulting model may be used to generate drawings, neutral files or manufacturing documentation.

CAD as a downstream engineering system

CPQ may send a validated configuration to CAD or product data systems after quotation or order approval. Engineering automation can then create or complete the detailed design. This is common where the product has significant engineered-to-order content.

These approaches have different governance requirements. A visual model may be suitable for communication but not for manufacturing release. A CAD output may be geometrically accurate but still require engineering approval, tolerance definition, material verification and production planning. More information is available in the CAD and engineering automation guide.

Manufacturing example: configuring an industrial pump skid

Consider a pump manufacturer selling configurable skid-mounted systems. The buyer or sales engineer selects flow rate, pressure, fluid type, temperature, motor voltage, pump material, valve arrangement, instrumentation and skid dimensions.

The visual CPQ process might work as follows:

The user enters duty requirements and installation constraints.
The system recommends compatible pump families and motor ranges.
Rules exclude materials that are unsuitable for the selected fluid or temperature.
The visualization adds the chosen pump, motor, valves, instruments and access features.
A calculation service checks pump selection and motor requirements.
Skid length and baseplate dimensions are recalculated.
The configured BOM includes the pump, motor, coupling, base, valves, fittings, instruments and fasteners.
Pricing applies component prices, engineering charges, options, freight assumptions and commercial approvals.
A quote displays the configured visual, technical specifications and commercial terms.
After approval, configuration data is sent to ERP and engineering systems for order processing and detailed documentation.

If the pump skid is standard enough for configure-to-order (CTO), the rules may resolve most of the design automatically. If each skid requires substantial new design work, the process may be engineer-to-order (ETO), with the visual configuration acting as a controlled starting point for engineering rather than a complete design release.

Visual CPQ in the sales-to-engineering handoff

The main operational value of visual CPQ is not only that customers can see a product. It can create a shared, structured definition of what was sold.

A strong handoff includes:

A unique configuration identifier.
Revision and model version.
All selected options and parameter values.
Resolved components and quantities.
Calculation results and assumptions.
Exceptions, warnings and engineering review requirements.
Approved drawings, images or CAD references.
Commercial status and approval history.

This is different from sending engineering a PDF or salesperson’s notes. Documents may be useful, but structured configuration data is easier to validate, reuse and map to ERP, PLM, PDM or MES processes. PDM means product data management, while MES means manufacturing execution system. Neither is interchangeable with CPQ: CPQ manages configuration and commercial decisions, whereas PDM manages product files and revisions and MES manages shop-floor execution data.

See the guide to configure-to-order, engineer-to-order and sales-to-engineering workflows for a broader process view.

Benefits of visual CPQ for manufacturers

Better product understanding: Sales teams, dealers and buyers can see the effect of options that are difficult to explain in text.
Earlier detection of misunderstandings: A visual representation can reveal incorrect orientation, access assumptions or missing accessories before order release.
Reduced manual re-entry: A structured configuration can be reused for pricing, quote documents, BOMs and engineering tasks.
More consistent sales engineering: Guided interaction and validation reduce dependence on individual spreadsheet knowledge.
Improved quote communication: The quote can show the actual proposed equipment rather than a generic catalogue image.
Faster variant definition: Standard components and rules can reduce repetitive design work for repeatable products.
Support for dealer and self-service channels: Visual configuration can make complex products easier to sell through authorized channels, provided the rules are governed centrally.

Limitations and risks

Visual CPQ does not remove the underlying complexity of engineered products. It can expose or manage that complexity, but it cannot compensate for poor product data or incomplete rules.

Visual accuracy may not equal engineering accuracy: A model can look correct while omitting tolerances, internal parts, materials or manufacturing constraints.
Large option spaces are difficult: Many product variants can create complex model maintenance and slow visualization performance.
CAD data may be unsuitable for direct web use: Detailed models often require simplification, conversion, security controls and performance testing.
Rules can become difficult to govern: Duplicated formulas and undocumented exceptions make changes risky.
Engineering calculations may remain external: Integration with specialist tools can require custom services, data mapping and validation.
Configuration and manufacturing structures may differ: The product selected by the customer may need transformation into an EBOM, MBOM or production order structure.
ETO work still needs engineering review: A visual configuration should not be presented as automatic design release when substantial engineering remains.
Data ownership can be unclear: Product, CAD, price and manufacturing data may be maintained by different departments and systems.

Implementation considerations

Define the authoritative product model

Decide which system owns product definitions, component identifiers, revisions, materials, CAD references and lifecycle status. CPQ may consume data from PLM or PDM rather than becoming the master for every engineering object.

Separate visual, configuration and engineering data

Map each visual object to a controlled product option or component. Do not rely on image names or informal labels as the only connection between what the user sees and what the ERP or engineering system receives.

Prioritize high-value configuration paths

Start with products where visual errors, engineering rework or quote delays create measurable operational problems. A focused model is easier to test than an attempt to represent every product family at once.

Test rules and outputs together

Test not only whether the interface allows or blocks a choice, but also whether the resulting price, BOM, CAD output, technical specification and integration message are correct. Use valid, invalid, boundary and change-impact test cases.

Plan model governance

Assign ownership for rules, visual assets, CAD templates, prices, BOM mappings and integrations. Establish review processes for product revisions, obsolete components, engineering changes and market-specific pricing.

Measure operational outcomes

Useful measures may include configuration error rate, engineering clarification workload, quote cycle time, percentage of quotes requiring manual re-entry, BOM correction rate, CAD automation success rate and time from order approval to engineering release. Measures should distinguish improvements caused by better rules from improvements caused only by a redesigned user interface.

Implementation planning, migration, testing and governance are discussed in the manufacturing CPQ implementation guide. System boundaries and integration patterns are covered in the CPQ integration guide.

How to evaluate visual CPQ software

Evaluation question	Why it matters
Can the platform represent dimensions, dependencies, constraints and calculated values?	Visual interaction is useful only when it reflects valid product logic.
Does the 3D viewer use configurable components, parametric geometry or static assets?	This determines how accurately variants and dimensions can be represented.
Can the system generate or exchange BOM data?	Manufacturing handoff requires structured product output, not only images.
How does it connect to CAD, PLM, PDM and ERP?	Integration determines whether configuration data can be reused downstream.
Are engineering calculations native or external?	The answer affects architecture, validation and implementation effort.
Can users distinguish warnings, invalid states and engineering review requirements?	Not every non-standard configuration should be silently accepted.
How are visual assets and product rules versioned?	Visual output must remain aligned with released product definitions.
Can the platform support CTO and ETO workflows?	Manufacturers need to know whether the result is an order-ready configuration or an engineering starting point.
Are APIs available for headless, dealer or ecommerce channels?	Multiple channels may need to use the same product model and rules.

Do not evaluate visual CPQ by screenshots alone. Request a demonstration using representative products, including dimensional changes, incompatible options, calculated selections, BOM output, CAD handoff and an ERP or PLM integration scenario where relevant.

Visual CPQ versus related technologies

Technology	Primary role	Relationship to visual CPQ
Product configurator	Defines and validates product options.	Visual CPQ adds an interactive representation and may connect configuration to quoting and engineering.
CAD automation	Creates or modifies technical geometry and drawings.	Visual CPQ may supply parameters or consume CAD outputs.
Product visualization	Displays products in 2D or 3D.	Visualization may exist without rules, pricing or manufacturing outputs.
Guided selling	Recommends products or options based on requirements.	It can be part of the interface but does not replace configuration validation.
CRM	Manages customer, opportunity and sales activity data.	CRM may launch CPQ and store quote status but is not normally the product rules authority.
ERP	Manages enterprise, order, inventory, purchasing and financial processes.	ERP may receive configured items, BOMs, prices or orders from CPQ.
PLM or PDM	Manages product definitions, files, revisions and lifecycle data.	These systems may provide controlled engineering data to CPQ.

Frequently asked questions

What is visual CPQ?

Visual CPQ is CPQ software that combines product configuration and quoting with an interactive 2D or 3D representation of the configured product. In manufacturing, it may also connect to engineering, BOM, CAD and enterprise workflows.

How is visual CPQ different from a product configurator?

A product configurator validates options and parameters. Visual CPQ adds a visual representation and commonly connects the validated configuration to pricing, quoting and downstream outputs. The exact scope depends on the software.

Does visual CPQ always include 3D?

No. Some implementations use 2D images, layered graphics, drawings or simplified product views. Three-dimensional visualization is an option, not a requirement for every visual CPQ project.

Can visual CPQ generate CAD models?

Some platforms integrate with CAD automation or parametric templates, while others only display prepared visual assets. CAD generation should be verified for the specific CAD system, product family and required output.

Can visual CPQ generate a BOM?

Some manufacturing CPQ systems can resolve a configurable BOM or produce an order-specific BOM. Others pass configuration selections to ERP, PLM or a separate BOM service. This capability should not be assumed.

Is a visual model the same as a manufacturing model?

No. A visual model may omit internal components, tolerances, materials or production information. It can communicate the proposed product without being suitable for manufacturing release.

What product data does visual CPQ require?

It commonly requires product families, options, components, attributes, dimensions, rules, visual assets, prices and identifiers. Engineering use cases may also require CAD templates, calculation inputs, BOM mappings and revision data.

What rules are used in visual product configuration?

Typical rules define compatibility, dependencies, exclusions, required components, dimensional calculations, engineering limits and commercial conditions. Rules may be represented as constraints, formulas, decision tables or scripts.

Can visual CPQ support engineer-to-order products?

It can support ETO by capturing requirements, creating a controlled starting configuration and passing structured data to engineering. It does not automatically eliminate engineering design work or approval.

What is the role of CAD in visual CPQ?

CAD can provide visualization assets, respond to configuration parameters, generate product-specific geometry or produce drawings. The role depends on whether the manufacturer needs communication-quality visuals or engineering-grade outputs.

How does visual CPQ support configure-to-order?

For CTO products, the system can validate selections within a predefined product model, resolve components and pass the result to order and production processes. The degree of automation depends on data quality and integration.

Can customers use visual CPQ directly?

Yes, some manufacturers expose visual configuration to customers, dealers or ecommerce users. The interface should limit access to appropriate options and protect pricing, engineering and product data.

Does visual CPQ replace sales engineers?

No. It can automate repeatable selections and reduce manual work, but sales engineers remain important for unusual applications, requirements analysis, engineering review and non-standard configurations.

How does visual CPQ connect to ERP?

It may send configured product identifiers, option values, prices, BOMs, documents or order data through APIs, middleware or integration services. The exact mapping depends on the ERP and the manufacturer’s process.

How does visual CPQ connect to PLM or PDM?

It may consume released product, CAD and revision data from PLM or PDM, or send approved configuration information back for engineering processing. System ownership and revision control must be defined explicitly.

What is the biggest implementation risk?

A common risk is building an attractive visual interface without a governed product model, rules, identifiers and downstream data structure. The result may look correct but still require manual engineering correction.

How should manufacturers test visual CPQ?

Test valid and invalid combinations, dimension boundaries, rule changes, visual accuracy, prices, BOMs, CAD outputs, approval paths and integration messages. Test complete product scenarios rather than isolated interface controls.

Semantic map

The relationships below summarize how visual CPQ connects configuration, visualization, engineering and manufacturing systems.

Visual CPQ uses product models to represent configurable products.
Configuration rules prevent invalid combinations.
Constraints validate dimensions, capacities and engineering limits.
Configured options update visual product representations.
Parametric CAD uses configuration parameters to generate product-specific geometry.
Configured products generate configurable BOMs or order-specific BOMs.
Engineering calculations validate technical requirements.
CPQ calculates prices from configured components and commercial rules.
CPQ generates quotes containing technical and commercial information.
CPQ exchanges configuration data with ERP.
CPQ may consume controlled product data from PLM or PDM.
CAD automation generates product-specific drawings and technical files.
Visual CPQ supports sales-to-engineering handoff.
Configure-to-order uses validated product configurations for repeatable manufacturing.
Engineer-to-order uses configured requirements as a starting point for engineering work.

Conclusion

Visual CPQ works by connecting an interactive representation of a product to a governed product model, configuration rules, engineering calculations, pricing logic and downstream systems. Its value in manufacturing comes from making the configured result understandable while preserving the structured data required for quoting, engineering and production.

The strongest implementations do not treat visualization as a decorative front end. They map every meaningful visual choice to controlled product data, validate the configuration, distinguish visual output from engineering release, and define how the result becomes a BOM, CAD output, quote, order or engineering task. Manufacturers should therefore evaluate visual CPQ as part of the complete configuration and engineering architecture rather than as an isolated 3D viewer.

September 18, 2026

Photorealistic Product Visualization in CPQ: Manufacturing Guide

Photorealistic product visualization in CPQ is the generation of realistic images, interactive 3D models or rendered views of a configured product during the configure, price, quote process. In manufacturing, the visual output should reflect the selected product options, dimensions, materials, finishes, accessories and major engineering decisions rather than showing a generic marketing image.

A manufacturing CPQ system may use a product model, configuration rules, parametric CAD data, 3D assets and rendering services to show a pump skid, industrial enclosure, material-handling vehicle, HVAC unit or machine assembly as it is configured. The visualization can support guided selling and customer approval, while the same configuration may also produce pricing, a configurable bill of materials (BOM), engineering calculations, CAD outputs or an order handoff.

Not every CPQ platform includes photorealistic rendering, interactive 3D, CAD automation or manufacturing BOM generation. Buyers should evaluate these capabilities separately and verify how visual data is synchronized with the product model, engineering systems and downstream manufacturing processes.

What photorealistic visualization means in manufacturing CPQ

Photorealistic visualization is a rendered representation of a configured product that aims to resemble the physical product in shape, proportion, color, material, lighting and component placement. It is more than displaying a static catalog photograph. The image or 3D scene changes when the user selects valid product options.

For example, a configurable industrial air-handling unit might change visually when a user selects a different casing width, access-door arrangement, filter section, fan type, roof package or exterior finish. A realistic view can help a sales engineer confirm that the selected arrangement matches the customer requirement. It can also expose misunderstandings before an order reaches engineering.

In manufacturing CPQ, visualization is normally one part of a larger product definition. The visual representation should be linked to configuration attributes and not maintained as an unrelated illustration. A selection such as stainless steel casing may affect the rendered material, price, weight, BOM components and manufacturing instructions.

How visual CPQ differs from generic sales CPQ

Generic sales CPQ often focuses on selecting products, applying discounts and producing a quote. Visual CPQ adds an interactive or rendered product representation, but manufacturing applications usually require a deeper relationship between the visual model and engineering data.

Area	Generic sales CPQ	Manufacturing visual CPQ
Primary purpose	Select items and calculate a commercial offer	Represent and validate a technically configurable product
Product data	Catalog products, options and prices	Features, dimensions, materials, components, geometry and engineering attributes
Visual output	Product image or basic option image	Configuration-specific 2D, 3D or photorealistic representation
Rules	Compatibility and commercial rules	Compatibility, dimensional, structural, performance and manufacturing constraints
Downstream output	Quote, proposal or sales order	Quote plus BOM, CAD files, drawings, calculations or engineering handoff where supported
Typical users	Sales representatives	Sales engineers, application engineers, dealers, customers and manufacturing teams

A visually attractive interface does not automatically make a CPQ system suitable for engineered products. The important question is whether the displayed configuration is controlled by the same governed data and rules used for pricing and downstream outputs.

Where visualization fits in the CPQ architecture

A visual CPQ solution commonly contains several connected layers. The exact architecture varies by platform and implementation, but the following components are typical.

Product model: Defines families, variants, options, attributes, dimensions, components and relationships. The product model is the basis for the configuration rules and product configuration.
Rules and constraints: Determine which combinations are valid. Rules may control compatibility, required components, allowable dimensions, material restrictions, performance limits or manufacturing feasibility.
Configuration state: Stores the selected options and calculated values for a specific product instance. This state should be identifiable and reusable by pricing, visualization, BOM and engineering services.
Visual asset library: Contains 2D images, 3D geometry, textures, materials, decals, animations and camera views. Assets may represent complete products, subassemblies or interchangeable components.
Geometry or CAD service: Updates parametric geometry, assembles components or calls a computer-aided design (CAD) automation process. Some systems use lightweight 3D geometry for performance while others generate more detailed engineering outputs separately.
Rendering engine: Produces a browser-based 3D scene, real-time view, still image or high-quality rendered output. Rendering may occur in the browser, on a server or through an external visualization service.
Commercial and engineering services: Calculate price and cost, generate a BOM, perform engineering calculations or create drawings when those capabilities are available.
Enterprise integrations: Exchange data with customer relationship management (CRM), enterprise resource planning (ERP), product lifecycle management (PLM), product data management (PDM), manufacturing execution systems (MES) or CAD platforms.

The CAD and engineering automation layer may be tightly embedded in CPQ or connected through application programming interfaces (APIs). A visual model is not necessarily an engineering model. The implementation must define which system owns dimensions, part numbers, geometry, materials and revision status.

Data required for photorealistic product visualization

Realistic visualization depends on more than a collection of photographs. A maintainable implementation normally requires structured product and visual data.

Data type	Examples	Why it matters
Configuration attributes	Width, height, capacity, motor size, voltage, orientation	Controls valid choices and visual changes
Component mappings	Fan, valve, guard, access panel, bracket, cable tray	Determines which components appear in the scene or assembly
Geometry	Parametric CAD, lightweight meshes, assembly transforms	Controls dimensions, placement and proportions
Materials	Paint, stainless steel, galvanized steel, glass, rubber	Controls surface appearance and may affect price or manufacturing
Appearance assets	Textures, decals, labels, logos and finishes	Improves realism and supports customer-specific presentation
Camera and scene data	Views, lighting, environments and exploded positions	Creates consistent product views for quotes and approvals
Revision metadata	Effective date, product revision, asset revision, status	Prevents obsolete or visually incorrect representations

Manufacturers should also decide whether the visual model is authoritative for any business decision. For example, a rendered pipe route may be illustrative while the CAD assembly and engineering calculation remain authoritative. This distinction should be clear to users and documented in the implementation.

How configuration rules control the visual output

Visualization should respond to the same valid configuration state used elsewhere in CPQ. This requires a clear relationship between options and visual behavior.

Rules-based configuration

Rules-based configuration uses explicit logic such as: if a roof-mounted fan is selected, show the fan assembly; if a left-hand access door is selected, place the door on the left side; if a high-voltage motor is selected, show the associated control cabinet label.

Constraint-based configuration

Constraint-based configuration evaluates permitted values and relationships, often across dimensions, performance requirements and engineering limits. For example, a pump selection may need to satisfy flow, head, fluid temperature, motor availability and pipe connection constraints. The visual model can show the selected pump and connected fittings, but the constraint engine determines whether the combination is technically valid.

Guided selling

Guided selling asks users requirement-oriented questions and recommends or restricts product choices. It may hide technical complexity from a customer or dealer. Guided selling can drive visualization, but it is not the same as a complete engineering rules engine. A guided question such as “What airflow is required?” may lead to a product selection, while engineering rules still need to validate fan, casing and electrical combinations.

When the configuration changes, the system may update the scene through one or more methods:

showing or hiding a predefined component;
changing the position or orientation of an assembly;
scaling a parametric section within permitted limits;
swapping a mesh or CAD representation;
changing material, finish or color;
updating labels, dimensions or callouts;
regenerating a CAD assembly or engineering drawing.

Relationship between visualization, CAD and engineering automation

Photorealistic visualization and CAD automation are related but different capabilities. Visualization prioritizes understandable presentation and interactive performance. CAD automation prioritizes geometric accuracy, engineering reuse, drawings and manufacturing outputs.

A manufacturer may use lightweight visual geometry in the browser while generating a precise CAD model on the server after configuration approval. In another architecture, a parametric CAD model may drive both the visual scene and the engineering output. The right approach depends on product complexity, rendering performance, required accuracy and the systems already used by engineering.

Output	Typical purpose	Accuracy expectation
Photorealistic still image	Quote, proposal or customer presentation	Visual and configuration accuracy; not necessarily manufacturing geometry
Interactive 3D model	Option selection, review and spatial understanding	Correct component presence, placement and proportions
Parametric CAD assembly	Engineering validation and design reuse	Engineering geometry and controlled parameters
2D drawing	Manufacturing, installation or approval documentation	Defined dimensions, views, annotations and revision control
Manufacturing BOM	Procurement, production and assembly	Correct parts, quantities, revisions and manufacturing structure

More information about this distinction is covered in the guide to CAD automation and engineering automation in CPQ. A rendering should not be presented as a certified drawing unless it has passed the required engineering and document-control process.

Example: visualizing a configurable pump skid

Consider a manufacturer selling packaged pump skids. The configuration includes pump type, flow range, motor rating, base-frame length, pipe material, valve arrangement, instrumentation, enclosure and paint finish.

The CPQ workflow may operate as follows:

The user selects the required duty point and installation environment.
Configuration logic restricts pumps, motors and materials that do not satisfy the requirements.
The system selects or recommends a pump and motor combination.
The visual scene displays the pump, motor, frame, valves, gauges and pipe arrangement.
Changing the discharge orientation moves the connected pipework and valve group.
Selecting stainless steel changes the appearance and may update material-related pricing and components.
The system calculates price and cost and creates a configurable BOM if supported.
After review, the configuration is passed to engineering for CAD regeneration, drawing creation or further ETO work.

ETO means engineer-to-order: the product is configured from a platform but requires additional engineering before production. CTO means configure-to-order: the product is assembled from predefined, validated options with limited design work. Photorealistic visualization can support both models, but it does not remove the engineering work required by an ETO product.

Sales-to-engineering handoff

The strongest manufacturing use case is not simply showing a product in 3D. It is preserving the approved configuration as a structured handoff. The quote, visual approval and engineering request should refer to the same configuration identifier and revision.

A handoff may include:

selected options and calculated dimensions;
configuration rules or validation status;
customer-approved images or 3D views;
part numbers and quantities;
preliminary or manufacturing BOM, clearly identified by type;
performance calculations and assumptions;
CAD generation parameters;
exceptions requiring engineering review;
commercial information and approval status.

An engineering bill of materials (EBOM) describes the product from an engineering perspective. A manufacturing bill of materials (MBOM) organizes the product for production, including manufacturing assemblies, operations or shop-floor requirements. A configurable BOM may contain rules or placeholders that resolve after selections are made. These structures should not be treated as interchangeable. The guide to BOM generation, pricing and quoting explains how these outputs relate to CPQ.

Benefits of photorealistic visualization in manufacturing CPQ

Better understanding of complex options

Industrial products can contain hidden components, multiple orientations and unfamiliar technical terms. A visual representation helps users understand the physical result of a selection such as an access side, discharge position or enclosure type.

Earlier detection of configuration misunderstandings

A customer may approve a configuration more confidently when the quote shows the selected door arrangement, material finish, control panel location or accessory package. Visual review can reveal an incorrect assumption before order entry, although it does not replace technical validation.

More useful proposals and dealer tools

Dealers and distributors can present a configuration-specific proposal instead of combining generic product photographs with manually written descriptions. This is particularly useful when a product has many visible options.

Reduced manual illustration work

Where visual assets and rules are well maintained, the system can generate views for many valid variants without requiring an engineer or marketing specialist to create every image manually.

Improved continuity from quote to order

When the approved visual state is connected to the configuration record, sales, engineering and production can work from a common reference. The benefit depends on data governance and integration quality rather than rendering quality alone.

Limitations and risks

Visual accuracy can lag product changes. New components, finishes or revisions require corresponding asset and rule updates.
A realistic image can create false confidence. A product may look correct while violating a load, clearance, electrical or performance constraint if those rules are not implemented.
Visual geometry may not be manufacturing geometry. Lightweight meshes may omit internal structure, tolerances, fasteners or production details.
Large assemblies can affect performance. High-resolution models and textures can cause slow loading, especially in browser-based configurators or dealer environments.
Rendering is not a substitute for engineering approval. ETO products may still require calculations, design review and controlled drawings.
Asset maintenance can be expensive. Each family of components may require geometry, materials, lighting, camera and rule mappings.
Color and material representation is approximate. Screens, lighting and rendering settings affect how paint, metal and surface treatments appear.
Integration boundaries can cause inconsistencies. If CAD, PLM and CPQ use different revisions or identifiers, the visual output may not match the released product.

Implementation approach

1. Select a product family with a clear business case

Start with a product that has visible configuration complexity and repeatable option structures. Industrial enclosures, pumps, HVAC units, conveyors and specialty vehicles are common candidates. Avoid beginning with a product whose geometry is still unstable or whose rules are undocumented.

2. Define the source of truth

Document which system owns product attributes, engineering revisions, CAD geometry, visual assets, prices and BOM structures. A product lifecycle management (PLM) or PDM system may govern engineering data, while CPQ manages the selling configuration. An ERP system may own released item and order data. These responsibilities must be explicit.

3. Build the product model before polishing the visuals

Identify features, options, dependencies, dimensions, constraints and component mappings. Separate configuration rules from presentation rules where possible. For example, “a stainless-steel option is available” is a product rule; “use a brushed-metal texture” is a visual mapping.

4. Create a reusable visual asset strategy

Use modular components and standard naming. Define coordinate systems, attachment points, material names, camera conventions, texture resolution and versioning. Reusable assets reduce duplication when the same motor, valve or control box appears across several product families.

5. Define accuracy levels

Decide whether each output is illustrative, configuration-accurate, dimensionally indicative or engineering-authoritative. These labels should appear in requirements and user guidance. A quote image may have a different accuracy requirement from a drawing released to production.

6. Connect the visual state to downstream outputs

Test whether the selected options that change the image also change price, BOM, CAD parameters and engineering documentation where appropriate. The CPQ integration architecture should define identifiers, APIs, error handling, revision handling and synchronization timing.

7. Test combinations and revisions

Test valid and invalid combinations, boundary dimensions, component substitutions, discontinued parts, material changes and regional variants. Compare the visual result with the configuration record and, where applicable, the generated CAD assembly and BOM.

8. Establish governance

Assign ownership for rules, product data, CAD assets, visual assets, pricing, integrations and release approval. A change to a component can affect geometry, appearance, cost, lead time, BOM and technical documentation. Governance should cover all of these dependencies.

The broader CPQ implementation guide covers requirements, data migration, testing, deployment, governance and maintenance in more detail.

Evaluation checklist for visual CPQ software

When evaluating a platform, ask vendors and implementation partners specific questions rather than accepting “3D visualization” as a complete capability.

Can the system display configurable 3D assemblies, or only swap static images?
Can visuals respond to dimensions, orientations, materials and component selections?
Is the visual model linked to the same configuration state used for pricing and BOM generation?
Does the platform support browser-based viewing, server rendering, downloadable images or all three?
Can it use CAD, mesh or lightweight geometry, and how are those assets imported?
Can it generate or exchange CAD parameters and drawings, or is it visualization-only?
How are visual assets versioned when an engineering revision is released?
How are invalid, incomplete or engineering-review configurations represented?
Can users create approved views for proposals, customer sign-off and order records?
What APIs are available for CAD, PLM, PDM, ERP, CRM and document systems?
How does the platform handle large assemblies and mobile or dealer access?
Which BOM types can it generate: configurable BOM, EBOM or MBOM?
Can the system support CTO, ETO, make-to-order (MTO) or assemble-to-order (ATO) workflows?
What tools exist for testing rules and visual mappings after a product change?
Which capabilities are native, which require customization and which require third-party software?

These questions help distinguish a genuine manufacturing visualization workflow from a catalog image feature. Vendor profiles and comparisons should document the answers for each platform rather than infer them from marketing terminology.

Key performance and quality measures

Manufacturers can evaluate the implementation with operational measures such as:

percentage of valid configurations that produce the expected visual state;
number of visual mismatches found during engineering review;
time required to create a configuration-specific proposal;
time required to update visual assets after a product revision;
frequency of manual corrections to configuration, BOM or CAD data;
user completion rate for dealer or customer configuration;
rendering and model-load performance for representative assemblies;
percentage of approved configurations transferred without rekeying;
number of engineering exceptions generated after sales approval.

These measures should be interpreted with product complexity in mind. A visual configurator for a small set of modular enclosures will have different targets from one supporting engineered machinery or specialty vehicles.

Semantic map

The following relationships summarize how photorealistic product visualization fits into manufacturing CPQ:

CPQ configures configurable industrial products.
Configuration rules prevent invalid product combinations.
Configuration attributes control visual component mappings.
Visual component mappings assemble a 3D product scene.
Photorealistic rendering presents configured product appearance.
CAD automation generates product-specific engineering geometry.
Configured products generate pricing and quote outputs.
Configured products may generate configurable BOMs.
EBOMs describe engineering product structures.
MBOMs organize products for manufacturing.
CPQ exchanges configuration data with ERP systems.
PLM and PDM systems govern engineering product data.
Approved configurations support sales-to-engineering handoff.
ETO workflows require additional engineering after configuration.
CTO workflows use predefined and validated product options.

Frequently asked questions

What is photorealistic product visualization in CPQ?

It is the generation of realistic images or interactive 3D views that represent a configured product during the CPQ process. In manufacturing, the view should respond to relevant options, dimensions, materials and component selections.

Is photorealistic visualization the same as 3D product configuration?

No. 3D product configuration describes the interactive selection and assembly of product components. Photorealistic visualization focuses on rendering appearance. A 3D configurator may use simplified geometry, while a photorealistic viewer emphasizes materials, lighting and realism.

Does every manufacturing CPQ platform support visualization?

No. Some platforms provide static images or basic option images, while others support interactive 3D, rendered scenes or CAD-linked visualization. Each capability should be verified in the vendor documentation and evaluated against the target product.

Does visual CPQ generate CAD files?

Not necessarily. Visualization and CAD automation are separate capabilities. Some platforms integrate with CAD systems or generate engineering geometry, while others only present visual assets.

Can a rendered image be used as a manufacturing drawing?

Usually not. A rendered image is generally a presentation or review output. Manufacturing drawings require controlled dimensions, annotations, tolerances, revisions and engineering approval.

How do configuration rules affect visualization?

Rules determine which options are valid and how the visual model changes. They may show or hide components, move assemblies, change dimensions, swap materials or trigger a new CAD representation.

What is the difference between visual rules and product rules?

Product rules control technical or commercial validity, such as whether a motor is compatible with a voltage. Visual rules control representation, such as which motor model or material texture appears in the scene.

Can photorealistic visualization support engineer-to-order products?

Yes, but it does not eliminate engineering work. It can communicate the intended configuration and support customer approval, while engineers may still need to calculate, design, validate and release the final product.

What is a configurable BOM in a visual CPQ workflow?

A configurable BOM is a product structure that resolves into specific components and quantities based on selected options. The visual model may help users understand the result, but the BOM must be generated and governed independently according to manufacturing requirements.

How does an EBOM differ from an MBOM?

An EBOM, or engineering bill of materials, represents the design structure. An MBOM, or manufacturing bill of materials, organizes components for production and may include manufacturing assemblies or operations. A visualization does not determine which BOM structure is correct.

What systems typically integrate with visual CPQ?

Depending on the implementation, visual CPQ may integrate with CAD, PLM, PDM, ERP, CRM, product information management (PIM), MES and document systems. The presence and depth of each integration varies by platform.

Should CPQ or PLM own visual assets?

There is no universal answer. PLM or PDM may govern engineering-linked assets, while CPQ may manage selling-specific mappings. The important requirement is clear ownership, revision control and reliable synchronization.

What are the main costs of implementing photorealistic visualization?

Costs may include product-model analysis, CAD or mesh preparation, material and texture creation, rule mapping, integration, rendering infrastructure, testing and ongoing maintenance. The effort increases with product variety, geometry complexity and required accuracy.

Can customers configure products directly in a browser?

Yes, if the platform supports browser-based configuration and the manufacturer chooses to expose it. Access may be provided to customers, dealers or internal sales teams, with different levels of technical detail and approval control.

How should manufacturers test a visual configurator?

Test valid and invalid combinations, dimensional boundaries, materials, orientations, component substitutions, product revisions, rendering performance and agreement between the visual result, price, BOM and engineering outputs.

What happens when an engineering revision changes a visible component?

The manufacturer should update the relevant geometry, visual asset, rule mapping and revision metadata, then retest affected configurations. The system should prevent obsolete assets from appearing in new quotes where appropriate.

Does photorealistic visualization improve configuration accuracy?

It can improve user understanding and expose visible misunderstandings, but it does not guarantee technical accuracy. Configuration rules, engineering calculations and controlled product data remain necessary.

September 16, 2026

Augmented Reality in Manufacturing CPQ: Engineering, CAD and Configuration Workflows

Augmented reality in manufacturing CPQ combines augmented reality (AR) with configure, price, quote (CPQ) processes so users can review a configured product in a real or simulated environment before it is quoted, engineered or manufactured. A CPQ system may use the selected options, dimensions, materials, accessories and engineering outputs to display a product-specific 3D model, identify components, show clearances or guide an assembly review.

In manufacturing, AR is not simply a visual sales feature. Its value depends on whether the AR experience is connected to a governed product model and reliable engineering data. When connected correctly, a configuration can produce a validated visual representation, a bill of materials (BOM), pricing, drawings and downstream manufacturing information. When it is not connected, AR may show an attractive but generic model that does not represent the product being quoted.

This guide explains where AR fits in a manufacturing CPQ architecture, how data moves between configuration and engineering systems, which use cases are practical, and what manufacturers should verify before implementation.

What is augmented reality in manufacturing CPQ?

Augmented reality in manufacturing CPQ is the use of digital overlays, 3D models and contextual product information to present a configured industrial product in the user’s physical environment or field of view.

For example, a sales engineer configuring a pump skid could use AR to place the selected skid in a plant area. The visualization might show the chosen pump, motor, frame, pipe connections and control enclosure. It could also display approximate footprint, service access zones and connection locations. The underlying CPQ configuration should determine which model variants and dimensions appear.

AR is therefore an interaction and visualization layer around CPQ data. It does not replace:

Product configuration, which selects valid options and applies dependencies and constraints;
Engineering calculation, which determines whether the selected product meets duty, load, capacity or dimensional requirements;
CAD, or computer-aided design, which represents product geometry and can produce drawings or design outputs;
BOM generation, which identifies components required for a configured product;
Pricing and costing, which calculate commercial values; or
Enterprise integration, which transfers approved information to systems such as enterprise resource planning (ERP), product lifecycle management (PLM) or customer relationship management (CRM).

A manufacturing CPQ platform may support some of these functions directly, integrate with specialist systems, or provide only the configuration and quotation layer. Buyers should verify the documented scope of each product rather than assuming that a CPQ system includes native AR, CAD automation or engineering automation.

How AR fits into a manufacturing CPQ architecture

A typical architecture contains several connected layers. The product model defines what can be configured. The rules engine validates selections. Engineering services calculate dimensions or performance. CAD and visualization services produce geometry. The AR application displays the resulting model on a device. Commercial and enterprise systems manage pricing, quotes, orders and production data.

Layer	Typical responsibility	AR relationship
Product model	Defines options, features, attributes, variants and component relationships.	Determines which product components and visual assets may be displayed.
Rules and constraints	Prevents incompatible combinations and validates technical conditions.	Prevents the AR view from representing an invalid configuration.
Engineering logic	Calculates capacity, dimensions, performance, loads, clearances or selections.	Supplies configuration-specific values and geometry parameters.
CAD and 3D services	Generate or retrieve parametric models, assemblies, drawings and lightweight visualization files.	Provide the three-dimensional assets rendered by the AR experience.
CPQ commercial layer	Calculates cost, price, discounts, lead time and quote content.	Associates the displayed configuration with a quote or opportunity.
ERP, PLM, PDM and MES	Manage enterprise, lifecycle, design, production and execution data.	Supply approved revisions, item identifiers and manufacturing context where required.

A product data management (PDM) system manages design files and revisions, while PLM manages product lifecycle information, structures, changes and governance. A manufacturing execution system (MES) manages production execution. These systems are related but not interchangeable. An AR application should use approved and traceable data, especially when the visual output is used for engineering review or production support.

Data flow from configuration to AR

The exact implementation varies, but a common flow is:

Start with requirements. A user enters application data such as flow rate, pressure, voltage, payload, dimensions, environment or vehicle use case.
Apply configuration rules. The CPQ product model enables valid options and rejects incompatible selections. For example, a motor voltage may be restricted by the selected electrical standard, and a frame size may depend on pump capacity.
Run engineering calculations. A calculation service may determine shaft size, heat exchanger area, structural dimensions, cable length or required safety factors.
Resolve product identity. The system identifies selected components, part numbers, variants and revision-controlled assemblies.
Generate or retrieve 3D data. The solution obtains a lightweight model, a parametric CAD output or a prebuilt 3D asset that matches the configuration.
Apply metadata. Components can be associated with labels, service zones, technical attributes, item numbers, cost information or installation instructions.
Render the AR experience. The user places, rotates, measures or inspects the configured product using a supported device.
Return decisions to CPQ. The user may confirm the configuration, request a change, attach an image to the opportunity or send the result for engineering review.

The most important control point is the relationship between the product configuration and the 3D output. A model generated from different rules, an old CAD revision or a generic product family may create false confidence. The system should record the configuration version, CAD revision and relevant calculation results where the AR output influences a quote or design decision.

Manufacturing use cases for AR-enabled CPQ

Industrial machinery and equipment

Manufacturers of machinery can use AR to show how a configured machine fits into a customer’s facility. A configured conveyor, packaging machine or material-handling system may include different lengths, guards, drives, access doors and discharge directions. An AR view can help the customer review footprint, operator access and interfaces before quotation approval.

Pumps, valves and process skids

For pumps and valves, AR can display selected connection sizes, orientation, actuator position, motor arrangement and service access. In a skid configuration, the visual output can help reveal clashes with adjacent equipment. It should not be treated as a substitute for a certified layout or piping design unless the underlying geometry and engineering process support that use.

HVAC and electrical equipment

An HVAC CPQ workflow may use AR to show an air-handling unit, duct connections, service panels and clearance zones in a building area. An electrical equipment configuration may display enclosure dimensions, cable entry locations, busbar sections and selected accessories. Rules still need to validate ratings, environmental requirements and applicable product constraints.

Specialty vehicles and mobile equipment

Vehicle and mobile-equipment manufacturers can display a configured body, cab, tank, boom, tool carrier or accessory package. The visualization may support customer review of reach, access and interference. Engineering validation remains necessary for axle loads, structural limits, legal requirements, stability and production feasibility.

Sales-to-engineering handoff

AR can make handoff discussions more concrete. A sales engineer can mark a customer concern on the configured model and transfer the same configuration identifier, selected options, dimensions and attachments to engineering. This is more useful than sending an unstructured screenshot, provided the receiving team can trace the visual output back to the controlled product model.

Installation, service and production support

After the sale, the same product-specific data may support installation or service guidance. A technician could identify components, access panels or connection points using an approved model. However, this requires revision control and a clear distinction between a sales visualization and an authoritative service or work instruction.

AR compared with 3D product configuration and CAD automation

These capabilities overlap but solve different problems.

Capability	Primary purpose	Typical output
3D product configuration	Lets users inspect and manipulate a digital representation of a product.	Browser-based model, option visualization or interactive assembly.
CAD automation	Creates or modifies engineering geometry from parameters and rules.	Parametric CAD file, drawing, assembly or manufacturing geometry.
Augmented reality	Places digital content in a physical context or user field of view.	Device-based overlay, spatial review or guided visualization.
Virtual reality	Places the user in a fully digital environment.	Immersive simulated facility or product review.

A CPQ system may offer browser-based 3D without AR, or it may integrate with a separate visualization and AR platform. CAD automation may produce a precise engineering model while AR uses a simplified model for performance. The simplified model must still preserve the dimensions, interfaces and components relevant to the intended decision.

Benefits for engineering-driven manufacturers

Earlier spatial validation: Customers and sales engineers can identify footprint, access and interface problems before order release.
Clearer technical communication: A configured assembly can be easier to review than a text description or generic catalogue image.
More useful sales-to-engineering handoff: The same configuration identifier and visual context can accompany the request for engineering review.
Reduced ambiguity in options: Users can see the practical difference between accessories, orientations, enclosures and connection arrangements.
Support for complex products: AR is particularly useful when the product contains many physical options whose effects are difficult to communicate in a quote.
Potential reuse of engineering assets: Approved 3D models and metadata may support sales, installation, service and training, subject to governance.

These benefits depend on data quality. AR cannot correct an incomplete product model, missing constraints, inaccurate CAD geometry or an uncontrolled engineering process.

Limitations and implementation risks

Visual accuracy is not engineering validation

A model can look correct while failing a load, pressure, thermal, electrical or regulatory requirement. CPQ rules and engineering calculations must remain authoritative for those decisions.

Model preparation can be expensive

Detailed CAD assemblies may be too large for real-time AR. Manufacturers may need simplified meshes, material definitions, texture optimization, coordinate systems and separate visual variants. This creates another data-maintenance task.

Configuration and CAD may not align

A CPQ option may not map cleanly to a CAD feature. Some options change geometry, while others change only metadata, hardware, purchasing items or manufacturing operations. The implementation must define what appears visually and what is represented only in the BOM.

Revision and lifecycle control are essential

AR content associated with an obsolete CAD revision can mislead users. The system should define approval states, effective dates, ownership and traceability between product rules, CAD files, visual assets and production structures.

Devices and operating conditions affect usability

Lighting, network availability, tracking quality, screen size, protective equipment and factory conditions can affect the experience. A browser or tablet workflow may be more practical than specialized headsets for some sales and engineering teams.

AR may not be appropriate for every product

For a small configurable component, a 2D drawing or standard 3D viewer may provide sufficient value. AR is most justified when physical context, spatial relationships or customer understanding materially affect configuration and approval.

Implementation approach

Select a specific decision to improve. Start with a use case such as equipment footprint review, accessory selection or plant interface validation rather than an open-ended AR project.
Map the authoritative data. Identify which system owns product options, rules, CAD revisions, item numbers, BOM structures, calculations and customer requirements.
Define configuration-to-geometry mappings. Document how each relevant option changes the model, metadata, assembly structure or no visual output at all.
Choose the required fidelity. Decide whether users need a conceptual model, dimensionally reliable layout, engineering CAD output or a service-grade representation.
Design identifiers and traceability. Link the AR session to a configuration ID, quote revision, product revision and, where appropriate, CAD or PLM revision.
Test rule and visual consistency. Test valid and invalid combinations, boundary dimensions, substitutions, obsolete parts and engineering overrides.
Integrate with the sales and engineering workflow. Define how users request review, capture customer approval, transfer comments and update the quote.
Govern changes after launch. Assign ownership for product rules, CAD assets, visual content, device support and release testing.

Manufacturers should document requirements, integration boundaries and acceptance tests as part of the wider CPQ implementation process. The product model and rule governance should be designed alongside the AR experience, not after it.

Questions to ask when evaluating AR and CPQ software

Does the platform provide native AR, browser-based 3D, or an integration framework?
Can the AR model be generated from the exact configured options and dimensions?
How are CAD files simplified, versioned and approved?
Can visual components be linked to part numbers, BOM items and engineering attributes?
Does the solution support parametric geometry, prebuilt variants or both?
How are configuration rules shared between CPQ and CAD automation?
Can the system distinguish a sales visualization from an engineering-approved model?
How are revisions synchronized with PLM or PDM?
Can a user return comments, measurements or approval status to the quote?
What happens when an option has no visible geometry but changes cost, BOM or manufacturing work?
Are offline use, device management and access permissions supported?
Can the implementation handle configure-to-order (CTO) and engineer-to-order (ETO) products?

These questions should be evaluated with representative products, not only a demonstration model. Review a product with dimensional dependencies, optional components, substituted parts and at least one engineering exception.

Related manufacturing CPQ concepts

AR is one part of a broader engineering and commercial architecture. Read the guide to CAD and engineering automation for parametric models, drawings and calculations. The guide to product configuration and rules engines explains how options and constraints are modeled. For downstream structures and commercial outputs, see BOM generation, pricing and quoting. The manufacturing workflows guide covers configure-to-order, engineer-to-order and sales-to-engineering handoff. Integration patterns are described in the guide to CPQ integrations.

Semantic map

The following relationships summarize how augmented reality connects to manufacturing CPQ and engineering data:

Entity	Relationship	Related entity
CPQ	configures	configurable industrial products
Configuration rules	prevent	invalid option combinations
Configured product	generates	configuration-specific BOM
CPQ	exchanges data with	ERP
CAD automation	generates	product-specific geometry and drawings
AR application	displays	configured 3D model
Engineering calculations	determine	technical product parameters
PLM	governs	product revisions and lifecycle data
PDM	manages	CAD files and design revisions
AR review	supports	sales-to-engineering handoff
Configured options	control	visual components and metadata
Approved product model	supports	quote, engineering and production workflows

Frequently asked questions

What is augmented reality in manufacturing CPQ?

It is the use of digital overlays and configured 3D product content to show an industrial product in a physical or spatial context during configuration, quotation, engineering review or service.

Does every manufacturing CPQ system support augmented reality?

No. Some systems provide only rules, pricing and quoting. Others include 3D visualization or connect to external CAD, visualization or AR platforms. Native AR capability must be verified with the vendor.

How is AR different from 3D product configuration?

3D configuration displays and manipulates a digital product, often in a browser. AR places digital content into the user’s physical environment or field of view. A CPQ solution may provide one without the other.

Can AR generate a BOM?

AR normally does not generate the BOM itself. The CPQ or engineering system generates a configurable BOM, while AR displays selected components or metadata associated with that BOM.

Can AR replace CAD automation?

No. CAD automation creates or modifies engineering geometry and drawings. AR presents visual content. They can be connected, but they perform different functions.

What product data does AR-enabled CPQ require?

It commonly requires product options, configuration rules, dimensions, part identifiers, approved 3D assets, revision information and mappings between configuration selections and visual components.

Can AR show a completely engineered-to-order machine?

It can, if the engineering process produces suitable geometry and the AR workflow can consume it. ETO products usually require stronger review, revision and approval controls than standard CTO products.

How does AR support sales-to-engineering handoff?

It can provide a shared visual reference and transfer the configuration ID, selected options, dimensions, comments and attachments to engineering. The handoff is reliable only when the visual output remains traceable to controlled data.

Is an AR model the same as an engineering-approved model?

Not necessarily. AR often uses a simplified model optimized for performance. It should be labeled according to its purpose and should not be treated as an approved design without the required engineering validation.

Can AR validate physical clearances?

It can support an early clearance review when the model, scale, coordinate system and placement method are reliable. Formal layout, safety and compliance decisions may require certified drawings or engineering analysis.

What is the role of configuration rules in AR?

Rules ensure that the visualized product reflects valid combinations. For example, they can prevent an AR view from showing an incompatible motor, frame, enclosure or connection arrangement.

Does AR affect pricing and quoting?

AR does not inherently calculate price. It can improve option understanding and customer approval, while the CPQ pricing engine calculates cost, price, discounts, lead time and quote values.

Can AR use data from PLM or PDM?

Yes, an integration may retrieve approved CAD assets, revisions and metadata from PLM or PDM. The integration must define ownership, release status, access rights and revision synchronization.

Is AR useful for configure-to-order products?

Yes. CTO products often have repeatable option structures and reusable visual assets, making them practical candidates for AR-based configuration and customer review.

Is AR useful for make-to-order and engineer-to-order products?

It can be useful, but the value depends on how much geometry and engineering data exists before the order. ETO workflows need careful handling of design changes, approvals and model revisions.

What are the main risks of implementing AR in CPQ?

Common risks include inaccurate or obsolete models, weak configuration-to-CAD mappings, poor device usability, excessive model detail, unclear data ownership and treating visualization as engineering validation.

How should a manufacturer start an AR CPQ project?

Choose one high-value use case, such as reviewing equipment footprint or accessory placement. Map authoritative data, define model fidelity, connect the configuration to visual assets and test the workflow with real product variants.

What should buyers ask AR and CPQ vendors?

Ask whether AR is native or integrated, how models are generated and versioned, how options map to geometry, how BOM and CAD data are linked, how revisions are governed and how the result returns to the quote or engineering workflow.

September 13, 2026