Is product configuration management the same as software configuration management?

No. Product configuration management in this guide concerns the options, rules and versions of a configurable product that a company designs, sells and delivers. Software configuration management concerns source code, application builds and technology environments. They share disciplines such as baselines, version control, approval and audit, but they govern different configuration items.

What is product configurator maintenance?

Product configurator maintenance is the governed work required to keep a live configurator accurate as products, dimensions, compatibility rules, 3D assets, materials, prices, markets, languages, documents, integrations and browsers change. It includes ownership, change assessment, implementation, review, regression testing, publishing, monitoring and support—not only fixing software defects.

Who should own a product configurator after launch?

Business ownership should remain with a named product or catalogue owner who can approve what the configurator may sell. Technical, 3D, pricing, content, integration, security and operational owners support their domains. The vendor or internal engineering team may implement changes, but accountability for product truth and commercial policy should not be ambiguous.

Can our team update products and prices without a developer?

Many controlled changes can be administrator-managed when the platform provides stable IDs, permissions, validation, preview, environments and an approval workflow. New parametric geometry, complex dependencies, production outputs or integration contracts often require specialist implementation and renewed acceptance. The maintenance model should classify each change type before launch.

How should price changes affect saved configurations?

Define whether a saved configuration stores a price snapshot, price reference, expiry or a recalculation rule. An accepted quote should retain its historical commercial evidence. A reopened draft may be repriced under an explicit policy, with the user told what changed. Test account, market, currency, tax, rounding and approval behavior before publishing.

What happens to saved projects when a product option is retired?

The system should resolve the historical option by stable identity and apply an agreed compatibility policy. The project may remain viewable, require review, offer an approved substitution, migrate to a new version or become read-only. It should not silently select a different component or lose the original quote and configuration evidence.

How often should a product configurator be regression tested?

Run targeted regression for every change and the relevant permanent core pack before release. The frequency depends on release volume and risk, not a universal calendar. Rule, price, geometry, integration, browser or platform changes can require broader coverage. Periodic full regression is useful, but it does not replace change-triggered testing.

What should be included in a configurator regression test pack?

Include a common valid configuration, minimum and maximum boundaries, invalid and dependent combinations, known price cases, saved and resumed projects, quote or cart completion, user-role differences, target devices, document output, integration success and failure, and compatibility with a previous catalogue version. Each case needs controlled inputs, expected results and retained evidence.

How are new colours and materials added to a 3D configurator?

Add a stable material ID, approved name and swatch, visual material under accepted lighting, product compatibility, market availability, price behavior, document label and any downstream component mapping. Review colour and material appearance on target devices while recognizing that displays and lighting cannot guarantee an exact physical match.

How should product rules be versioned?

Record the effective rule version associated with each saved configuration and output. A new rule should be tested against normal, boundary, invalid and historical cases. Decide whether older projects remain valid, need review or migrate. Avoid overwriting rule meaning without retaining enough context to explain an earlier quote or order.

What environments does configurator maintenance need?

At minimum, teams need a safe place to prepare and review changes before production. Broader implementations may separate development, acceptance and production environments. Each environment should have controlled data, access, publishing responsibility and a clear path for promoting the accepted version without manual reconstruction.

How should integration changes be maintained?

Version the field and event contract, test representative and rejected payloads, protect against duplicates and retries, document authentication and deprecation, and verify monitoring and reconciliation. A CRM, ERP, ecommerce or production-system change is not complete until both sides accept the same identifiers, semantics and failure behavior.

What maintenance questions should buyers ask configurator vendors?

Ask who can add products, change rules, update prices, publish translations and revise documents; which changes require vendor work; how stable IDs and saved projects survive updates; what environments, permissions, regression tools, monitoring and support are included; how changes are priced; and whether the vendor can demonstrate a real post-launch catalogue change.

Product configuration management

Your products evolve. Your configurator keeps up.

Keep catalogue options, 3D materials, rules and prices aligned as your products change. Configurix builds custom configurators and factory software around your approval process and connected systems.

Plan your configurator

Change review workspace

Change type

Label, content or translation change

1Scope
2Prepare
3Review
4Publish

Affected areas

Customer labelsHelp contentDocumentsSearch and accessibility text

One change. Every affected layer.

Product configuration management controls the definitions, options, rules and versions behind a configurable product. For manufacturers, it connects the approved catalogue to the website, sales configuration, quote and agreed factory outputs. Ownership, review and historical compatibility matter as much as the editor screen.

Product definition

Families, modules, dimensions, options, accessories, materials and the stable identifiers that keep each sellable choice recognizable across systems and revisions.

Configuration logic

Compatibility, dependency, quantity, formula, validation and engineering-review rules that determine which combinations are valid for a market and date.

Commercial context

Prices, discounts, currencies, taxes, dealer or account conditions, quote validity and the effective commercial version used for a saved project.

Visual and operational output

3D geometry, materials, documents, BOM or order mappings, integration payloads and the evidence that connects a customer selection to delivery.

What are you changing?

Choose a change to see the owners, affected areas and review evidence to agree before publication. Use the planner to prepare a focused conversation about your catalogue.

Change type

Label, content or translation change

Change visible wording without changing the stable product identifiers or allowed configuration state.

People to involve

Product owner
Market or language reviewer
Publisher

Affected areas

Customer labels
Help content
Documents
Search and accessibility text

Evidence to review

Stable IDs remain unchanged
Text fits desktop and mobile layouts
Fallback and all target languages reviewed
Quote or document wording checked where reused

Release review: Content review and targeted journey check

Your product or catalogue change

Decisions and questions

Your planner stays in this browser tab. Download the review requirements or start again. It does not publish catalogue changes or add notes to the enquiry form.

A controlled route to release.

A new finish and a new geometry module need different work. Both need an accountable owner, review evidence and a deliberate route from preparation to production.

1
Describe the change
Name the business reason, requested effective date, affected products, markets, users, saved projects, outputs and accountable approver.
2
Assess cross-layer impact
Trace catalogue, rules, 3D, pricing, content, documents, integrations, analytics and historical-project behavior before implementation begins.
3
Implement away from production
Use controlled data and assets in a working environment where reviewers can reproduce the requested change without affecting live customers.
4
Run targeted and core regression
Test the changed behavior plus the permanent representative pack that protects normal, boundary, invalid, price, quote and handoff scenarios.
5
Approve and publish deliberately
Record the reviewed version, approvers, release window, migration decision, monitoring plan and rollback or correction path.
6
Observe and reconcile
Confirm the published catalogue, customer journey, documents and downstream records match the accepted release before closing the change.

Keep existing projects explainable.

Today's catalogue must not silently rewrite an accepted quote. Define how stable identifiers, effective versions, substitutions and historical prices behave before your first update.

Stable identity

A renamed option should remain the same option. Keep labels separate from stable product, option, component and configuration identifiers.

Effective versions

Record which catalogue, rules, price and document versions produced a saved configuration, quote or order—and when each became effective.

Explicit compatibility

When reopening an old project, decide whether it remains valid, needs review, can be migrated, contains retired choices or must stay read-only.

Historical commercial evidence

Do not silently replace an accepted quote with today's price. Preserve the accepted result and define when a new revision triggers repricing.

Protect the complete product journey.

Test the changed behaviour and a permanent set of representative cases. Open each group to see what your release review should cover.

Core customer journey

Start from the intended entry point
Complete a common valid product
Save, resume and revise
Submit the intended lead, quote or cart action

Product-rule boundaries

Minimum and maximum dimensions
One value just outside each boundary
Required and excluded combinations
Warning, hard stop and technical-review paths

Commercial result

Known standard price
Accessory quantity and formula case
Account, market, tax and currency context
Quote revision, validity and approved historical price

Experience and rendering

Desktop, tablet and target mobile viewport
Accepted cameras and material states
Loading, fallback and validation feedback
Keyboard, focus, labels and core accessible completion

Connected systems

CRM or cart record creation
Quote and document generation
Order, BOM or production payload when scoped
Timeout, duplicate, rejection and recovery

Historical compatibility

Open a saved project from the previous version
Display retired or substituted options clearly
Reprice only under the agreed rule
Preserve accepted quote and order evidence

Who owns each decision?

Define the source of truth and approver for each data domain. Configurix can govern the sales configuration layer while connecting to the engineering, catalogue and operational systems you already use.

Product families, options and stable IDs

Authoritative source: Governed catalogue or PIM/configuration source
Accountable owner: Catalogue owner
Review before release: Create, revise, retire and market assignment

Compatibility and dimension rules

Authoritative source: Configuration rule model
Accountable owner: Product engineering owner
Review before release: Boundary, dependency and invalid-state acceptance

Geometry, materials and cameras

Authoritative source: 3D asset and parametric-model repository
Accountable owner: 3D or visual owner
Review before release: Visual review, performance budget and supported-device regression

Prices, formulas, tax and discounts

Authoritative source: Pricing service, ERP, CPQ or governed price source
Accountable owner: Commercial owner
Review before release: Known-case reconciliation, effective date and permission review

Customer and opportunity status

Authoritative source: CRM
Accountable owner: Sales operations
Review before release: Field ownership, lifecycle mapping and duplicate behavior

Order, component or production status

Authoritative source: ERP, order or production system
Accountable owner: Operations owner
Review before release: Accepted revision, identifiers, quantities and reconciliation

Labels, translations and help content

Authoritative source: Content or translation workflow
Accountable owner: Market/content owner
Review before release: Terminology, layout, fallback, documents and accessibility review

Match the change to the right team.

Administrator-managed

Controlled labels, translations, help content, approved availability, selected prices and prepared catalogue values where validation is built into the publishing workflow.

Fast routine changes with stable IDs, review permissions and preview evidence.

Specialist-assisted

New materials, prepared components, quote templates, regional price structures, controlled rule changes and supported system mappings.

A specialist prepares or checks the cross-layer effect before the customer's approver publishes.

Scoped implementation

New parametric geometry, complex rules, additional user journeys, production outputs, major integration contracts and structural catalogue migrations.

A planned release with design, implementation, full acceptance and operational handover.

Where configuration management fits.

Product configuration management, CLM, PLM, PIM and CPQ have different responsibilities. Agree the boundaries rather than giving two systems conflicting ownership of the same data.

Product configuration management

Controls the structure, rules, versions, effectivity and approved change of configurable product information.

A traceable product model that remains valid as the offer evolves.

Configuration lifecycle management (CLM)

Coordinates configuration definitions and logic across engineering, sales, manufacturing and service systems.

Cross-functional alignment and a governed configuration thread.

PLM and engineering change management

Own engineering definitions, revisions, documents, approvals and product change processes.

Released engineering truth and its lifecycle history.

PIM and catalogue management

Own market-facing product content, attributes, media, taxonomy and channel publication.

Consistent product information for each market and channel.

CPQ and sales configurator

Guide a buyer or salesperson to a valid selection, calculate a commercial result and create a quote or order-ready record.

A valid, priced and explainable customer configuration.

Software or infrastructure configuration management

Controls application, environment, device and infrastructure settings rather than the choices inside a sellable physical product.

Reliable technology environments and deployments.

Custom software for manufacturers

A configurator up front. Your business connected behind it.

We specialize in complex, configurable and made-to-order products. We build custom software around your catalogue, calculations, permissions, sales process and factory workflows.

Keep the business connected as products change.

We specialise in complex products. We build custom configurators and business or factory software around your catalogue, product rules, prices, approvals and connected systems. Agree how each catalogue change reaches your website, CRM, appointments, quotes, materials, orders, jobs and invoicing.

CRM and qualified leads

Capture the selected product, dimensions and options with each enquiry. Qualify by product fit, project requirements and commercial readiness, then assign the next action to the right salesperson.

Configurix workspaceQuote revision

New enquiry

Product configuration management

Product fit

Qualified

Product configuration management

Requirements

Proposal

Product configuration management

Next action

Calendars and appointments

Let a configured project continue into a sales consultation, technical review, survey or installation appointment. Connect calendars, responsibilities and reminders to the same customer record.

Configurix workspaceQuote revision

09:00Project review
11:30Technical review
14:00Production planning

Bill of materials and factory data

Map product selections to component codes, quantities, materials and cut lengths. Build the sales or manufacturing BOM your team needs, with revisions and production review rules defined for your products.

Configurix workspaceQuote revision

Bill of materials and factory data
Component	Quantity
FRM-01Configured components	1
PNL-02Materials and quantities	1
KIT-03Agreed operations	1

Mapped to your product codes

Live prices and branded quotes

Apply your own formulas, price lists, dealer margins and approval rules. Generate a quote containing the saved specification, product images, commercial terms and a clear customer approval step.

Configurix workspaceQuote revision

Quote revision

Your catalogue

Options

Services

Your price rulesBranded PDF

Orders, jobs and production

Carry accepted choices into order lines and assigned jobs. Keep product revisions, required approvals, documents and delivery tasks together so sales and the factory work from the same specification.

Configurix workspaceQuote revision

Accepted quote01
Configured order02
Production job03
Installation04

Invoicing and accounting

Connect accepted orders to deposits, invoice drafts, payment terms and your accounting workflow. Agree which system issues the invoice and how references and confirmed payment status return to the project.

Configurix workspaceQuote revision

Draft invoice

Product configuration management

Order referenceProduct configuration management

Customer—

Payment terms—

Accounting handoff

Built for your website. Connected to your systems.

Launch a branded configurator in your existing website or a custom sales portal. Connect CRM, ERP, PIM, ecommerce, calendars and accounting through available APIs, webhooks or agreed imports. We define the data, permissions and responsibilities for each connection with your team.

01Your website
02Configurator
03CRM & calendar
04ERP & accounting

Choose the workflows your implementation needs. We build and validate them against your products, documents and target systems.

Plan your configurator

References for a governed product lifecycle.

ISO

ISO 10007:2017 — Guidelines for configuration management

The standard applies configuration-management guidance to products and services from concept through disposal and establishes the wider lifecycle context for controlled product information.

Read the source

Microsoft Learn

Approve a product configuration model

Dynamics 365 documents product-model versions with availability dates, expiry, named approval and activation—useful evidence for version and effectivity design.

Read the source

SAP Help Portal

Advanced Variant Configuration

SAP describes integrated configurable-product modeling across sales, planning, production and engineering, including model simulation and configurable BOM testing.

Read the source

Oracle Help Center

Control explosion dates for configuration models

Oracle shows why configuration effectivity matters when a model changes after an order line was created and historical or current model state must be selected deliberately.

Read the source

Configit

Configuration Lifecycle Management

Configit defines CLM as an approach for aligning configurable product options and rules across design, manufacturing, sales and service rather than as one universal replacement system.

Read the source

Product configuration management questions.

Product configuration management software controls the information that defines configurable products: families, modules, options, dimensions, compatibility rules, versions, effective dates, prices, visual assets and downstream mappings. It gives named owners a controlled way to propose, test, approve, publish and trace changes so websites, sales tools, quotes and operational outputs use an accepted product definition.

Configuration lifecycle management, often shortened to CLM, is an approach for keeping configurable product definitions and rules aligned across engineering, sales, manufacturing and service over time. It emphasizes shared configuration truth, cross-system validation, version context and traceability. A company may implement that approach through several connected systems rather than one application owning every data domain.

PLM commonly governs engineering product definitions, documents, revisions and engineering change. Configuration lifecycle management concentrates on aligning configurable options and rules across PLM, ERP, CPQ, sales and service contexts. Configurix should connect to the accepted engineering and master-data authorities; it should not silently replace them or duplicate ownership without a defined reason.

Configurix can govern the customer-facing and sales configuration layer: selectable products and options, rule behavior, 3D states, commercial context, saved configurations, quotes and connected project data. The exact authority split with PLM, PIM, ERP, CRM or production systems is defined during implementation. Complex enterprise CLM scope should be proven against working integrations, version behavior and signed acceptance criteria.

Effective dates identify when a product model, component, rule or price becomes valid and when it expires. They prevent a new catalogue state from silently rewriting an earlier order or accepted quote. The system still needs an explicit policy for drafts, revisions, substitutions and historical records because current-date, order-date and original-creation-date behavior can produce different valid results.

Plan the first product and the changes that follow.

We specialise in complex products and build custom configurators and software for manufacturers. Bring your catalogue, pricing rules and one real change you need to make. We will discuss the ownership, sales workflow, factory outputs and integrations around it.

Your products evolve. Your configurator keeps up.

Label, content or translation change

One change. Every affected layer.

Product definition

Configuration logic

Commercial context

Visual and operational output

What are you changing?

Label, content or translation change

People to involve

Affected areas

Evidence to review

Price-list or formula update

People to involve

Affected areas

Evidence to review

Market or channel availability change

People to involve

Affected areas

Evidence to review

New finish or material

People to involve

Affected areas

Evidence to review

Dimension or compatibility rule change

People to involve

Affected areas

Evidence to review

New accessory or component

People to involve

Affected areas

Evidence to review

New module or parametric geometry

People to involve

Affected areas

Evidence to review

Integration contract change

People to involve

Affected areas

Evidence to review

A controlled route to release.

Describe the change

Assess cross-layer impact

Implement away from production

Run targeted and core regression

Approve and publish deliberately

Observe and reconcile

Keep existing projects explainable.

Protect the complete product journey.

Who owns each decision?

Match the change to the right team.

Where configuration management fits.

CRM and qualified leads

Calendars and appointments

Bill of materials and factory data

Live prices and branded quotes

Orders, jobs and production

Invoicing and accounting

Built for your website. Connected to your systems.

References for a governed product lifecycle.

ISO 10007:2017 — Guidelines for configuration management

Approve a product configuration model

Advanced Variant Configuration

Control explosion dates for configuration models

Configuration Lifecycle Management

Product configuration management questions.

What is product configuration management software?

What is configuration lifecycle management?

Is product configuration management the same as software configuration management?

How is configuration lifecycle management different from PLM?

Can Configurix act as a product configuration management layer?

Why do configurable products need effective dates?

What is product configurator maintenance?

Who should own a product configurator after launch?

Can our team update products and prices without a developer?

How should price changes affect saved configurations?

What happens to saved projects when a product option is retired?

How often should a product configurator be regression tested?

What should be included in a configurator regression test pack?

How are new colours and materials added to a 3D configurator?