Should a website configuration create a lead immediately?

Usually not during anonymous exploration. Define a meaningful trigger such as identified save, consultation request, quote request, sample request, appointment or checkout. The trigger should reflect explicit customer intent and the team's follow-up capacity. Behavioral analytics can measure anonymous configuration activity without filling CRM with records that sales cannot action.

Should Configurix create a lead, contact or opportunity?

That depends on the CRM's accepted data model and qualification process. A lightweight lead can suit early enquiries. Known customers may map directly to a contact and company. A quote-ready configured project may create or enrich an opportunity or deal. The contract should state the trigger, required fields, associations, ownership, duplicate policy and what happens when qualification fails.

How can sales reopen the customer's exact 3D configuration?

The CRM record should store a secure, resumable reference to the Configurix project and exact revision. Access must validate tenant, user role, account or dealer scope and project permissions. If sales edits the design, Configurix should create a new traceable revision while preserving the customer's submitted state, source and prior quote relationship.

How should anonymous configurator activity be connected after identification?

Use a privacy-aware journey or project identifier before identification. When the buyer provides their details for an agreed purpose, associate the relevant saved project and permitted prior events with the resolved CRM person or company. Do not assume that identifying a person creates consent for unrelated marketing, and do not expose the anonymous browser identifier as a public CRM key.

Can a CRM launch Configurix from an opportunity?

Yes, when scoped. A CRM action can open Configurix with a short-lived signed context containing the tenant, opportunity, account, user and intended action. Configurix validates the context, opens the existing project or creates the allowed new one, and returns accepted project, quote and activity references. Test revoked users, reassigned owners, expired links and cross-account access.

Should CRM integration use APIs or webhooks?

Most dependable implementations use several patterns. APIs support lookups and explicit create or update operations. Asynchronous jobs protect customer responsiveness. Webhooks notify Configurix about selected CRM changes. Scheduled reconciliation finds missed events and drift. Choose each pattern by urgency, authority and failure impact instead of calling one method the complete integration.

How should lead routing work for dealers and territories?

Routing can use country, postcode, product family, account relationship, dealer coverage, language, value, capacity or another agreed rule. Record the input values, routing revision, selected owner and reason. Define reassignment, unavailable dealers, overlapping territories and existing-account precedence. The website confirmation should not promise an owner until the routing result is accepted.

How do we protect customer data in a configurator CRM integration?

Minimize transferred fields, use least-privilege credentials, isolate tenants and environments, encrypt transport, protect secrets, verify webhook signatures, restrict resumable links, redact logs and document retention, export and deletion. Separate customer identity from marketing consent and test privacy requests across Configurix, CRM, analytics and connected marketing systems.

What information is needed to scope CRM integration?

Provide the CRM product, edition and environment; API and authentication documentation; standard and custom objects; required fields and associations; external identifiers; lead and opportunity stages; routing and ownership rules; consent and retention policy; quote and activity behavior; expected volumes; service limits; error ownership; representative records and acceptance fixtures.

Can Configurix build custom business and factory software with the configurator?

Yes. We specialize in complex products and can build the configurator together with the agreed CRM, qualification, calendar, quotation, bill-of-materials, order, job and invoice workflows. We define which functions belong in Configurix and which remain in your existing systems. APIs, identity, permissions, product revisions and acceptance checks are scoped for your implementation.

Custom configurators and connected business software

Product configurator CRM integration. Every enquiry with its product.

We specialize in complex products. Configurix builds custom configurators and business software that keep the customer's choices, saved design and quote request connected to the CRM workflow your sales team uses.

Plan your integration

Configured customer project

Product choices

Qualified enquiry

CRM follow-up

Define which customer and pipeline data the CRM owns and which product revisions Configurix owns. Each API, calendar and two-way update is scoped and tested for your systems.

A product journey your team can continue.

Capture intent with the design

Send the selected product, dimensions, options and saved revision when the customer asks to continue. Define qualification and ownership so sales receives a project it can understand.

Continue the same conversation

Let the responsible salesperson reopen the permitted configuration, arrange a consultation and prepare a revised quote. Keep the submitted design and later changes traceable.

Connect your actual CRM

Agree the objects, record associations, external keys and events for your Salesforce, HubSpot, Dynamics or other CRM environment. Test duplicate handling, permissions and recovery against your real workflow.

Interactive CRM integration planner

Define the sales action before mapping CRM fields.

Choose the closest journey. The result identifies the contracts and acceptance work to prioritize; actual objects, APIs, fields and capabilities depend on the CRM environment and signed Configurix scope.

Journey origin

Business trigger

CRM record model

Return path

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.

Connected software

Define which customer and pipeline data the CRM owns and which product revisions Configurix owns. Each API, calendar and two-way update is scoped and tested for your systems.

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

Configured customer project

Product fit

Qualified

Configured customer project

Requirements

Proposal

Configured customer project

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

Configured customer project

Order referenceConfigured customer project

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 integration

Your product. Your systems. A connected workflow.

Bring one complex product, your current systems and the result your team needs. We will define the configurator, custom software, responsibilities and acceptance checks together.

Questions and answers

A product configurator CRM integration connects customer and account context with a versioned configured project. CRM can provide contact, company, opportunity, owner, territory, campaign and permission context. Configurix can return the configuration ID and revision, product summary, dimensions, selected options, visual and document links, price or quote state, intent and activity timestamps. APIs, asynchronous jobs, webhooks and reconciliation keep the agreed records and lifecycle states connected.

CRM manages business relationships and sales processes: people, companies, accounts, ownership, activities, qualification, pipeline stages and outcomes. A product configurator manages what the customer or salesperson is designing: valid choices, rules, dimensions, 3D state, revisions, scoped pricing and configured outputs. Integration links them through stable IDs and associations without asking either system to replace the other's authority.

Configurix can include lead capture, project records, quotes and sales workflow for teams that want one connected platform, but it does not have to replace an established CRM. It can be scoped to create or update CRM records, attach configured-project context and let sales resume the exact design. The correct boundary depends on the existing sales process, CRM capabilities, required integrations and signed scope.

Configurix can be scoped to connect with CRM platforms such as Salesforce, HubSpot or Microsoft Dynamics 365 when the required APIs, permissions, objects, external identifiers and test environments are available. Support must be proven against the customer's actual CRM edition, configuration and workflow. A vendor name alone does not prove custom-object, association, routing, quote, duplicate or lifecycle behavior.

Store the data sales needs to identify, route, prioritize and reopen the project: configuration ID and revision, product family, concise option and dimension summary, completion and intent, price or quote status, value and currency where appropriate, visual and document links, source context, owner and timestamps. Keep detailed executable rules, geometry and every intermediate state in Configurix unless a specific CRM use case requires them.

Use immutable external keys, normalized identity fields, CRM search or upsert capabilities, explicit person-company associations and an agreed conflict policy. Every submission or event should carry a unique identity and idempotency key so retrying it updates the intended record. Reconciliation should report duplicate keys and unexpected one-to-many relationships rather than silently choosing one.

Keep a stable project or opportunity association while each material configuration and commercial change receives a revision. The CRM can display the current accepted summary and links while Configurix preserves the detailed revision history. Define when a new configuration invalidates a price, requires a new quote, updates forecast value or needs approval; never overwrite an accepted quote without traceability.

Test anonymous exploration, first identification, an existing contact and company, duplicate submission, conflicting identity, quote request, assignment, CRM-launched continuation, configuration revision, slow CRM, rejected authentication, webhook redelivery and reordering, won and lost outcomes, deletion and full reconciliation. Verify the visible sales workflow and exact project revision—not only API response codes.

A focused Configurix Fast Launch can usually target one working product in around seven days when inputs are prepared and broad CRM integration is not required. A white-label multi-product build with CRM objects, custom routing, identity resolution, quotes, lifecycle synchronization and other integrations can take up to 30 days depending on access, API capability, decisions, data readiness and review speed. The signed scope and acceptance plan remain authoritative.

Technical integration guide

Integration definition

Connect customer relationship context to canonical configuration state.

A useful product configurator CRM integration is more than a form connector. It tells sales who acted, what they configured, which revision and price context they saw, what they asked for and how to continue. It also tells Configurix which account, owner, territory or opportunity the project belongs to without copying CRM logic into the product model.

CRM context to Configurix

Contact, company, account and opportunity identity
Sales owner, dealer, territory and market
Campaign, source and consent context
Account catalogue and commercial permissions
Existing project and quote references
A secure link for assisted configuration

Configurix project to CRM

Configuration ID, revision and product family
Selected dimensions, options and finish summary
Price, currency, quote and document references
3D snapshot and resumable project link
Buyer action, completion and intent signals
Created, updated and submitted timestamps

Lifecycle and reconciliation

Owner, stage and qualification changes
Quote sent, viewed, revised and accepted state
Won, lost, inactive and privacy-deletion events
Duplicate, retry and out-of-order handling
Integration acknowledgement and error evidence
Scheduled completeness reconciliation

System-of-record matrix

Put every customer, product and commercial decision in one accountable place.

System	Typical authority	Boundary to resolve
CRM	People, companies, accounts, ownership, pipeline stage, activities, qualification and sales outcome	Do not turn the CRM into an uncontrolled copy of every configuration field and revision.
Configurix	Product rules, valid configuration state, interactive 3D, saved projects, revisions, scoped prices and quotes	Keep one canonical configuration ID that the CRM can link to and sales can reopen.
Marketing automation	Campaign journeys, consented communication, audiences, forms, attribution inputs and nurture activity	Define which consent, campaign and lifecycle fields are permitted to cross into CRM and Configurix.
CPQ or pricing	Commercial rules, account price context, discounts, approvals, quote totals and commercial validity	A CRM amount is an output or forecast unless it is explicitly the accepted price authority.
ERP	Customer master, sellable items, orders, tax, finance, availability, fulfillment and invoice state	Won opportunity does not automatically equal an accepted, complete and order-ready configuration.
Analytics	Behavioral events, acquisition context, funnel definitions, attribution analysis and reconciled outcomes	Use pseudonymous journey identity until identification is lawful and necessary; keep metric definitions explicit.

Canonical CRM handoff contract

Carry sales intent without flattening the configured product.

The contract must resolve the same person, company, opportunity and project after a retry, reassignment or revision. Stable identifiers connect the systems; explicit authority prevents one system from silently overwriting another.

identity

CRM tenant, record IDs, Configurix project ID, configuration ID and immutable external keys

person_company

Contact details, company, account, role and the association between each CRM record

ownership

Sales owner, team, dealer, territory, routing reason and effective assignment timestamp

attribution

Source, medium, campaign, landing page, referral and consented first- or last-touch context

project

Product family, market, locale, currency, dimensions, selected options and completeness

revision

Configuration revision, catalogue revision, rule revision, price revision and prior-revision reference

intent

Save, callback, quote, sample, appointment, checkout or another precisely named customer action

commercial

Price status, amount, currency, quote ID, document URL, expiry, discount and approval state

delivery

Event ID, idempotency key, correlation ID, sent time, received time and acknowledgement

privacy

Lawful basis or consent reference, permitted purpose, retention class and deletion behavior

Opportunity lifecycle

Follow the project from first configuration to accepted sale.

Not every product interaction deserves a CRM record, and not every CRM stage means a product is ready to order. Define the lifecycle as observable business events with a clear owner, required state and next action.

Anonymous exploration

A browser session can create useful product analytics without prematurely creating a CRM lead or attaching personal identity.

Identified save

The buyer supplies the minimum agreed details and receives a resumable project. Identity resolution runs before record creation.

Quote or consultation request

A valid configuration, current revision, commercial context and explicit intent become a routed CRM action—not a generic form submission.

Qualification and ownership

CRM applies territory, account, dealer, workload or value rules and returns the accepted owner and qualification state.

Sales continuation

The salesperson opens the same project, sees what the buyer chose and can revise it without losing the original revision or source.

Quote revision

Every material configuration or commercial change creates a traceable revision and updates the CRM summary under an explicit policy.

Accepted or won

Acceptance links the selected configuration and quote to the downstream order or project handoff rather than only closing a CRM stage.

Lost, inactive or deleted

Loss reasons, inactivity, retention and privacy deletion follow agreed rules across CRM, Configurix and connected marketing systems.

Identity and duplicate control

One customer action should create one accountable sales record.

Use external keys

Store stable Configurix IDs in CRM and CRM IDs in the integration mapping. Names, emails and visible project labels are not durable keys.

Resolve before creating

Search or upsert using agreed identifiers and normalization. Decide what happens when email, domain, account number or dealer context conflicts.

Associate, do not flatten

Keep contact, company, opportunity, quote and configured project relationships explicit instead of duplicating every field on one record.

Make retries safe

An idempotency key and event identity should make a repeated delivery update the intended record rather than create another lead or deal.

Preserve routing evidence

Record why an owner or dealer received the project and which data and rule revision produced that assignment.

Separate identity from consent

Knowing who someone is does not prove permission for every marketing purpose. Carry the required purpose and consent evidence separately.

Integration patterns

Use real-time calls only where the journey needs real-time answers.

Synchronous lookup

Use when: The journey needs an immediate account, owner, catalogue or existing-project answer.

Strength: Provides current context before the next customer or sales action.

Control: Set strict timeouts and a safe fallback so CRM latency does not freeze the configurator.

Asynchronous create or update

Use when: A save, quote request or qualified event can be acknowledged without waiting for all CRM operations.

Strength: Protects customer responsiveness and supports controlled retries.

Control: Use durable queues, idempotency, dead-letter review and visible processing state.

CRM-launched configuration

Use when: Sales starts from an existing contact, account or opportunity and needs the correct project context.

Strength: Reduces searching and lets sales continue one governed customer record.

Control: Use short-lived signed context, role checks and explicit rules for creating versus opening projects.

Webhook lifecycle

Use when: Owner, stage, activity, deletion or association changes should reach Configurix promptly.

Strength: Avoids constant polling and makes selected lifecycle changes responsive.

Control: Verify signatures, deduplicate, tolerate reordering and retrieve authoritative state when needed.

Scheduled reconciliation

Use when: Operational completeness matters beyond individual real-time calls and webhook deliveries.

Strength: Finds missing associations, stale owners, divergent stages and records that failed silently.

Control: Compare by stable keys and revision watermarks; assign an owner for every exception class.

Hybrid integration

Use when: Immediate lookups, durable writes, webhooks and periodic reconciliation serve different needs.

Strength: Balances customer speed with reliable lifecycle consistency.

Control: Document one event and data contract so the patterns reinforce rather than contradict each other.

Implementation blueprint

From one customer action to a governed CRM lifecycle.

Choose one real journey

Use a representative product, public or assisted entry point, customer action, CRM pipeline and downstream handoff.

Define record outcomes

Name exactly when a lead, contact, company, opportunity, project, activity or quote is created, associated or updated.

Assign authority

Mark the owner of identity, consent, assignment, configuration, price, quote, stage, order and analytics fields.

Design identity resolution

Choose external keys, search and upsert behavior, normalization, duplicate policy and conflict handling before importing data.

Version the contract

Define required fields, types, associations, enums, revisions, event names, idempotency and backwards compatibility.

Build the return path

Let sales reopen the correct configuration revision and return only the CRM lifecycle state Configurix truly needs.

Test failures and privacy

Prove retries, partial failure, slow CRM, duplicates, revoked access, deletion, redaction and audit evidence.

Operate and reconcile

Monitor latency, rejects, duplicate rate, missing associations and drift; review exceptions against agreed service ownership.

Security, privacy and access

Connect only the data and permissions the journey requires.

CRM integration handles personal data, commercial context and privileged project access. Treat authorization, consent, retention and deletion as contract behavior, not a policy document added after the API works.

Least-privilege OAuth scopes or service credentials

Tenant, environment and account isolation

Server-side secret storage and rotation

Signed launch context and short-lived links

Webhook signature verification and replay defense

Field-level minimization, redaction and logging rules

Retention, export and deletion propagation

Audit evidence for mappings, changes and failures

Working acceptance matrix

Twelve tests before sales depends on the CRM handoff.

An anonymous visitor can configure without creating personal CRM records before the agreed identification or intent trigger.

A first quote request creates or updates the intended person, company, opportunity and project records with correct associations.

Repeating the same request, webhook or retry does not create duplicate leads, deals, activities, quotes or configured projects.

An existing customer or account is resolved with the agreed external key and conflict behavior rather than matched by display name alone.

The CRM record stores a resumable link to the correct Configurix project and configuration revision with role-appropriate access.

Product family, dimensions, selected options, price status, currency, quote and visual references match the submitted configuration.

A salesperson can open the project from CRM, revise it and preserve the original customer revision and attribution context.

Owner, team, dealer, territory and routing reason follow the accepted rules and remain traceable after reassignment.

A slow or unavailable CRM does not lose the customer request, block safe continuation or cause uncontrolled repeated submission.

Out-of-order owner, stage, quote and deletion events converge to the authoritative state under the documented revision policy.

Consent, permitted purpose, retention, export and deletion behavior are proven across Configurix, CRM and connected marketing tools.

Reconciliation reports missing records, broken associations, duplicate keys, stale revisions and unresolved failures with accountable owners.

Failure patterns

What “connected to CRM” can hide.

Every interaction becomes a lead

The CRM fills with anonymous browsing and weak intent, making sales prioritization harder instead of more informed.

Email is the only identity key

Shared addresses, changed emails, dealer-created contacts and multi-brand accounts create false merges or duplicates.

The configuration becomes a text note

Sales sees a product description but cannot reopen the exact rules, options, dimensions, price and revision the buyer used.

CRM owns the product truth

Copied option and price fields become stale while Configurix continues to enforce a different catalogue and rule revision.

Two-way sync means every field

Unbounded bidirectional updates create loops, overwrites and unclear authority instead of a controlled lifecycle contract.

Retries create new opportunities

A network timeout or webhook redelivery produces duplicate sales work because no stable event or idempotency key exists.

Won stage proves order readiness

The pipeline closes while required configuration, approval, price, quote or production fields are still incomplete.

Successful API calls prove integration

Records exist, but associations, ownership, revisions, links, consent and reconciliation have never been tested end to end.

Primary technical references

Design against documented CRM objects, keys, associations and events.

Continue planning your configurator

Configurator integrations Lead generation Sales configurator software ERP integration

Product configurator CRM integration. Every enquiry with its product.

A product journey your team can continue.

Capture intent with the design

Continue the same conversation

Connect your actual CRM

Define the sales action before mapping CRM fields.

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.

Your product. Your systems. A connected workflow.

Tell us about your business

Questions and answers

How does a product configurator integrate with a CRM?

What is the difference between CRM and a product configurator?

Does Configurix replace a CRM?

Can Configurix integrate with Salesforce, HubSpot or Microsoft Dynamics 365?

Should a website configuration create a lead immediately?

Should Configurix create a lead, contact or opportunity?

What configurator data should be stored in CRM?

How can sales reopen the customer's exact 3D configuration?

How does CRM integration prevent duplicate leads and deals?

How should anonymous configurator activity be connected after identification?

Can a CRM launch Configurix from an opportunity?

Should CRM integration use APIs or webhooks?

How are configuration and quote revisions handled in CRM?

How should lead routing work for dealers and territories?

How do we protect customer data in a configurator CRM integration?

How do we test product configurator CRM integration?

What information is needed to scope CRM integration?

How long does a Configurix CRM integration take?

Can Configurix build custom business and factory software with the configurator?

Connect customer relationship context to canonical configuration state.

CRM context to Configurix

Configurix project to CRM

Lifecycle and reconciliation

Put every customer, product and commercial decision in one accountable place.

Carry sales intent without flattening the configured product.

Follow the project from first configuration to accepted sale.

Anonymous exploration

Identified save

Quote or consultation request

Qualification and ownership

Sales continuation

Quote revision

Accepted or won

Lost, inactive or deleted

One customer action should create one accountable sales record.

Use external keys

Resolve before creating

Associate, do not flatten

Make retries safe

Preserve routing evidence

Separate identity from consent

Use real-time calls only where the journey needs real-time answers.

Synchronous lookup

Asynchronous create or update

CRM-launched configuration

Webhook lifecycle

Scheduled reconciliation

Hybrid integration

From one customer action to a governed CRM lifecycle.

Choose one real journey

Define record outcomes

Assign authority

Design identity resolution

Version the contract

Build the return path

Test failures and privacy

Operate and reconcile

Connect only the data and permissions the journey requires.

Twelve tests before sales depends on the CRM handoff.

What “connected to CRM” can hide.

Every interaction becomes a lead

Email is the only identity key

The configuration becomes a text note

CRM owns the product truth