Simple Configurable Products

[sverdier]

Is it planned to add this natively?
http://www.magentocommerce.com/magento-connect/simple-configurable-products.html
With Simple Configurable Products, the price for configurable products is taken directly from the associated simple products rather than the configurable product itself.
Otherwise it is necessary to calculate the difference of price and enter it to the configurable product and this is a very complex management for customers using Magento without ERP.

[magento-team]

There are changes in the product editing interface that should simplify entering configurable information but i'm not sure yet if this new price functionality will be implemented. It is not on our short term roadmap at least.

[FiveDigital]

It would be great if this feature could be implemented since every of our customers asks for this feature.

[mzeis]

Some of our customers also asked for this. Also, if they have to define prices for the associated simple products they don't want to calculate some kind of price difference but just want to enter the price directly. Enabling them to enter the price directly (and not enter the difference) may enhance the usability.

[sverdier]

If you have a configurable product with several simple product (visible on "Catalog, Search") :

Size 1 : 150
Size 2 : 200
Size 3 : 250
...

You must set Configurable product price : 150
Size 1 : 0
Size 2 : 50
Size 3 : 100
...

If you want increase $10 for the product "size 1", all prices must be changed on configurable product and also the price of simple product "size 1" =>
You must set Configurable product price : 160
Size 1 : 0
Size 2 : 60
Size 3 : 110
...

If You want add a product Size 4 for 100$, all prices must be changed on configurable product =>
You must set Configurable product price : 100
Size 1 : 50
Size 2 : 100
Size 3 : 150
Size 4 : 0

If you want set a special price on product simple Size 3 you must change the price of Size 3 on the configurable product and the special price is not display like a special price on the configurable product.

It's very Complicated for customers.
I think the price of a variation product must be the price of a simple product.

[barbazul]

I agree with sverdier for configurables with only one level of
customization. For n > 1 it becomes actually impossible to handle.

Consider a product with sizes A B and colors X Y Z.

The following table is impossible to reproduce for what I understand

A - X $100
A - Y $150
A - Z $200
B - X $200
B - Y $150
B - Z $100
El ago 17, 2013 5:04 PM, "sverdier" notifications@github.com escribió:

If you have a configurable product with several simple product with simple
product visible on "Catalog, Search" :

Size 1 : 150
Size 2 : 200
Size 3 : 250
...

You must set Configurable product price : 150
Size 1 : 0
Size 2 : 50
Size 3 : 100
...

If you want increase $10 for the product "size 1", all prices must be
changed on configurable product and also the price of simple product "size
1" =>
You must set Configurable product price : 160
Size 1 : 0
Size 2 : 60
Size 3 : 110
...

If You want add a product Size 4 for 100$, all prices must be changed on
configurable product =>
You must set Configurable product price : 100
Size 1 : 50
Size 2 : 100
Size 3 : 150
Size 4 : 0

If you want set a special price on product simple Size 3 you must change
the price of Size 3 on the configurable product and the special price is
not display like a special price on the configurable product.

It's very Complicated for customers.
I think the price of a variation product must be the price of a simple
product.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/335#issuecomment-22818727
.

[xyphoid]

This is an interesting case where it's effectively a global configuration setting for Magento - either you want to use magento-style pricing, or SCP-style pricing, and you will be deciding that on an installation-by-installation basis.

Roughly half of our installations use SCP-style pricing so far.

[clockworkgeek]

I agree with sverdier for configurables with only one level of customization. For n > 1 it becomes actually impossible to handle.

See this stackexchange for more examples of multiple attributes causing an impossible situation. Also it mentions that simple-configurable-products is not being updated, making the matter more urgent.

[michaelgrosser]

Now that this has been brought up, I think this is worth some serious consideration on Magento's part. This may not come up often in client interviews for feature requests, but that's probably because their implementation partner is already using SimpleConfigurableProducts.

On nearly every Magento implementation I've worked on, if Configurable Products were being used SimpleConfigurableProducts was installed.

As mentioned above, there are pricing scenarios that are simply impossible to express natively in Magento, and these pricing scenarios are not at all uncommon, especially in the apparel space where items are often configurable by two or more attributes.

Additionally, many clients import pricing from external systems (ERPs, 3PLs, etc), and those systems nearly universally have pricing set on the simple SKU. Trying to build an integration based on attribute-based pricing increases is unmanageable for those clients, which again, are a substantial majority of large scale Magento implementations.

If the pricing of Configurable Products isn't modified in Core Magento 2, the first thing we'll have to do is write our own module to deal with that because of the fact that the native system is only useful for smaller retailers who manage their pricing directly in the admin panel.

[benmarks]

Let's not fail to lose sight on what I believe to be widespread experience that SCP has multiple knock-on effects (and with good reason, as there are assumptions regarding parent-child relationships (esp in Sales module), as well as the view integrations which assume relationships. These issues are multiplied in an EE instance.

That said, @sverdier and @barbazul have salient points. Simple, single-option façades should be intuitive for admins and developers, and matrix pricing scenarios are not uncommon, and should be achievable without massive customization or extension wizardry. I would like to see composite/façade product pricing receive some manner of re-engineering. However, I'm not sure how effective arguing/advocating domain issues is/will be on this forum. Would be great to hear from @piotrekkaminski or others Magento team on this.

[michaelgrosser]

For sure, SCP is by no means perfect. If I re-wrote it I'd probably simplify it greatly to simply carry over the pricing model. So, to clarify, it's only really a similar model I'd like to see worked into the core. Not so much the other behavioral modifications SCP brings to the party.

[CodeMonkey90]

@tanya-soroka Are there any updates on this? (Asking you since you're assigned.)

[tanya-soroka]

Hello
I agree that it is the reasonable changes. I added this request to our Product Creation requirements. As we are focused on the development framework, this feature will be implemented in later features' releases.

[shayW]

Hi Guys
I think that @mzeis gave the clearer description of the problem statement from customer perspective.
it comes down to a simple solution that should be implemented by the Mgento team.
the attribute prices (either entered manually under custom options) CANNOT be associated to the product price (which is being defined at the price folder) moreover these attributes should override the main product price
The user/Administrator should be given the option to update each price of each sub product independently of the "Main price" and set a specific price to be edded from external excel.
for example lets assume a product with main product price =10$ (which will be eqaul to the small size)
medium size will be +10 =20$
Large size will be +20$ = 30$
now lets assume that Admin/store owner like to execute the following prices changes:
small new price 9$
Medium new price 16$
Large new price 17$
sound simple? I would love someone to tach me how to do it... as far as i understand the Magento engine there is no support for that...

[tanya-soroka]

Hello @shayW,
We are going to support it with in the future. It is already planned for the feature's release. I can totally understand the importance of that feature for you, so you are welcome to contribute its implementation as a pull request to Magento 2 code. We really appreciate your interesting in Magento 2 future.