Custom software for manufacturers
We specialize in complex, configurable products. Configurix builds custom configurators and software around your permitted dimensions, compatible options, approvals and component mappings. Keep one product specification connected to 3D, pricing, quotes and factory data.
Interactive rule evaluator
Try an example bioclimatic pergola to see how dependencies, exclusions, dimensional checks and review decisions work together.
The current demo state passes its dependency, exclusion and dimensional checks.
Width is inside the allowed range.
Selected side elements do not conflict.
Derived state
Custom software for manufacturers
Use the agreed configuration and revision in lead qualification, technical appointments, quotes, material lists and order handoffs. We define the rules, responsibilities and integrations for each step with your team.
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
Configured product
Product fitQualified
Configured product
RequirementsProposal
Configured product
Next actionLet a configured project continue into a sales consultation, technical review, survey or installation appointment. Connect calendars, responsibilities and reminders to the same customer record.
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-01Frame assembly | 1 |
| PNL-02Panel set | 1 |
| KIT-03Hardware kit | 1 |
Mapped to your product codes
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
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.
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.
Configured product
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.
Choose the workflows your implementation needs. We build and validate them against your products, documents and target systems.
Plan your manufacturing configuratorShow us one product range, difficult combinations and the outputs your teams need. We can scope the configurator, business software and acceptance cases around your catalogue.
Clear definition
A catalogue lists what exists. A rules engine determines which combination of those products, dimensions, components and options can exist together for a specific market, role or project. It evaluates the current configuration whenever a relevant input changes and returns a controlled result.
That result may allow the choice, require another component, calculate a derived value, replace an option, display a warning, request specialist review or stop an invalid state. The important part is consistency: the saved configuration must mean the same thing to the 3D scene, live-price calculation, quote, order and optional bill of materials.
Rule types
Define which choices exist for a product, market, role or channel and which safe starting value appears first.
A dealer catalogue starts with its assigned product series and default finish.
Require one field, component or service when another selection or condition is present.
Selecting motorized louvers also requires a compatible control package.
Prevent incompatible combinations or replace an option with the approved alternative while keeping the reason visible.
A selected side element can exclude a conflicting element on the same elevation.
Validate minimums, maximums, step sizes, quantities, clearances and dimensional relationships.
Width must use an accepted increment and remain inside the chosen system range.
Calculate values the user should not enter manually, such as module count, material area or component quantity.
The selected span and system determine a derived support or module count.
Separate a valid configuration, a state that needs specialist review and a combination that cannot proceed.
A boundary case remains saved but cannot become an approved quote until reviewed.
Connected architecture
Clean ownership makes errors easier to find. Each layer answers a different question while reading the same configuration identity and stable product data.
Catalogue
What exists?
Families, components, option groups, identifiers, lifecycle and market availability.
Configuration rules
What is allowed?
Requirements, exclusions, dependencies, limits, derived values and review states.
Geometry
What should change visually?
Dimensions, visibility, material assignment, position, repetition and animation.
Pricing
What should it cost?
Price lists, formulas, quantities, accounts, markets, discounts, tax and rounding.
Output mapping
What should leave the system?
Quote lines, product codes, BOM or order components, drawings and integration fields.
Rule record
A spreadsheet cell, remembered exception or unlabeled script is difficult to test and dangerous to change. Use a shared rule record that product, engineering, commercial and implementation owners can read.
Stable rule ID
A durable identifier that does not change when customer-facing wording is renamed or translated.
Plain-language intent
The product or commercial reason the rule exists, written so a reviewer can challenge it.
Condition
The product state, audience, date, market or value that activates the rule.
Action
Allow, require, hide, exclude, substitute, calculate, warn, request review or stop.
Priority and scope
Where the rule applies and how it resolves a collision with defaults, market rules or another action.
Message and recovery
What the user sees and the specific choice that returns the product to an accepted state.
Owner and evidence
The accountable source, effective version and normal, boundary and invalid test cases.
Across configurable products
Execution and conflicts
Load context
Resolve product revision, market, channel, account, role and effective date before presenting choices.
Apply availability and permissions
Remove choices the current audience cannot use without changing their stable product identity.
Apply defaults and user input
Create a complete current state while preserving explicit choices that remain valid.
Evaluate constraints and derived values
Run requirements, exclusions, limits, substitutions and calculations until the state is stable.
Return one explained result
Expose accepted, review or invalid status plus messages and recovery actions to every connected layer.
Acceptance and regression
A polished common journey proves very little about rule accuracy. Keep a permanent pack that tests the values and combinations most likely to expose contradictions.
A common configuration follows the expected route without unnecessary warnings or automatic changes.
The smallest accepted value remains selectable, visible, priced and represented in every required output.
The largest accepted value behaves exactly as defined, including derived components and performance.
A value immediately beyond an accepted limit produces the intended stop, correction or review state.
Selecting the trigger creates the required choice, message or component without leaving stale data.
Two incompatible choices cannot silently coexist; the user can see why and how to recover.
A saved project created under an older rule version is reopened, explained and handled according to policy.
The same accepted state reaches price, quote, BOM or integration output using stable identifiers.
Versioning and ownership
Each saved configuration, quote and accepted order should remain traceable to the product and rule revision that produced it. When a rule changes, decide which new, saved, quoted and ordered projects it affects before publication.
Assign an owner for the rule source, an owner for implementation and an approver for the resulting product behavior. Separate permission to edit from permission to publish. Re-run the relevant rule, price, visual and output cases, then monitor the first live use and retain a correction path.
Read the maintenance and governance guidePrimary technical references
These sources illustrate established ways to describe conditional requirements, rule composition, inclusion, exclusion and execution order. Configurix scopes the actual implementation from the customer's catalogue and accepted architecture.
A primary technical reference for conditional requirements and if/then/else validation patterns. It is an external reference model, not a statement about Configurix internals.
Explains AND, OR, exclusive-OR and NOT composition—useful concepts when documenting overlapping validation criteria.
An official example of configuration rules limiting a product to valid states and why execution order matters when actions affect the same attributes.
An official example of configurable attributes governed by inclusion, exclusion and bundling rules.
Rules-engine FAQ
Continue your research
Define stable IDs, characteristics, variants, configuration revisions, 3D mappings, price context and output identity.
Connect ranges, increments, units and derived values to generated geometry, live price and controlled technical outputs.
Govern module identity, ports, adjacency, sequence, repetition and derived connecting parts as one accepted assembly.
Turn accepted product state into traceable line items, account pricing, discounts, services, tax and quote revisions.
Use rule-selected components and derived quantities to create exact configured, engineering, manufacturing and installation outputs.
Understand how catalogue, rules, 3D, pricing, quotes and project data work as connected layers.
Turn rule behavior into RFP language, boundary cases and vendor acceptance evidence.
Prepare product knowledge, ownership, assets, prices, integrations and acceptance for launch.
Define which fields, options, rules, visuals and commercial inputs business teams can safely operate without source-code changes.
Control rule changes, versions, publishing, saved projects and regression testing after launch.
Connect accepted product state to CRM, ERP, ecommerce, documents and optional BOM output.
Use shared definitions for constraints, dependencies, exclusions, solution space and configuration identity.
Turn rule boundaries, invalid states, saved revisions and downstream consequences into permanent regression evidence.
