Product configurator data architecture
A product data model that connects choices to work.
We specialize in complex products. Configurix builds custom configurators and business or factory software around your product data, rules and working process. Connect what customers select to the 3D view, price, quote, materials and the teams that handle the next step.
Map your product workflowUnsaved draft
Cabinet
- Width (mm)
- 800 mm
- Finish
- White
- Local changes
- 0
Width rule passed
Explore a working product record.Decide what owns the orderable configuration
A browser can render a pergola as someone adjusts its width. Before quoting, an authoritative rules service should validate that width, the requested accessories and the user's available catalogue. The quote and materials list can then reference the same saved selection and rules revision. Keep ERP item ownership in ERP if that is already where the factory maintains it. Bring one product record to discovery and label which system can change each field.
Change a rule while a quote is open
Save a valid quote, then publish a new compatibility rule that prohibits the selected screen on new orders. Reopen the earlier quote and check its price, document and rule version. If you edit it, the system should identify the new conflict and route the decision under the agreed policy. Send an accepted revision to a test ERP with a missing item mapping. Verify that someone can correct and retry the export without duplicating the order.
This test gives sales, product and operations something concrete to review when scoping a custom product configurator.
One product meaning. Several connected views.
Keep identity stable
Separate product, option and component IDs from their visible names. Renaming or translating a choice should preserve its stored meaning.
Share the accepted product state
Make the visual view, calculations, quote and connected systems use the same selections, units and revisions.
Build around factory and sales work
Map the configuration to qualification, appointments, material lists, orders, jobs and invoices where agreed, with clear ownership at every step.
Explore a working product record.
Choose a family, edit its width rule and change the options. Compare the customer view, structured record and handoff. The draft updates locally; saved identity and production approval are separate lifecycle steps.
Width rule passed
Cabinet
- Width (mm)
- 800 mm
- Layout
- Freestanding
- Finish
- White
- Accessory
- Shelf
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 business software
Product identities, rules, visual mappings, commercial ownership and factory outputs are agreed for your implementation. A valid width rule is one check within a wider product and release process.
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.
New enquiry
Structured product record
Product fitQualified
Structured product record
RequirementsProposal
Structured product record
Next actionCalendars 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.
- 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.
| 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.
Quote revision
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.
- 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.
Structured product record
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.
Map your product workflowBuild the data contract behind the interface.
Separate the catalogue model from a customer project
The catalogue defines product families, characteristics, allowed values, dimensions and reusable rules. A configuration records one set of choices against that definition. Keep product-model revision, configuration identity, accepted project revision and quote identity distinct. Define what happens when an item is withdrawn, renamed or superseded. A screen title or a translated label is not a durable identifier.
Define types, units and product rules
Store a width as a number with a defined unit, an accessory as a boolean or stable option value, and a finish as an allowed identifier. Validate required fields and data shape, then evaluate dependencies, exclusions and engineering constraints separately. JSON Schema can check structure; it does not establish that a product is safe to build. Apply authoritative checks on the receiving server as well as in the interface.
Map 3D to the same structured choices
Connect product fields to the relevant geometry, materials, visibility and dimensions. Keep a controlled asset revision and test that the scene matches the saved selection. A glTF file delivers visual assets; it does not automatically contain the commercial product model. Avoid treating a node index, translated mesh name or camera position as the only product identity.
Keep price context and quote revisions explicit
A valid product can receive different prices by account, quantity, market or service package. Name the responsible pricing system and preserve currency, price-list revision, quantities, tax responsibility and approval context. Tie the issued quote to an accepted configuration revision. Repricing a reopened project must follow the agreed policy rather than silently rewriting a previous offer.
Turn selected options into usable material data
A bill of materials needs component or item identifiers, quantities, units, revision and review status. Define the actual mapping for cabinet panels, door components, pergola supports or your own product family. Cutting rules, waste allowances, operations and engineering release need their own accepted logic. Agree which PLM, ERP, MES or factory team owns each downstream record and acknowledgement.
Connect CRM, calendars and operational software
A saved configuration can become the shared reference for a qualified enquiry, sales activity, appointment or order. Configurix can build the custom CRM, calendar, quote, job and invoicing workflow around that reference, or connect to your existing systems. Define permissions, consent, customer ownership and how a salesperson continues the same project. Send stable fields instead of reconstructing choices from a PDF.
Control change and prove the integration
Preserve source and target revisions, lifecycle status and who changed the product. Agree whether older projects remain unchanged, require review or migrate. Test invalid input, missing values, duplicate delivery, timeout, retry, permissions and reconciliation. Keep machine-readable JSON numbers separate from localized display formatting. Replacing a label or changing language must not alter the selected product or its units.
Publish useful content without exposing private records
Your operational model and public SEO markup serve different purposes. Publish clear native descriptions, supported choices, original media and useful answers in accessible HTML. Product-variant markup belongs to appropriate real product pages, not every internal configuration record. Keep customer identifiers, account terms and private projects out of public metadata. Link the public explanation to a contextual enquiry and test the real mobile journey.
Your catalogue. Your rules. Your connected software.
Bring one complex product and its current options, materials, price calculation and required outputs. We will define the data model, configurator, custom software and acceptance tests together.
Product-data questions
Primary technical documentation
These references explain data validation, JSON, 3D assets and product publishing. They support distinct technical layers; they do not replace your product rules or implementation tests.
Detailed technical reference
Clear definition
The model beneath the configurator interface.
A product configurator data model describes the complete solution space in structured terms: product families, characteristics, option groups, allowed values, dimensions, components, rules, revisions and mappings. It also defines how one accepted customer configuration is identified, saved and reproduced.
The visual interface is one view of that model. The price calculation, quote, CRM record, ecommerce cart, configured order and optional bill of materials are other views. They can live in different systems, but they must agree on identifiers, product revision, selected values, units and configuration revision.
Core layers
Six parts of a connected product model.
Product family and revision
The configurable system, its stable identity, lifecycle state and effective product-model revision.
A saved project can state exactly which product definition it used.
Option groups and characteristics
Named decisions such as dimensions, mounting, roof, finish and accessories, each with a data type and allowed values.
Labels can change or translate without changing the stored meaning.
Rules and validation state
Dependencies, exclusions, ranges, derived values, warnings and the rule revision that accepted the configuration.
The system can explain why a choice was allowed, changed, reviewed or stopped.
3D and visual mapping
The node, material, visibility, dimension, animation or camera behavior driven by each accepted field.
The 3D scene displays the same product state that is saved and priced.
Commercial context
Price-list identity, account, market, currency, date, quantity, tax and approval context—separate from product meaning.
The same valid product can receive the correct commercial result for each audience.
Output and system mappings
Quote lines, product codes, CRM fields, cart payloads, configured-order data and optional BOM component mappings.
Every receiving system gets stable identifiers rather than trying to parse display text.
Identity and revisions
Give every meaning a durable identity.
One identifier should answer one question. This keeps product meaning separate from translations, interface labels and downstream document numbers.
Product family ID
Identifies the configurable system, not a customer-facing page title.
Model revision
Identifies the effective catalogue and rule structure used to create the state.
Characteristic ID
Identifies a decision such as width, mounting or finish independently of its label.
Value or component ID
Identifies the selected value, prepared variant or physical component mapping.
Configuration ID
Identifies the saved project state across sessions and connected systems.
Configuration revision
Identifies each accepted change without overwriting an earlier quote or approval.
Price result ID
Connects a calculated commercial result to its inputs and effective price context.
Output or order ID
Connects the configuration revision to the generated document or downstream record.
Variants and made-to-order products
A variant selector is not the whole configuration model.
Prepared variant
A known combination with its own SKU or product identity. Useful for stocked and frequently sold states.
Runtime configuration
A structured state assembled from dimensions, modules, options and rules. Useful for made-to-order products.
Matched result
A runtime state may match a prepared variant or continue as a configured order with characteristic values.
Source of truth
Connected does not mean stored in one database.
A connected configurator can read from and write to several systems. The requirement is one authoritative owner for each field, stable mappings and visible failure handling.
Product catalogue or PIM
Families, stable product and option IDs, descriptions, lifecycle and market availability.
Runtime camera state or customer-project status.
Configuration model
Characteristics, allowed values, dependencies, exclusions, dimensions, derived state and rule versions.
Customer credit status or final accounting documents.
3D asset model
Geometry, materials, nodes, animation, camera presets and mapping to stable configuration fields.
The authoritative commercial price or translated product identity.
ERP, pricing or CPQ
Price lists, formulas, accounts, discounts, tax, approvals and configured commercial result where agreed.
Unversioned visual labels as a substitute for product identifiers.
CRM or project system
Customer, opportunity, owner, stage, activity and follow-up state.
The only copy of the product model or engineering rules.
ERP or production system
Accepted order, component, routing, production and fulfilment records where included.
A guessed configuration reconstructed from a PDF description.
Languages and markets
Translate labels. Preserve product meaning.
A multilingual configurator should not create a separate technical model for every language. It should render market-aware content around shared stable product IDs.
Language-neutral
Product, characteristic, value and component IDs; units stored explicitly; configuration and revision identity.
Market-aware
Availability, defaults, regulatory copy, price context, currency, tax and commercial documents.
Translatable
Product names, option labels, guidance, validation messages, quote content and customer communications.
Test completely
Configuration, rules, price, quote and destination records in every priority language and market—not only navigation labels.
Acceptance tests
Prove the record survives the real lifecycle.
Rename and translate
Rename an option and render it in another language. The stored IDs, price mapping and reopened project remain unchanged.
Save and resume
Save a valid project, close the session and reopen it. Every choice, derived value, visual state and revision is reproducible.
Revise after quote
Change one price-relevant field after issuing a quote. A new configuration and quote revision is created without rewriting history.
Change the rule model
Open a project created under an older rule revision. The system follows the agreed remain, review or migrate policy.
Send downstream
Create the target CRM, cart, ERP or BOM record from structured fields and verify identifiers, units, quantities and revision context.
Recover from failure
Reject or time out a destination call. The configuration remains intact and the operator sees an actionable delivery state.
Search-facing product data
Operational truth and SEO markup serve different jobs.
Product and ProductGroup structured data can help search engines understand visible products and prepared variants. It does not replace the operational model needed for rules, arbitrary dimensions, saved revisions, pricing context or production mappings.
Publish what the page represents
Use eligible Product or ProductGroup markup for visible product facts and prepared variants with unique IDs, canonical URLs and compliant offers where applicable.
Keep the richer system record
Store characteristic values, rules, visual mappings, configuration revisions, price context and downstream identity in the governed application model.
Primary references
Reference models for variants, characteristics and connected product data.
SAP: Variant Configuration
Official documentation describing configurable product structures using characteristics, configuration profiles and object dependencies.
SAP: Advanced Variant Configuration
Official reference for single- and multi-level configuration models, integrated product data and simulation including configurable BOMs.
Google: Product variant structured data
Official guidance for search-facing ProductGroup and Product variant markup, unique IDs and variant grouping. This is a publishing layer, not an operational configurator model.
Khronos: glTF
Official resources for efficient real-time 3D asset delivery. A visual asset format still needs explicit mapping to the governed product state.
Data-model FAQ
Detailed answers for product owners, IT and operations.
Continue your research
Connect the data model to rules, systems and delivery.
Modular product configurator
Model module instances, typed ports, slots, assembly relationships, derived parts and output mappings with durable identities.
Product configurator vs digital twin
Separate reusable product models, configured instances, physical assets and operational twin state with stable lifecycle identity.
Product rules engine
Define dependencies, exclusions, dimensional validation, derived values and rule versioning.
Product pricing engine
Use stable configuration IDs and commercial context to create traceable live-price results and quote revisions.
Configurator BOM generation
Map stable selections and derived values to exact component identities, quantities, revisions and operational destinations.
Configurator security and privacy
Classify records, enforce object and tenant boundaries, minimize browser exposure and test the complete data lifecycle.
3D asset pipeline
Bind stable product, component and finish IDs to nodes, materials, modules, transforms and governed asset revisions.
Product configurator integrations
Turn source ownership and configuration identity into reliable CRM, ERP and ecommerce contracts.
Product configurator PIM integration
Map product families, variants, attributes, translations, media and publication revisions to executable configuration.
Requirements checklist
Write testable data, rule, 3D, pricing, revision and output requirements for vendors.
Implementation guide
Prepare the catalogue, owners, assets, prices, journeys and evidence required for launch.
Maintenance and governance
Control catalogue changes, publishing permissions, saved projects and historical meaning.
Product configurator glossary
Align definitions for characteristics, variants, configuration identity, BOM, PIM, ERP and CPQ.
Bring one representative catalogue.
We will map its identities, characteristics, rules, visual states, price inputs and required operational outputs into one reviewable model.