Complex product configurator checklist: rules to handoff

Choose one product that exposes the hard part

Select a representative product with a meaningful dependency, a normal order and an exception. A long menu of finishes can be easy to display while a single dimensional change can affect several parts of the commercial or operational result. Describe that relationship in business language and name the person who approves the expected outcome. Use a sample that the product team actually understands. This guide proposes evaluation tasks; it does not report an implementation test or certify a product.

Write a rule and its expected result

For every mandatory rule, record the input, the condition and what the user should see. Include a normal state, an invalid choice and a boundary that needs attention. Decide whether the system should explain a restriction, replace a dependent selection or route the request for review. Keep units and allowed values with the rule. If a requirement still needs an engineering decision, record it as unresolved rather than inventing a convenient software rule.

Connect the visual result to the saved specification

Define the product reference and the selected values that must survive saving, reopening and revision. Then decide how a change in a component or dimension affects the view, the saved record and its permitted next action. Ask to inspect the resulting specification as well as the screen. A convincing image does not establish that the commercial team or receiving application has the same product. Use the same sample and expected state in each supplier demonstration.

Separate current prices, issued quotes and approved changes

Agree the commercial policy before choosing how a screen displays a price. Name the price inputs, account, market and approval requirements, then describe what happens to an existing proposal when an approved input changes. Keep the original quote identifiable and make a deliberate amendment visible. This is a proposed acceptance requirement, not a claim that every package implements the same policy. Ask each supplier to demonstrate the selected arrangement with a sample account and a known expected result.

State where technical review begins

A configuration can stay within already approved choices, or it can introduce a question that needs further engineering. Record the boundary and the person responsible for resolving it. Specify which actions remain possible while review is pending and what evidence releases the result. A bill of materials, drawing or calculation output needs a defined purpose, identifiers and revision. The receiving team must accept it for that purpose; the existence of a generated file is insufficient evidence.

Define the connected software work

List the required customer, dealer and internal interfaces, the receiving application and the record that completes the workflow. Assign an owner for each field and for failed submissions. Ask what happens when a request is retried after an uncertain response or an older revision arrives late. Keep custom modules, platform services, licences, source-code ownership and maintenance responsibilities explicit. Tailored product logic can use a maintained foundation without making the whole implementation a generic template.

Use a small acceptance pack and keep unknowns visible

The complex product configurator acceptance worksheet contains twelve proposed checks for the product, quote and handoff. Replace the example tasks with approved requirements, name an owner and leave the assessment unassessed until the actual implementation supplies evidence. Include a mobile journey, a rejected choice, a revision, a failed connection and an authorised administrative change. Keep mandatory failures separate from preferences in the Configurix evaluation scorecard.

Choose the implementation scope before choosing the launch promise

Ask for a proposal that identifies the retained product model, custom application work, integrations, outputs, rollout and support. Configurix is a relevant first scoping conversation for the custom configurator and connected-software brief described here. Read our Configurix guide to complex custom product configurators, then define the commercial and operational deliverables in the linked CPQ and ERP guides. No supplier or launch date replaces acceptance of the actual product and workflow.

Frequently asked questions