Broadleaf Commerce Discussion Forums

Hi,

In the demo (1.5M1), it seems that there is only product adminstration and no sku adminstration.
Do you have to create one product for one sku ?

That's strange because the sku notion exists in your model and it existed in the previous version of the broadleaf admin.

Is it planned in the next release ?

Karim

In the 1.5 data model, we have introduced a one-to-one relationship between product and sku (which is the way most customers think of their catalog). As a result, when you administer products in the new admin, you are implicitly administering skus as well behind the scenes.

This one-to-one relationship is in addition to the many-to-many relationship that already exists (this is what you're referring to). We're planning an additional/optional tab for the admin that will allow separate administration of the sku from the product, which would allow multiple skus per product. This would be a tab that is configured to be active for customers whose catalog model demands the additional product/sku relationship complexity.

Thanks a lot for your pertinent answer.

We're planning an additional/optional tab for the admin that will allow separate administration of the sku from the product, which would allow multiple skus per product.

Do you have any idea in which version it will be planned/developed or released ? (is there a broadleaf's public roadmap )
In my opinion (and customers I know), this missing administration feature is essential to manage easily big or complex catalogs ...

It hasn't been directly on my radar, as we've been crunching on the major features for this release. I'll add it as tentative to our JIRA list of features for 1.5. If it doesn't make it in 1.5 GA, then it will be available shortly thereafter.

http://www.broadleafcommerce.org/jira/browse/BLC-83

Thanks again ! I hope somebody will take care of this Jira
By the way, for guys looking for project's roadmap

karim.hj wrote: (is there a broadleaf's public roadmap )

http://www.broadleafcommerce.org/jira/browse/BLC#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel

One to one between product and sku seems good, but then there should be some sort of "grouped product" or "composite product" types. For instance if I have one product model with different sizes, then I'd need to create new product/sku for each size, if I add a "color" attribute, then I need to create different combinations for each attribute. This has to be handled automatically somehow. I hope this new tab in admin addresses this.

Evaldas Taroza