CAD product configurator

Connect visual selling to engineering automation.

A CAD product configurator connects governed product choices with browser 3D, technical drawings, CAD automation or production data. The strongest architecture does not confuse those outputs: it defines which system owns every decision and proves that the accepted configuration remains the same from customer selection to engineering release.

Scope a CAD-connected configurator Plan the architecture

One accepted configuration

CX-CAD-1047 · revision 4

Traceable

Browser 3DCustomer-ready

Rules + priceValidated

Drawing jobReady for review

Order payloadMapped

A visual match is not enough. Product IDs, units, rule revisions, parameter values, generated files and approval state must remain connected.

Three valid meanings of “CAD product configurator.”

Buyers often use one phrase for three different operating models. Defining the model first prevents a fast web configurator from being judged like a native engineering system—or an engineering tool from becoming an unusable customer experience.

Web configurator with governed product data

Products whose sellable geometry can be represented with modules, dimensions, finishes and accessories without regenerating native engineering CAD for every sale.

Browser responsibility: The customer or salesperson configures a lightweight interactive 3D scene driven by accepted product rules.
CAD responsibility: CAD remains the engineering source for approved modules, profiles and technical references.

Connected visual CPQ and CAD automation

Made-to-measure products where a commercial configuration can safely drive approved drawings, derived files or parameterized engineering templates.

Browser responsibility: Configurix governs the buying journey, valid choices, 3D presentation, price context, saved revision and approval state.
CAD responsibility: A connected CAD automation service consumes accepted parameters and generates only the outputs defined in the implementation contract.

Engineering-led configuration with a sales surface

Complex or engineer-to-order systems where engineering rules, CAD automation or specialist calculations must remain authoritative.

Browser responsibility: The customer-facing experience collects requirements, guides preliminary choices and communicates an approved visual state.
CAD responsibility: Engineering software validates or generates the authoritative design before price, delivery or production acceptance is confirmed.

Interactive scope planner

Match the architecture to the product and output.

Select the product behavior and the strongest output you need. The recommendation shows where customer experience can lead and where engineering authority must remain.

Product behavior

Required output

Recommended operating model

Web configurator with governed product data

Products whose sellable geometry can be represented with modules, dimensions, finishes and accessories without regenerating native engineering CAD for every sale.

Model the product

Define typed dimensions, units, ranges and derived quantities once. Reconcile generated visuals and technical outputs at minimum, typical and maximum sizes.

Accept the output

Specify views, dimensions, units, title block, template revision, status and the exact downstream use of the drawing.

Keep the handoff traceable

The accepted configuration creates a structured specification, price, quote and optional BOM or order payload.

Give every decision one authoritative owner.

“CAD is the source of truth” is too broad. CAD can own engineering geometry while a catalogue owns sellable identity, a rule service owns compatibility and CPQ owns price. The integration should connect those authorities without silently duplicating them.

Decision	Typical authority	Contract	Control
Sellable catalogue and option identity	PIM, ERP or product catalogue owner	Product family, revision, option and component IDs	Do not infer commercial identity from a CAD body name or screenshot.
Compatibility and commercial rules	Product-rule service or governed configurator model	Allowed values, dependencies, exclusions, warnings and stops	One accepted rule result must drive the UI, price request and output request.
Customer-facing 3D state	Web configurator bound to accepted configuration data	Visible modules, materials, dimensions, motion and camera state	A realistic scene communicates the product; it is not automatically the manufacturing model.
Commercial price and discount	Pricing or CPQ service	Price list, market, account, quantity, services, tax and approval context	CAD mass or area can be an input, but commercial policy still needs an explicit owner.
Engineering geometry	CAD, PLM or engineering automation owner	Native model, feature logic, tolerances, drawings and approved derived geometry	The CAD revision used for generation must be recorded with the configuration revision.
BOM and production interpretation	ERP, PLM, MES or approved mapping service	Parts, quantities, variable dimensions, operations and effectivity	A sales BOM, configured order and manufacturing BOM are related but not interchangeable.
Released document or file	Named output service and approval workflow	File ID, type, template, source revision, status, checksum and retention	A download button should never conceal whether an output is illustrative, review-ready or production-released.

Name the output—and the authority it carries.

A screenshot, configured order, DXF, STEP model and released production package are different deliverables. Each needs its own input, generator, validation and approval status.

Commercial specification

Human-readable choices, dimensions, finish codes, accessories, images, price context and a configuration ID for a quote or CRM record.

Acceptance evidence

Reopen the exact saved revision and reconcile every displayed value.

Configured order payload

Stable product, component, parameter and quantity IDs delivered to ERP, CPQ, PLM or an order service through a versioned contract.

Acceptance evidence

A receiving system acknowledges the same configuration and mapping revision.

2D plan or technical drawing

A scoped PDF, SVG, DXF or other drawing output produced from accepted data or an approved automation template, with dimensions and status defined.

Acceptance evidence

Known dimensions, view rules, title block, units, revision and approval state pass acceptance.

Neutral 3D exchange file

A scoped STEP, IGES, STL, IFC, GLB or other derivative generated for a named downstream use—not a generic promise that every format preserves every feature.

Acceptance evidence

The target application imports representative files and verifies units, geometry, assemblies and metadata.

Native CAD automation result

A model or drawing generated in a specific authoring system from controlled templates, parameters, feature logic and a known software version.

Acceptance evidence

The automation job completes deterministically and the engineering owner approves boundary cases.

Production-released package

The accepted combination of files, BOM, cut or pick data, notes and approvals authorized for the factory or installation team.

Acceptance evidence

Release status, approver, source revisions, checksums and change procedure are retained.

Use a versioned CAD-output contract.

Treat output generation as a durable system integration. The request and response need enough identity to reproduce, diagnose, approve and supersede the result.

Configuration identity

configurationId, revision and lifecycle status

Product context

product family, model, catalogue revision, market and account

Parameter values

stable parameter IDs, typed values, units and accepted ranges

Rule evidence

rule-set revision, warnings, stops, review flags and override authority

Geometry request

template or model revision, coordinate convention and requested output purpose

Commercial context

price result ID, currency, price-list revision and approval status

Output identity

job ID, file ID, format, media type, checksum and storage reference

Generation result

queued, processing, review, failed, accepted or released

Traceability

requested by, generated at, software version, inputs and diagnostic record

Retention and change

expiry, supported reopen period, supersession and rollback behavior

Implement one traceable path from product rules to released output.

Stage 1

Classify the buying and engineering decisions

List every choice the customer, salesperson, product owner and engineer makes. Mark which decisions are safe for self-service, which require review and which only engineering can accept.

Stage 2

Choose the authoritative model for each decision

Assign catalogue identity, rules, pricing, browser visuals, CAD parameters, BOM and release status to named systems. Avoid one vague claim that CAD is the source of truth for everything.

Stage 3

Define stable identities and units

Map products, modules, parameters, materials and outputs with stable IDs. Normalize units, precision, origins and coordinate conventions before connecting interfaces.

Stage 4

Separate presentation geometry from engineering geometry

Decide which visible forms and movements belong in the web scene and which detailed features stay in CAD. Preserve traceable component identity without pushing manufacturing detail into the browser.

Stage 5

Write the output contract

Specify formats, templates, required parameters, job states, errors, review steps, service limits, retention and accepted downstream uses for every generated output.

Stage 6

Connect asynchronous generation safely

CAD and document jobs can outlive a browser request. Use idempotent job creation, authenticated callbacks or polling, timeouts, retry rules and permanent job identity.

Stage 7

Test representative and boundary configurations

Cover minimum, maximum, unusual but valid, invalid, legacy and revised products. Compare UI state, input payload, generated geometry, documents, BOM and reopening behavior.

Stage 8

Release with version and change governance

Bind the accepted catalogue, rule, visual asset, CAD template, output mapping and integration versions. Define who can publish changes and how earlier quotes or orders reopen.

Acceptance tests for a CAD-connected configurator.

A demo proves that one happy path can work. Acceptance proves that identities, boundary values, outputs, revisions and failures remain controlled.

Identity trace

One configuration ID resolves to the exact catalogue, rule, visual, price, CAD-template and output revisions used.

Known dimensions

Minimum, typical and maximum products reproduce approved dimensions and units in browser state and generated outputs.

Invalid state

Unsupported combinations cannot reach a CAD job through either the user interface or a direct API request.

Boundary geometry

Parameter limits, repeated modules, openings, clearances and optional components generate without feature or assembly failure.

Output import

Every promised exchange format opens in the named downstream application and preserves the accepted scope.

Price reconciliation

Any CAD-derived quantity used for price is recorded and reconciles with the accepted commercial result.

Job reliability

Duplicate requests, retries, timeouts and partial failures do not create ambiguous or conflicting released files.

Revision behavior

An earlier quote reopens against its recorded revision or enters a deliberate migration and review path.

Approval boundary

Illustrative, review-ready and production-released outputs are visibly and technically distinguishable.

Access control

Only authorized roles can request sensitive outputs, view engineering files, approve overrides or release production data.

Performance

Browser configuration stays responsive while generation runs asynchronously and communicates real job state.

Change regression

A CAD template, rule, product or mapping change reruns the affected scenario pack before publication.

Where Configurix fits

Keep the customer journey clear while engineering stays governed.

Configurix is white-label 3D product configurator and visual CPQ software. It connects guided configuration, live pricing, saved projects, quotes and structured handoff for manufacturers, product owners, dealers, retailers and installers. When CAD automation, drawings, BOMs or production data are required, those outputs are defined as product-specific integrations with named owners and acceptance criteria.

That boundary matters. Customers should see a fast, understandable product. Sales should receive an accurate commercial record. Engineering should receive controlled parameters—not a screenshot. Production should receive only accepted outputs—not an attractive but unverified scene.

Discuss your CAD and product workflow

The connected record

Validated customer or sales configuration

Stable product, option, parameter and revision IDs

Rules, price result, quote and approval context

CAD or document job identity and status

Accepted output references and downstream acknowledgement

Change history for reopening, revision and support

CAD product configurator FAQs.

Direct answers for product, sales, engineering, ecommerce and IT teams evaluating visual configuration and CAD automation.

A CAD product configurator is a rule-driven system that turns accepted product parameters into a valid design state and, when required, drives CAD models, drawings or exchange files. Some systems are engineering-first and automate native CAD. Others are sales-first web configurators that connect an accepted commercial configuration to a separate CAD automation service. The important questions are which system owns each rule, which outputs are generated, what approval they carry and how every result is traced to the exact configuration revision.

A web 3D product configurator prioritizes fast, understandable interaction for customers, dealers and sales teams. It uses optimized runtime geometry and shows the effect of valid options in a browser. A CAD configurator prioritizes engineering geometry, feature logic, drawings or manufacturing-oriented files in a specific CAD workflow. One implementation can connect both, but a photoreal browser scene is not automatically a native CAD model and a native CAD model is rarely the right payload for a public website.

Yes, when CAD automation is part of the agreed implementation scope. Configurix can provide the governed configuration identity, validated parameters, visual state, commercial context and workflow that a connected CAD or document service consumes. The exact authoring system, templates, formats, job orchestration, review states and acceptance tests must be defined for the customer's products. Configurix does not treat every browser configuration as production-ready CAD without that product-specific contract.

A configurator can request those outputs when the connected generation stack supports them and their downstream purpose is defined. Format names alone are not enough. Specify whether a file is a visual derivative, quotation drawing, fabrication input, neutral exchange model or production-released artifact; which units, assemblies and metadata it preserves; which application must import it; and who approves it. Support should be confirmed with representative products and boundary cases.

Usually no. Native CAD contains construction history, internal parts, exact curves, tolerances and application-specific structure that can be too heavy, sensitive or incompatible with real-time browser interaction. A controlled asset pipeline normally derives lightweight glTF or GLB visualization assets while retaining the authoritative CAD separately. Stable product and component IDs connect the representations without requiring them to be the same file.

It can, but only if the rule domains and execution contract are explicit. Commercial compatibility, pricing policy, geometric constraints and engineering calculations are not automatically the same kind of rule. A shared governed product model can provide accepted parameters while specialized services retain authority for price, CAD generation or engineering validation. Reconcile representative configurations so the browser cannot accept a state that CAD rejects.

CPQ governs the sellable configuration, commercial context, price, discount, approval and quote revision. After a configuration reaches the required state, CPQ or the configurator submits a versioned parameter payload to CAD automation. The CAD job returns status and output identities. The quote or order record stores those identities rather than attaching an untraceable file. Engineering review can remain a mandatory gate before delivery or production release.

Yes, when product and component mappings are explicitly modeled. The result might be a sales BOM, configured order BOM, engineering BOM or manufacturing BOM; these should not be conflated. Define the owner of part identity, quantities, variable dimensions, substitutions and effectivity. A CAD assembly can contribute structure or calculated values, while ERP, PLM or an approved mapping service may own the released production interpretation.

Use one configuration identity, stable parameter and component IDs, explicit units, compatible model revisions and automated trace tests. For representative states, compare the web scene, parameter payload, CAD result, dimensions, BOM and quote. Prevent a visual-only option from silently becoming a production choice, and prevent CAD template changes from publishing until saved configurations and boundary cases pass regression.

A parametric CAD product configurator drives dimensions, features, patterns, component selection or assembly relationships from controlled parameters. Parameters need types, units, bounds, dependencies and stable identity. The automation must handle minimum, maximum and unusual valid cases deterministically. Parametric does not mean unrestricted: the solution space should remain governed by product and engineering rules.

It can automate repeatable decisions that engineering has already modeled and approved. It should not silently replace project-specific structural, safety, compliance or specialist engineering judgment outside that accepted domain. Define when a state is automatically accepted, when it raises a warning and when it requires technical review. The interface and output status should make that boundary clear to customers and sales teams.

Classify native models, derived geometry, drawings, BOMs and customer files separately. Apply role and tenant authorization to both generation requests and downloads; use short-lived access where appropriate; protect service credentials; validate input size and type; log requests and approvals; and define retention. Public browser geometry should not expose manufacturing detail merely because the original source contained it.

Timing depends on product families, source-model readiness, parameter quality, rule complexity, output formats, templates, integrations and acceptance scope. A visual sales configurator using approved modules can be much faster than a native CAD automation program across several engineered product lines. Configurix uses a fast-launch path for focused configurators and a broader scoped implementation for custom white-label, multi-product and engineering-output workflows.

Ask which system owns catalogue, rules, price, browser 3D, CAD geometry, BOM and release status; which formats and authoring versions are actually supported; how units and IDs map; whether jobs are asynchronous and idempotent; how boundary configurations are tested; what happens to old quotes after a template change; who owns source files and automation scripts; how outputs are secured; and which evidence proves a file is approved for its stated purpose.

Primary technical sources.

These references support the technical distinctions in this guide. Product capability, file support and acceptance remain implementation-specific.

Autodesk Platform Services — Design Automation API

Official overview of running supported Autodesk engines and automation activities in cloud workflows.

Open source

Siemens Solid Edge Design Configurator

Official product overview for rule-based automation of models, BOMs and technical documentation in Solid Edge.

Open source

Khronos glTF 2.0 specification

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

Open source

OpenAPI Specification

The official specification for describing HTTP APIs and their operations, parameters, responses and security schemes.

Open source

JSON Schema specification

The official specification index for describing and validating structured JSON instance data.

Open source

Connect visual selling to engineering automation.

Three valid meanings of “CAD product configurator.”

Web configurator with governed product data

Connected visual CPQ and CAD automation

Engineering-led configuration with a sales surface

Match the architecture to the product and output.

Web configurator with governed product data

Give every decision one authoritative owner.

Name the output—and the authority it carries.

Commercial specification

Configured order payload

2D plan or technical drawing

Neutral 3D exchange file

Native CAD automation result

Production-released package

Use a versioned CAD-output contract.

Implement one traceable path from product rules to released output.

Classify the buying and engineering decisions

Choose the authoritative model for each decision

Define stable identities and units

Separate presentation geometry from engineering geometry

Write the output contract

Connect asynchronous generation safely

Test representative and boundary configurations

Release with version and change governance

Acceptance tests for a CAD-connected configurator.

Identity trace

Known dimensions

Invalid state

Boundary geometry

Output import

Price reconciliation

Job reliability

Revision behavior

Approval boundary

Access control

Performance

Change regression

Keep the customer journey clear while engineering stays governed.

CAD product configurator FAQs.

What is a CAD product configurator?

What is the difference between a 3D product configurator and a CAD configurator?

Can Configurix connect to CAD automation?

Can a customer generate STEP, DXF, DWG, PDF or STL files from a configurator?

Should native CAD files be loaded directly in the browser?

Can one rule engine drive both web 3D and CAD?

How does CAD automation work with CPQ software?

Can a CAD product configurator generate a bill of materials?

Can CAD-derived dimensions update live pricing?

How do you prevent browser 3D and CAD from showing different products?

What is a parametric CAD product configurator?

Does a CAD configurator replace an engineer?

How are CAD generation jobs handled when they take longer than a web request?

How should CAD outputs be secured?

How long does a CAD product configurator take to implement?

What should buyers ask a CAD product configurator vendor?

Primary technical sources.

Autodesk Platform Services — Design Automation API

Siemens Solid Edge Design Configurator

Khronos glTF 2.0 specification

OpenAPI Specification

JSON Schema specification

Continue the implementation path.

3D asset pipeline

Parametric product configurator

BOM generation

PLM integration

BIM product configurator

Integration architecture

Testing and QA