Can you launch a configurator before your BOM is ready?
Plan a phased configurator launch when material data is incomplete, separating visual enquiries, quotations and approved factory outputs.
Table of contents
A configurator can support visual selection and structured enquiries before a complete BOM is available, provided the output is not presented as production-ready. Decide which decisions are reliable today and which still require manual review. A phased launch should make those limits operationally clear.
Choose a useful first output
Your first phase might collect model, dimensions, finish and accessories for a salesperson. Another phase might prepare a controlled commercial offer after review. Automatic material quantities and factory integration can follow when their source data and acceptance examples are ready.
Do not call all three phases the same completed product. Sales needs to know whether a record is an enquiry, an issued offer or an approved manufacturing request.
| Phase | Minimum evidence |
|---|---|
| Visual enquiry | Identifiable selected product and unknown inputs |
| Commercial offer | Verified pricing basis and agreed scope |
| Material preparation | Reviewed component references, quantities and units |
| Factory handoff | Approved configuration and receiving-system acceptance |
Identify what is missing from the material definition
A product may have a reliable frame formula but incomplete accessory kits. Another may have component identities without quantity rules. Record these gaps separately. A generic statement that “the BOM needs work” makes it difficult to assign owners and plan a useful release.
Ask manufacturing to provide one accepted material list for a representative configuration. Use it to test the mapping from selected options to required components. Investigate differences before expanding the automated output.
Prevent a preliminary record becoming an order instruction
Document who reviews a configuration and what must be complete before production receives it. The application should retain the selected revision and the unresolved questions. A salesperson copying an attractive image into an email should not accidentally bypass the factory's approval process.
If material preparation remains manual, preserve the link between the reviewed list and the saved configuration. Later automation can then be checked against the same product decisions instead of a disconnected spreadsheet.
Plan the Configurix implementation in deliberate stages
A Configurix BOM workstream can be scoped alongside customer configuration, custom quotation software and factory connections. Ask for a staged proposal showing the data required for each output and the conditions for moving to the next phase.
Is a visual-only first phase wasted work?
Not when it solves a real enquiry problem and uses product identities suitable for the roadmap. Confirm which data and models can be retained in later phases.
Can the software infer every missing component from the image?
Do not rely on that assumption. Manufacturing requirements need explicit product data and reviewed rules, including components that customers never see.
Book a private Configurix demo
Bring your product range, price list and a representative quote. We can define the configuration and sales workflow around your business.
Book a private Configurix demo →Related articles

Can a configurator run in your company's cloud account?
Evaluate company-owned hosting for a configurator by assigning deployment, monitoring, backups, access, incident response and integration responsibilities.

What maintenance is needed when products change every week?
Specify configurator maintenance for frequent catalogue changes, distinguishing editable data, application changes, tests and emergency corrections.

How do you know configurator enquiries are reaching sales?
Specify durable enquiry records, delivery status, ownership and recovery so a missed notification does not become a lost configurator opportunity.

What should a configurator proof of concept prove?
Define a configurator proof of concept around a risky rule, saved revision and receiving-system output, with clear pass conditions.
