3D product configurator for manufacturers
Turn product knowledge into one connected selling workflow.
Configurix connects governed product choices, interactive 3D, commercial context and a persistent configuration so customers, dealers and sales teams can create the right product and continue it into a quote, order or scoped operational handoff.
One accepted state
The 3D model is one layer. The manufacturer value comes from agreement between product, commercial and operational meaning.
The manufacturer definition
More than a viewer. Less ambiguous than a spreadsheet.
A manufacturing product configurator creates a permitted, identifiable product state. It can show that state in 3D and connect it to price, proposal, order or production data. The important distinction is not the interface label; it is which authority, revision and evidence sit behind every output.
3D viewer
Presents a prepared model. It may not govern choices or save a structured product.
Visual configurator
Creates governed choices and keeps the visible result connected to selected state.
Visual CPQ
Adds commercial rules, account context, approvals, proposals and revisions.
CAD automation
Creates engineering geometry or files under a separate technical authority and release process.
Interactive manufacturer scope builder
Map the product journey before comparing features.
Select one representative route. The result identifies the controls and evidence a working implementation needs; it is not a quote, feasibility decision or production approval.
Connected operating model
Eight layers keep sales speed connected to product truth.
Not every system owns every layer. Define the source and owner before integration so the same field does not acquire competing meanings in the website, quote, ERP and factory.
Product identity
Stable families, models, options, finishes, components, markets and lifecycle status.
Authority: PIM, PLM, ERP or governed catalogue
Configuration rules
Dependencies, exclusions, required choices, ranges, increments and derived values.
Authority: Approved commercial product model
Interactive 3D
Runtime geometry, materials, cameras and animations bound to the same selected state.
Authority: Configurator runtime and asset pipeline
Commercial context
Market, account, quantity, services, tax, discounts, approvals and price revision.
Authority: Pricing authority agreed per calculation
Channel experience
Customer, dealer and internal-sales journeys with role-specific guidance and permissions.
Authority: Configurix white-label experience
Persistent project
Configuration ID, revision, customer context, status, documents and historical meaning.
Authority: Configurix, CRM or connected project system
Operational mapping
Configured order, BOM, routing, CAD, drawings, cut lists or review tasks when implemented.
Authority: ERP, PLM, CAD, MES or scoped integration
Change and evidence
Versioned publishing, regression fixtures, approvals, monitoring and rollback decisions.
Authority: Named product, commercial and technical owners
Digital thread for commercial configuration
From published product to accepted handoff.
NIST describes a digital thread as connected, traceable information across lifecycle stages. A sales configurator contributes one part of that thread when its identity, revisions and downstream contracts are explicit.
Publish a governed product
Start from approved product identities, decision logic, dimensions, finishes, accessories and market availability—not from a visually plausible model alone.
Acceptance evidence: Representative normal, boundary and invalid cases have expected structured states.
Guide the right user
Expose the catalogue, price, margin, language, units, permissions and next actions appropriate to a customer, dealer or internal salesperson.
Acceptance evidence: Role and account tests prove restricted values and actions are enforced on the server.
Configure one canonical state
Every control changes a stable configuration record. The 3D scene, selected-options summary and downstream payload all read the same accepted state.
Acceptance evidence: A known selection produces matching visual, readable and machine-readable results.
Calculate commercial status
Resolve price, discount, tax, freight, installation, lead-time or review status from named sources and show whether the result is live, estimated or subject to approval.
Acceptance evidence: Known-price ledgers reconcile across market, account, quantity and exception cases.
Save and approve a revision
Preserve the exact configuration, price context, product revision and customer action that produced a quote, cart line or internal approval request.
Acceptance evidence: Reopening and editing create intentional revisions without silently rewriting history.
Hand off a configured order
Send stable product and option IDs, values, quantities, customer context and source revisions into CRM, ecommerce, ERP or another accepted destination.
Acceptance evidence: Idempotent retries, validation failures and destination outages have tested recovery behavior.
Generate optional operational output
Map the accepted commercial state to a BOM, CAD request, drawing, cut list or production pack only where the source rules and responsible release process are implemented.
Acceptance evidence: Expected components, files, quantities, tolerances, exceptions and approvals are accepted by operations.
Govern catalogue change
Assess the effect of a new price, option, asset, rule or component on active projects, historical quotes, dealer catalogues and production mappings before publishing.
Acceptance evidence: A permanent regression pack and rollback decision accompany each risk-relevant release.
System authority matrix
Connect systems without duplicating authority.
System names vary. The durable decision is which source owns each identity and calculation, which consumers may enrich it and which approval releases it for the next stage.
PIM or governed catalogue
Commercial product identity, descriptions, media, classifications and market availability where implemented.
Geometric validity, price calculation or production readiness by itself.
PLM and CAD
Engineering definitions, source geometry, technical revisions and released design output.
A usable buyer journey, account price or accepted commercial quote by itself.
Configurix
Scoped channel experience, guided product state, 3D bindings, project continuity and connected workflow.
Engineering approval or factory release unless those authorities are explicitly integrated.
Pricing or ERP
Approved price lists, costs, taxes, inventory, configured-order IDs or BOM master data according to scope.
That the 3D scene or customer-facing explanation matches the calculation.
CRM and CPQ
Account, opportunity, approval, activity and proposal records according to the operating model.
That every stored option remains buildable after catalogue change.
MES or production process
Released work, routing, execution status and shop-floor instructions where connected.
That an earlier sales configuration is automatically production-authoritative.
Configured-order contract
Carry identity, not a screenshot.
A visual snapshot helps people review the product. The machine-readable handoff needs stable identities, values, source revisions and commercial context so another system can validate, reconcile and retry it.
Example contract shape
{
"configurationId": "cfg_4821",
"revision": 3,
"product": { "id": "family_model" },
"selections": [
{ "optionId": "finish_a", "value": "anthracite" }
],
"dimensions": [
{ "id": "width", "value": 4200, "unit": "mm" }
],
"commercialContext": {
"market": "EU", "priceRevision": "2026-08"
},
"status": "quote_ready"
}Illustrative logical shape only. Field names, security, required values and destination contracts are defined for the working implementation.
Working acceptance pack
Twelve tests a manufacturer demo should survive.
Use one representative product and expected outputs. Ask every vendor or internal team to run the same normal, boundary, failure and historical-change cases in the working system.
A representative base product opens with the expected catalogue, market, language and role context.
Normal, boundary, missing and incompatible choices produce the approved allowed state or a specific recovery path.
A selected option changes the correct structured value, 3D component, readable summary and downstream identity.
Known dimensions drive the expected geometry and derived quantities without unsupported rounding or unit conversion.
Known price cases reconcile for public, dealer, account, quantity, discount, tax, freight and approval contexts in scope.
A user can review, save, reopen, revise, share and complete the configuration on agreed mobile and desktop devices.
The same configuration revision reaches the quote, CRM, cart or order payload without retyping or ambiguous free text.
Duplicate submission and retry do not create conflicting customer, quote, order or production records.
A changed or retired option produces the approved behavior for an active project and a historical quote.
BOM, CAD or production output matches the accepted fixtures and enters the named review or release process.
Unauthorized users cannot access another account's catalogue, prices, margins, projects, documents or APIs.
A product, rule, price, asset or integration change runs the relevant permanent regression scope before publishing.
Manufacturer implementation roadmap
Build a controlled product system in eight phases.
The phases can overlap, but none disappears. A fast first product still needs agreed sources, rules, prices, acceptance and change ownership; it simply limits the number of product families, roles, documents and integrations introduced at once.
Focused launch versus platform rollout
A focused Configurix Fast Launch can usually target one ready product in seven days. A broader multi-product white-label system with dealer roles, languages, integrations and production outputs can take up to 30 days depending on source readiness, review and scope.
Define the business route
Inputs: One representative product, primary user, current process, target completion and baseline measures.
Accepted result: A bounded journey from entry to lead, quote, cart, configured order or technical-review request.
Assign data authority
Inputs: Current catalogue, price books, CAD sources, component data, documents, systems and named owners.
Accepted result: A field-level source-of-truth matrix that separates product, visual, commercial and operational meaning.
Model rules and dimensions
Inputs: Decision tables, dependencies, exclusions, ranges, increments, formulas and known boundary examples.
Accepted result: A canonical configuration model with expected valid, invalid, incomplete and review-required states.
Prepare runtime 3D
Inputs: Approved source models, materials, variants, naming, pivots, parametric behavior and target devices.
Accepted result: Optimized runtime assets whose nodes and materials bind predictably to product and option identities.
Build commercial context
Inputs: Price ownership, account logic, markets, quantities, discounts, approvals, tax, freight and services.
Accepted result: Known-price calculations with visible status and preserved price provenance for each accepted revision.
Connect roles and systems
Inputs: Customer, dealer and team permissions plus CRM, ecommerce, ERP, PIM, CAD or document contracts.
Accepted result: Authorized channel journeys and observable handoffs with validation, retries, reconciliation and ownership.
Accept the whole journey
Inputs: Representative fixtures, devices, accounts, historical states, failures and expected downstream results.
Accepted result: Signed evidence for product logic, 3D, pricing, UX, accessibility, security, performance and outputs in scope.
Operate catalogue change
Inputs: Publishing roles, change classes, regression scope, monitoring, support, rollback and review cadence.
Accepted result: A maintained product platform rather than a launch-day configuration demo that gradually becomes unreliable.
Common failure patterns
Problems a polished manufacturer demo can hide.
These failures usually cross team boundaries. Product, sales, ecommerce, IT, engineering and operations should review the representative journey together before approving architecture or vendor claims.
A shadow catalogue grows inside the configurator
Options are copied from spreadsheets or presentations without a named owner, stable identity or controlled update path. The website, dealers and ERP then disagree after the first range change.
Control: Assign authority per field, preserve source IDs and define who reviews and publishes each change class.
The 3D scene becomes the only product truth
A combination looks plausible on screen, but no structured rule proves it can be sold, priced or produced. Screenshots conceal missing dimensions, components and revision context.
Control: Bind every visible state to a canonical configuration and test visual, textual and downstream agreement.
Dealer security is implemented as hidden buttons
The interface hides margin or another account's project, while the underlying API still returns restricted data when called directly or with a changed identifier.
Control: Enforce tenant, account, role and object authorization on the server and test cross-account access explicitly.
Price is live but its meaning is unclear
The total updates quickly, yet users cannot tell whether tax, freight, installation, account discount or engineering review is included—or which revision produced the result.
Control: Show commercial status and provenance, then reconcile known cases against the named pricing authority.
A sales BOM is treated as released production data
Component lines are generated from commercial choices without validating substitutions, units, scrap, tolerances, routing, engineering exceptions or effective revisions.
Control: Name the output precisely and route it through the accepted operational validation and release process.
Historical projects silently adopt new meaning
A retired option, changed formula or replaced component alters an old quote when it is reopened, even though the customer and factory understood the earlier revision differently.
Control: Store source revisions and define retain, migrate, review and non-orderable policies before catalogue change.
Integration succeeds only on the happy path
A demo sends one order, but duplicate clicks, destination timeouts, partial validation, retry, cancellation and reconciliation have no designed behavior or accountable owner.
Control: Specify idempotency, correlation, status, error details, retry limits, reconciliation and operational alerts.
Success is inferred from activity
More rotations, option clicks or time in 3D are reported as business impact without connecting versioned sessions to qualified leads, quotes, orders, margin or correction cost.
Control: Define funnel denominators and baseline measures, reconcile downstream outcomes and separate contribution from causation.
Manufacturer product examples
One method, different product logic.
Each family needs its own decisions, constraints, pricing, visual behavior and output contract. Explore the product-specific guides for practical inputs and edge cases.
Primary technical references
Standards before unsupported promises.
NIST · Digital Thread for Smart Manufacturing
Lifecycle information, traceability, standards and connected design-to-production context.
Open primary sourceNIST · UUIDs in manufacturing lifecycle data
Persistent identifiers for finding and tracing information across systems and lifecycle stages.
Open primary sourceKhronos · glTF
Open royalty-free specification for efficient transmission and loading of runtime 3D scenes and models.
Open primary sourceOpenAPI Specification
Language-agnostic interface description for HTTP APIs and connected system contracts.
Open primary sourceJSON Schema
Declarative validation and annotation language for JSON documents and structured payloads.
Open primary sourceW3C · Web Content Accessibility Guidelines 2.2
Testable web accessibility criteria for customer, dealer and internal configuration journeys.
Open primary sourceManufacturer configurator FAQ
Detailed answers for product, sales, IT and operations teams.
Bring one representative product
Test the product, price and handoff—not a generic demo.
We can map your catalogue, user roles, pricing authority, outputs and acceptance cases into a focused Configurix implementation plan.