Product attributes and sku

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
12 年 前
Hi All
Please excuse this question from a newbie - I have checked the forums and can't really find a definite answer.

nopCommerce is targeted and clearly capable of being used by even quite a big SME. However, in one key area it appears to be missing something (or I am not seeing it).

For a given product that is available in sizes and colours (variants) there is no support for skus for each variant. For example http://demo.nopcommerce.com/p/7/adidas-womens-supernova-csh-7-running-shoe is available in colour and sizes. In a live situation a store would be hooked upto a back office system, syncing price and/or availability. Since only the  parent http://admin-demo.nopcommerce.com/Admin/ProductVariant/Edit/58 can have a sku, I cannot see how the variants have an sku.

I have seen this in smaller less capable stores, so I am sure I'm missing something.

Thanks in advance.
12 年 前
atl, I found your post interesting as I just posted today a question about the same thing (https://www.nopcommerce.com/boards/t/15837/product-attributes-inventory.aspx). Hopefully we can get a task created for this feature request.
12 年 前
Shawn at nopadmin.com kindly commented the following;

"nopC does support skus on the product variant level – and thusly NopAdmin does as well.  NopAdmin give s you a mechanism to manage your products including the skus.   nopC does not handle the creation of a separate sku at the attribute level however – nopC simply ‘appends’ the attribute description to the product to tell you what the product ordered was and the attributes that were selected.  So if you have a Ladie’s Top for example – that Ladie’s Top may have a sku of top123 at the variaint level.  It may come in S-XL sizes…. nopC does not allow you to assign a sku for top123 and each size, like top123-S, top123-M, etc.   It’s at the variant level."

Note also https://www.nopcommerce.com/p/197/product-attribute-sku-modifiers.aspx which appears to deal with this issue - but this is for 1.90..
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.