Self-service product configuration
Let buyers configure now. Keep your product rules in control.
Configurix self-service product configurator software gives customers, business buyers, dealers and sales teams a clear path from product discovery to a valid 3D configuration, the right commercial result and a connected next step—without rebuilding the project in another system.
Havenform Outdoor
Customer configurator
Your project
Next step
Request a project quote
Product, revision and selections stay attached.
Direct definition
What self-service product configuration actually means.
A self-service product configurator lets a buyer or channel partner identify and assemble a valid product through a digital interface without requiring a salesperson to perform every decision. It uses governed catalogue data and product rules to control dimensions, components, materials, finishes, accessories and allowed combinations.
Self-service is not the same as exposing every option. A useful journey guides people from what they know toward the technical decisions the product requires. It explains consequences, prevents impossible combinations, updates the visual product and makes review conditions explicit.
The journey is complete only when the selected product can continue. Configurix can preserve the configuration and its revision for a saved project, sales consultation, dealer follow-up, quote, cart, order or scoped downstream handoff. The destination depends on the product, audience and commercial model.
One engine, different channels
Give each audience the right route—not the same screen.
Public visitors, account customers, dealers and sales teams can work from the same governed product knowledge while receiving different catalogues, prices, documents, permissions and next actions.
Prospects and end customers
Public website
Let visitors explore a governed catalogue, configure a valid product and continue to a saved project, consultation, quote request, cart or another defined action.
Public catalogue · public price or quote path
Known B2B or repeat buyers
Customer account
Give authenticated customers their assigned products, account price context, saved projects, revisions, documents and controlled reorder or approval journeys.
Account catalogue · account terms · project history
Dealers, distributors and resellers
Dealer portal
Equip partners with approved products, price lists, margin permissions, branded proposals and structured order or project handoff without exposing administration controls.
Partner catalogue · role pricing · assigned markets
Sales, showroom and field teams
Sales-assisted channel
Use the same product logic during calls, showroom sessions and site visits, then continue the buyer's saved configuration instead of rebuilding it in another tool.
Sales permissions · assisted workflow · human review
Connected buyer journey
From a question to a usable product record.
A self-service configurator should reduce friction without removing control. Each stage adds structured information to the same project so the buyer, commercial team and connected systems do not have to reinterpret the selection.
Understand the requirement
Capture use, dimensions, site conditions, preferences, location, account and any other facts that genuinely affect the permitted solution.
Select the right product family
Recommend or reveal the relevant system from governed catalogue data instead of asking the buyer to interpret internal model codes.
Build a valid configuration
Apply ranges, increments, dependencies, exclusions, derived quantities and explicit engineering or survey review conditions.
Show each decision in 3D
Update geometry, materials, visible components and the selected specification from the same configuration state.
Return the permitted commercial result
Show a live price, price range, quote-only state or approval route according to market, account, role and product rules.
Continue without re-entry
Preserve the configuration ID and revision for a quote, cart, order, CRM opportunity, dealer follow-up or controlled production handoff.
Role and channel control
Same product truth. Different commercial permissions.
A connected platform can reuse product knowledge across channels without making sensitive price or customer data public. The matrix below is a design pattern; the working implementation must be accepted against the actual roles and systems.
| Control | Public buyer | Customer account | Dealer | Sales team |
|---|---|---|---|---|
| Catalogue | Public range | Assigned products | Partner range | Governed range |
| Price | Retail, range or hidden | Account price | Buy/sell context | Controlled commercial view |
| Discounts | Not available | Contract rules | Permission-based | Permission and approval |
| Documents | Summary or quote request | Account proposal | Branded or co-branded | Quote and internal output |
| Next action | Save, enquire or buy | Approve or order | Quote or submit | Continue, review or approve |
| Sensitive data | None | Own account only | Assigned accounts only | Role-dependent |
Product rule foundation
Self-service works when the rules do the hard work.
Read the product rules guideProduct boundaries
Minimums, maximums, increments, permitted shapes, module counts, structural limits and required measurements.
Compatibility
Dependencies, exclusions, prerequisites, conditional components, replacement choices and market-specific availability.
Derived configuration
Calculated quantities, component counts, areas, lengths, supports, fixings, packaging or other values derived from selections.
Commercial logic
Price books, formulas, quantities, services, tax context, currencies, discounts, promotions, margins and approvals.
Review conditions
Cases that require a survey, engineering decision, stock check, commercial approval or another controlled human intervention.
Output permissions
Which roles can see, save, quote, download, order, revise, approve or hand a configuration to another system.
Structured project handoff
Send the project—not another blank contact form.
The durable value of self-service is the configured context it creates. A salesperson, dealer, cart, quote service or operational system should receive a traceable product record rather than reconstructing the buyer's decisions from a message.
Configuration identity
Stable ID, revision, status, timestamps and catalogue version
Buyer and channel
Customer or account, role, market, language, source and assigned dealer or salesperson
Configured product
Family, dimensions, components, materials, finishes, accessories and derived values
Validation
Rule result, warnings, review conditions, accepted exceptions and unresolved inputs
Commercial state
Price context, currency, tax, discounts, services, approval and quote or cart reference
Visual state
3D scene state, selected camera or snapshot and optional AR or document references
Customer intent
Save, consultation, quote, checkout, order, reorder or another explicit next action
System handoff
CRM, ecommerce, ERP, PIM, document, analytics or production references and delivery status
Buyer confidence and control
Self-service should feel independent—not unsupported.
A usable journey helps people progress alone and preserves a clean route to human expertise. These safeguards make the experience more understandable, maintainable and trustworthy across devices, roles and changing catalogue data.
Make validity visible
Tell the buyer when the configuration is complete, when information is missing and when the project requires human review. Do not hide uncertainty behind a generic success screen.
Keep help inside the journey
Explain technical choices in the customer's language, preserve progress when assistance is requested and give support staff the same saved configuration.
Design beyond desktop dragging
Provide keyboard-operable controls, clear focus, text alternatives, touch targets, descriptive errors and non-drag methods for essential adjustments.
Version changing data
When prices, rules or catalogue content change, define whether an older saved project remains valid, is recalculated or enters review before continuation.
Separate roles and accounts
Test authorization on the server side. A public user must not receive dealer costs, account prices, other customers' projects or administrative actions.
Keep the output connected
Quotes, carts, orders and operational records should reference the configuration and revision that produced them so later changes remain traceable.
Implementation blueprint
Build the first journey around evidence.
Start with one representative product and a complete buyer-to-handoff path. Accept the product rules, commercial result and downstream record before expanding across a catalogue, partner network or international market.
Scope
Choose one audience, product and action
Define who will use the first journey, which representative product it covers and whether success means a saved project, consultation, quote, cart or order.
Catalogue
Prepare products and availability
Structure families, components, options, market assignments and role visibility. Record ownership and normal, boundary and exceptional examples.
Rules
Model technical decisions
Capture dimensions, dependencies, exclusions, formulas, derived quantities and review states from product experts rather than from interface labels alone.
Experience
Design the self-service sequence
Order questions around what each audience knows, reveal complexity progressively and define explanations, validation, backtracking and assistance.
Commercial
Connect price and permissions
Map price authority, account context, discounts, approvals, tax, services, documents and the commercial result each role may receive.
Systems
Define the durable handoff
Map identifiers, payload fields, source-of-truth ownership, API or webhook behavior, retries, duplicate handling and failure visibility.
Acceptance
Test representative journeys
Use public, customer, dealer and sales roles; mobile and keyboard access; price examples; invalid choices; revisions; permissions and downstream checks.
Operation
Launch with named ownership
Assign catalogue, rule, price, translation, asset, document, integration and analytics owners before expanding products, markets or channels.
Measurement model
Measure the journey against your own baseline.
Define each event and denominator before launch, preserve stable configuration identifiers and reconcile digital behavior with the connected quote, order or CRM outcome. These measures describe an evaluation method, not guaranteed results.
Open the analytics and KPI guideEligible session
A session in which the self-service journey is available and relevant
Journey start
An eligible session that begins product discovery or configuration
Valid configuration
A journey that reaches the documented complete and rule-valid state
Assistance request
A saved project intentionally handed to a salesperson, dealer or expert
Qualified action
A valid project that reaches quote, cart, order, reorder or another defined action
Follow-up progression
A structured project contacted, quoted, approved, won or lost in the connected system
Operational acceptance
A submitted configuration accepted downstream without avoidable clarification or re-entry
Adoption by role
Relevant customers, dealers or salespeople who use the journey for the intended work
Vendor acceptance checklist
Ask every vendor to prove the same journey.
Replace feature-list comparisons with a working scenario based on your real product, roles, price examples and destination systems.
- 01A new visitor can reach a valid representative configuration without product-code knowledge.
- 02Minimum, maximum, increment and one derived dimension behave as the approved examples specify.
- 03At least one dependency and one exclusion change the available choices and remain understandable.
- 04The 3D product, specification and commercial result use the same canonical configuration state.
- 05The journey works at the agreed mobile width and all essential actions work without dragging.
- 06A customer can request help without losing configuration identity, revision or selections.
- 07Public, customer, dealer and sales roles receive only the catalogue, prices and actions they are permitted to access.
- 08Saved projects explain or control what happens after a catalogue, rule or price version changes.
- 09A quote, cart or order references the exact configuration revision that created it.
- 10CRM or dealer handoff includes structured product context, not only contact details and free text.
- 11Integration failure is visible, retryable and protected from duplicate project or order creation.
- 12Analytics events use stable names, documented properties and configuration identifiers that can be reconciled with outcomes.
Primary implementation references
Build accessibility and data contracts into the scope.
WCAG 2.2
Primary accessibility requirements relevant to keyboard access, pointer gestures, focus, labels, errors, redundant entry, authentication and consistent help.
Google Analytics recommended events
A primary reference vocabulary for lead and ecommerce actions. Configuration-specific events still require a documented implementation contract.
JSON Schema
A primary specification for describing and validating the structured configuration and integration data exchanged between systems.
OpenAPI Specification
A standard format for documenting HTTP APIs, request and response shapes, authentication and integration behavior.
Self-service configurator FAQ
Practical answers for product and commercial teams.
These answers describe Configurix scope and implementation patterns without treating unverified outcomes, production outputs or integrations as automatic.
Related Configurix research
Continue from buyer experience to operating system.
Guided selling software
Needs-led questions, governed recommendations, product rules and structured next steps.
Read guideProduct selector software
Requirements-led selection, explainable recommendations and a connected path into configuration.
Read guideB2B product configurator
Account catalogues, dealer prices, permissions, proposals, approvals and orders.
Read guideSales configurator software
Continue website and dealer configurations through assisted sales, pricing, proposals and approval.
Read guideEcommerce product configurator
Product pages, variant logic, live retail pricing, cart identity and checkout patterns.
Read guideOnline 3D product configurator
Website delivery patterns, performance, crawlable content, attribution, saved projects and structured lead capture.
Read guideVisual CPQ software
Configuration, price control, proposals, approvals, revisions and commercial handoff.
Read guideProduct configurator integrations
CRM, ERP, ecommerce, PIM, API, webhook, document and optional production connections.
Read guideYour product, your channels
Turn product knowledge into a self-service journey people can finish.
Bring one representative product, your pricing examples and the next step you want customers or dealers to reach. We will map the rules, experience and connected record.