-
- impulsis

-
Total Posts: 3
Joined: 2008-01-16
|
Well, this isn’t a real-life example, but it was specially designed to outline the problems with current configurable product logic.
1. Let’s say we have a toy store. We have four toys on sale: Tiger, Piglet, Donkey and Rabbit. Now we want to present them all as a configurable toy. So, we have two attributes: Fur (long/short) and Ears (long/short). Our toys (simple products) will be configured as follows:
- Tiger - long fur, short ears
- Piglet - short fur, short ears
- Donkey - short fur, long ears
- Rabbit - long fur, long ears
And the configurable product Nice Toy with two attributes to select Fur and Ears.
Now, somebody orders the Nice Toy with long fur and long ears - so, actually he buys a Rabbit. And this is correctly reflected by deducing the Rabbits’ stock - but nowhere else can we see the Rabbit was bought! This makes it quite difficult (if not impossible) to track and fulfill orders.
Then let’s try to remove the Donkey from the Nice Toy’s list of associated products - we’ll see, that customer will be not able to configure Nice Toy for the combination of short fur and long ears anymore, although both short fur and long ears options are still available on their own. This proves, that the actual logic of configurable product is in selling appropriate simple one, not just something with some options selected. So it would be much more reasonable to show the actual simple product everywhere, instead of (or at least along with) the configurable one with selected option values reported.
2. Moreover, let’s say that our toys have different prices. To make things yet more complicated, we’ll price our toys as follows:
- Tiger - $13.95
- Piglet - $17.95
- Donkey - $10.95
- Rabbit - $19.95
But the configurable product completely ignores associated simples’ pricing and has its’ own pricing defined per each single attribute value, not per attribute values combination!. So, to make our Nice Toy be priced correctly to match the prices of associated simple products, we’ll have to solve the system of four linear equations:
{base price} + {long fur} + {short ears} = $13.95
{base price} + {short fur} + {short ears} = $17.95
{base price} + {short fur} + {long ears} = $10.95
{base price} + {long fur} + {long ears} = $19.95
This one is simple, but anybody curious enough could try to solve it on his own and see, how much time this simple exercise will take… to figure out that there is no solution!
In my not so humble opinion, as long as we do sell simple products and not the configurable itself, the configurable one should not have any own pricing at all, totally relying on the underlying simples’ prices. Or at least, this setting should be configurable like it is with bundles’ pricing (fixed/dynamic). Otherwise, we end up being unable to price the configurable product correctly, like in this example.
|