Skip to main content

One configurator or several?

Question​

> We sell several very different products. Should we include them all in a single configurator, or create a separate configurator for each product?

Answer​

Both options work. The decision depends on how much your products have in common.

Rule of thumb: The fewer things two products share—steps, features, rules, pricing logic—the more they should be placed in separate configurators.

When Separate Configurators Are Worth It​

  • The products have hardly any features in common. In a single configurator, you’d have to constantly use rules to hide half of all the steps.
  • The configurator has grown so large that even you are losing track of it. Fewer features and fewer rules mean fewer places where errors can occur.
  • The products are offered in different sections of your website or in different store categories.
  • Different people on your team manage different products.

Arguments Against It​

  • Duplicate maintenance. You have to maintain everything both products have in common twice: a shared color palette, the shipping cost logic, the ordering process, and the design. You have to make each change individually in every configurator.
  • Licensing costs. Each configurator is billed separately. You can find details on this under Wie buche ich den K3?.
  • No automatic synchronization. There is no link between the two configurators. Changes made in one remain unchanged in the other.

The Middle Ground​

Before splitting things up, check whether you can achieve clarity within a single configurator:

This keeps a configurator manageable even with many variants—as long as the products share the same core structure.

Split only when it becomes a problem

Splitting can be done later; merging is the more time-consuming approach. If you’re unsure, start with a single configurator and split it up as soon as the rules become confusing.

Further Information​

  • Modifying a configurator
  • Connecting multiple configurators to the same store