Custom configurators and connected business software

Configurator order management. Keep the accepted product connected.

We specialize in complex products. Configurix builds custom configurators and order workflows that connect the customer's approved design with quotations, materials, assigned jobs and the systems your factory uses.

Plan your integration
Configured order workflow

Accepted quote

Order review

Factory handoff

Define the system that accepts the order and the teams that release production, delivery and invoicing. A submitted configuration remains subject to the agreed commercial and technical checks.

A product journey your team can continue.

Approve a defined product

Keep the selected dimensions, options, documents and commercial terms with the accepted configuration. Make outstanding technical reviews visible before an order is released.

Connect orders and assigned work

Turn the agreed order structure into the scoped jobs, production steps or installation tasks your team needs. Preserve responsibility and revision history through each handoff.

Control later changes

Keep amendments connected to the original order and the new product revision. Agree how price changes, deliveries, deposits and invoice references return from the responsible systems.

Interactive order architecture planner

Define acceptance, authority and change before creating the first order.

Choose the closest journey. The result identifies the contracts and acceptance evidence to prioritize. Actual systems, fields, payment responsibilities and fulfilment behavior depend on the working environment and signed Configurix scope.

Journey source
Acceptance trigger
Order authority
Change model

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 the system that accepts the order and the teams that release production, delivery and invoicing. A submitted configuration remains subject to the agreed commercial and technical checks.

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 order workflow

Product fit

Qualified

Configured order workflow

Requirements

Proposal

Configured order workflow

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
ComponentQuantity
FRM-01Configured components1
PNL-02Materials and quantities1
KIT-03Agreed operations1

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
  1. Accepted quote01
  2. Configured order02
  3. Production job03
  4. 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 order workflow

Order referenceConfigured order workflow
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.

  1. 01Your website
  2. 02Configurator
  3. 03CRM & calendar
  4. 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.

Tell us about your business

Step 1 of 2 — your details, then pick a time.

2 min

By submitting you agree to be contacted about Configurix. We respect your privacy.

Questions and answers

Technical integration guide

Order-management definition

Four records connect the sale without collapsing into one vague “order.”

A dependable workflow preserves the meaning of each record. The configuration proves what was selected. The quote proves the commercial offer. The configured order proves what was accepted. The operational order proves what the responsible downstream system received and acknowledged.

Configuration

A versioned set of customer, dealer or sales choices that is valid under the product rules and tied to a product-model revision.

Quote

A commercial proposal for a specific configuration, price context, validity period, terms and customer or account.

Configured order

An accepted commercial request that preserves the exact configuration revision and provides structured order lines and references.

Operational order

The sales, fulfilment or production record accepted by ERP, ecommerce or OMS and acknowledged with its own identity and state.

System-of-record matrix

Put product intent, commercial approval and operational state in the right systems.

SystemPrimary responsibilityBoundary to prove
ConfigurixProduct rules, interactive 3D, valid selections, dimensions, derived values, saved project and accepted configuration revisionPreserve what was configured and approved; do not silently turn a draft or invalid revision into an order.
CRM or CPQAccount, contact, opportunity, sales owner, commercial approval, proposal and customer decision contextA won opportunity can trigger order preparation, but it does not replace product or order-line validation.
EcommerceCart, checkout, payment or deposit, tax presentation, customer account and online order lifecycle by scopeMap a configured product deliberately; a generic SKU line cannot explain every made-to-measure choice.
ERPCustomer, item, price, tax, credit, sales order, inventory, procurement, planning, delivery, invoice and financeERP should accept, reject or hold the configured order explicitly and return the authoritative order identity.
OMSOrder intake, orchestration, provider coordination, fulfilment source, exception and cross-channel statusAn OMS can coordinate the journey without becoming the source of every product rule or engineering detail.
MES, WMS or installationProduction execution, warehouse fulfilment, dispatch, survey, scheduling, installation and operational evidenceReceive only released work with the correct order and configuration revision, then acknowledge actual progress.

Canonical configured-order contract

Carry identity, revision and commercial meaning with every order field.

An order payload is not an export of every field Configurix knows. It is a versioned contract for one business action, with enough context to validate, reject, create, acknowledge, amend and reconcile the intended order.

identity

Configuration, project, quote, cart, order, order-line and downstream-system identifiers

revision

Product model, rules, configuration, price, quote, terms and order revision or version

parties

Customer, account, dealer, salesperson, legal entity, market, delivery and billing context

product

Product family, model, variant, selected options, dimensions, derived values and readable summary

lines

Commercial line type, item reference, quantity, unit, parent-child relationship and fulfilment meaning

price

Currency, list, account, option, service, discount, tax, freight, deposit, total and validity context

acceptance

Customer decision, signer or actor, timestamp, terms, approval, payment and technical-review status

delivery

Requested date, site, fulfilment method, survey, installation, package, shipment or production context

control

Correlation, idempotency, event, state, reason, retry, acknowledgement and reconciliation fields

evidence

Snapshot, document, audit actor, source revision, exception, cancellation and supersession references

Configuration-to-order lifecycle

Make every commitment, validation and acknowledgement observable.

1

Configure

Create a valid saved project with stable product choices, dimensions, calculated values and revision identity.

2

Price

Resolve the accepted currency, account, discount, service, tax and validity context without losing calculation evidence.

3

Approve

Capture customer acceptance plus any margin, credit, technical, dealer or internal approvals required by policy.

4

Prepare order

Transform one accepted revision into the expected header, lines, relationships, documents and delivery context.

5

Validate downstream

Check customer, items, quantities, units, price, credit, tax, availability, dates and required references.

6

Create and acknowledge

Create exactly one intended operational order and store the authoritative external ID and state.

7

Fulfil and communicate

Return useful released, scheduled, produced, shipped, installed, blocked or cancelled status by scope.

8

Change and reconcile

Control amendments, cancellations, replacements and drift between the accepted configuration and live order.

Order models

One Configurix product model can support very different order outcomes.

Standard catalogue order

A valid configuration resolves to established items and services. The order still preserves the configuration ID and human-readable summary.

Control: Dropping the configuration because a sellable SKU exists can remove option, visualisation and approval evidence.

Made-to-order project

Dimensions and options create an order-specific commercial structure, with operational mapping completed by ERP or a governed service.

Control: A free-text description is not a controlled substitute for dimensions, units, revision and validated derived values.

Configure-to-order assembly

Approved choices resolve modules, components or order lines under a controlled product model and accepted downstream mapping.

Control: A sales BOM, configured order and manufacturing BOM have different meanings and should not be treated as identical exports.

Engineer-to-order request

The accepted commercial project initiates engineering review, variant creation or a technical release before operational execution.

Control: Customer acceptance must not bypass required engineering, safety, compliance or production approval.

Dealer or wholesale order

The order uses account products, buy and sell prices, discount authority, delivery addresses and dealer-customer relationships.

Control: Tenant, account and price-list isolation must be enforced in data access and downstream payloads, not only in the interface.

Installed-project order

Product, survey, delivery, installation, permits, services and milestones remain connected to the same accepted project.

Control: The requested product date, installation date and production release are separate commitments that need explicit ownership.

Integration patterns

Choose the order path that matches the real commercial and fulfilment authority.

ERP-owned sales order

ERP already owns customer, item, commercial, planning, delivery and invoice processes.

Configurix acceptance → validated configured-order request → ERP sales order → acknowledgement

Control: Use stable correlation and idempotency so retries create or update one intended ERP order.

Commerce-owned checkout

The product is sold online and checkout, payment, customer tax and order communication live in ecommerce.

Configurix project → cart or draft order → checkout → ecommerce order → ERP or fulfilment

Control: Keep the configuration revision connected to the order and use the current supported platform API.

OMS-orchestrated order

Orders enter from several channels or require provider, fulfilment-source and exception coordination.

Channel order → OMS validation and policy → ERP, warehouse, partner or installation provider

Control: Define which system owns order state and how provider events converge after delay or failure.

Quote-to-order approval

A salesperson or dealer needs technical, margin, credit or customer approval before order release.

Accepted quote → approval policy → order preparation → downstream validation and creation

Control: Record the exact accepted quote and configuration; reject changed price or product revisions.

Event-driven handoff

Acceptance events start asynchronous validation, enrichment and order creation without slowing the customer interface.

Acceptance event → queue or integration service → order API → durable acknowledgement

Control: Design for duplicate, delayed, reordered and failed events plus scheduled reconciliation.

Managed B2B document exchange

Trading partners require a reviewed EDI, XML, CSV or other business-document contract.

Configured order → approved business document → partner acknowledgement → status exchange

Control: Map party, location, item, unit, code-list and document identities to the chosen standard and partner profile.

Revision and amendment policy

Never let a later edit rewrite what the customer accepted.

A change policy explains what happens before and after quote acceptance, order creation and operational release. It protects the customer decision while giving sales and operations a controlled path to correct or amend real projects.

Before acceptance

A new draft revision can replace the previous draft while the accepted history remains empty.

After quote acceptance

Any product, quantity, price, term or delivery change creates a visible amendment decision.

After order creation

The downstream authority decides whether to update, hold, cancel, replace or reject the requested change.

After fulfilment release

Production, procurement, shipment or installation impact is reviewed before a new revision proceeds.

After partial completion

Completed and remaining quantities, costs, documents and customer communication are handled explicitly.

After cancellation

The cancelled order and configuration remain historical evidence; a reorder receives new identity.

Implementation blueprint

Start with one accepted product and one real order path.

01

Name the commercial commitment

Define whether acceptance means quote signature, purchase order, checkout, deposit, internal approval or another event.

02

Map system authority

Assign customer, account, product, configuration, price, tax, credit, order, fulfilment and invoice fields to one owner.

03

Choose representative fixtures

Use normal, minimum, maximum, option-heavy, dealer-priced, revised, invalid and technical-review projects.

04

Design the configured-order contract

Specify identities, revisions, lines, units, prices, approvals, delivery fields, documents and error reasons.

05

Implement safe transformation

Validate accepted state, map deterministic values and prevent stale, incomplete or duplicate requests.

06

Prove downstream behavior

Verify the actual ERP, ecommerce or OMS order, not only the request payload or successful HTTP status.

07

Test change and recovery

Cover amendment, cancellation, retry, provider outage, rejection, partial fulfilment and later reconciliation.

08

Operate with evidence

Monitor latency, rejections, duplicates, unmatched orders, stale revisions and ownership of every failed record.

Security and commercial control

Protect customers, prices and orders at every boundary.

  • Authorize customer, dealer, salesperson, approver, administrator and service identities separately.
  • Enforce account, tenant, market, project, price-list and order access at the data and API boundary.
  • Use least-privilege service credentials, environment separation, secret rotation and controlled scopes.
  • Minimize personal and payment data; use the responsible payment provider rather than copying sensitive card fields.
  • Validate every external customer, item, price, quantity, unit, address, tax, discount and status field.
  • Authenticate events and webhooks; defend against replay, duplicates, reordering and forged acknowledgements.
  • Keep audit events for acceptance, approval, order creation, change, cancellation and privileged administration.
  • Define retention, deletion, backup, recovery and incident responsibilities across every connected system.

Acceptance evidence

Test the resulting order, not only the integration call.

  1. 1One accepted configuration creates exactly one intended downstream order with one recorded external identity.
  2. 2A draft, expired, invalid, technically pending or commercially rejected revision cannot create an order.
  3. 3Minimum, maximum and option-heavy valid products create the expected header, line, quantity, unit and relationship structure.
  4. 4List, account, option, service, discount, tax, freight, deposit and total values match the approved commercial context.
  5. 5A timeout, retry or repeated acceptance event does not create duplicate orders, lines, deposits or customer communication.
  6. 6A downstream validation failure returns a usable reason and leaves the Configurix project in an honest recoverable state.
  7. 7Customer, dealer, salesperson and service identities can access only the permitted projects, accounts, prices and orders.
  8. 8A later configuration revision does not silently change the accepted quote or operational order.
  9. 9An authorised amendment updates, holds, cancels or replaces the correct downstream record according to policy.
  10. 10Fulfilment, production, shipment or installation status is attached to the correct order and project without overwriting history.
  11. 11Partial fulfilment, cancellation, return or credit preserves quantities, reasons and related financial or operational references.
  12. 12Reconciliation detects missing, extra, stale, rejected and mismatched records across Configurix and every order authority.

Failure patterns

Where configuration-to-order projects create false confidence.

The quote PDF becomes the order integration

A document can support human review, but it is not a complete structured contract for identity, lines, revisions and acknowledgement.

A draft configuration creates a live order

Exploration or an autosaved project crosses the commercial boundary without explicit acceptance and approval.

Every selection becomes an unrelated line

Parent-child structure, quantity logic, services and product meaning are lost in a flat list.

The API returned success

The order can still contain the wrong customer, revision, price, unit, item, date or fulfilment state.

Retries create duplicates

No stable request, correlation or idempotency identity exists across timeouts and redelivery.

Changes overwrite acceptance

The original customer decision and historical order become impossible to reproduce.

Status has several owners

Configurix, ecommerce, ERP and OMS each display a different truth with no reconciliation rule.

Errors disappear into middleware

Sales and operations cannot see who owns the rejected order or what evidence is needed to recover it.