Traditional configurators create every possible product variant individually - and get bogged down in maintenance work. Combeenation flips this approach on its head and thinks in terms of possibilities.
REQUEST NOWCombeenation operates on a simple yet powerful principle: the separation of static data and dynamic interpretation. Customers only need to maintain their product data. The Combeenation Engine handles the complex logic of what happens to which data and when.
Data
Describe the possibilities
All relevant product information is maintained here: features, 3D models, product data, and prices. The data does not describe individual variants, but rather all possible options.
Engine
Real-time interpretation
The engine - the core component - determines how rules are applied in real time, based on the context. A rule can behave differently depending on the situation - for example, offering discounts based on customer group.
Result
Provide suitable options
The result is a customized product configuration that contains only valid options - without the need for manual verification or pre-calculated variants.
The difference: Traditional systems create every possible variant in advance. As modularity increases, this quickly results in millions of individual items. Combeenation, on the other hand, thinks in terms of possibilities, not variants. The specific variant is only created during the configuration process - exactly when it is actually needed. You manage data. Not millions of variants.
All product information is entered here: details such as weight, color, diameter, prices, and discount tiers - as well as 3D models and product images. This data defines what is fundamentally possible. The customer manages this information themselves - once and in one place, rather than individually for each variant.
This is the heart of the system. The engine takes the raw data and decides, based on context and in real time, how rules should be applied. This means a rule can behave differently depending on the situation: Which bill of materials needs to be automatically generated for this specific product configuration? Which pricing rules apply to this customer type? Which components need to be automatically added?
Sound complicated? Don’t worry - Combeenation or one of our partners will handle the setup.
The result is a custom product configurator that shows end users only valid configurations, calculates prices in real time, checks availability, and generates a unique, traceable configuration. The entire system is operated via a custom user interface.
The key difference: possibilities instead of variants
This is the very essence of what makes Combeenation different. Traditional systems are variant-based: every possible combination is created in advance as a separate item. With 25 colors, 17 sizes, 9 control options, 12 motor options, 17 equipment options, and 6 region options, this quickly results in over 4.6 million variants - and each one would have to be maintained, created in the ERP system, and displayed in the shop. As modularity increases, the number of variants explodes. The maintenance effort becomes unsustainable.
Combeenation flips the principle on its head: architecture based on possibilities, not variants. Instead of managing millions of end products, it manages the building blocks and rules from which they can be created. The engine uses these to calculate the currently valid combination in real time. A specific variant is only created when the user configures it - and is only transferred to ERP or the online store when it is actually needed.
The implication is fundamental: you manage data, not millions of combinations. Variants are a result, not a starting point. This makes even highly complex, modular products manageable - without a data explosion or a maintenance nightmare.
The starting point is the data, not the variants. This enables Combeenation to efficiently manage even highly complex product portfolios. Traditional systems, on the other hand, often rely on a variant-based approach.
Let’s take a closer look at the traditional approach used by competitors compared to the Combeenation approach.
Predefined variants
Architecture is based on variations.
Dynamic configuration
Architecture is based on possibilities.
Imagine a product with 27 variants. The load capacity is to be increased from 5 kg to 7 kg.
Data alone does not guarantee good results. What matters is how the engine interprets it in the specific context: Who is currently configuring the system? For which market? Which options have already been selected? All channels access the same data – without the need for duplicate maintenance.
Three typical scenarios illustrate how the same database meets different requirements:
Region
A retailer in Germany needs different options than a retailer in the Czech Republic.
Product ranges, certifications, and delivery options automatically adapt to the respective market - without the need for separate data maintenance or duplicate logic.
Currency
Prices and discount rules adjust automatically based on the market.
Whether in EUR, USD, or CHF: price lists, tiered pricing, and surcharges are applied dynamically based on the selected region or sales situation.
Situation
Technical dependencies are automatically taken into account.
When a specific engine is selected, the system automatically enables compatible wheels, brakes, or towing capacities.
Let’s work together to build a configurator that grows with your product - without you having to manage millions of variants.
REQUEST NOW