Precisely Enterworks

When setting up a new item, we are able to specify the sizes and various colors associated with that item and the SKU generator will "explode" each size/color combination into individual SKU records, which saves hours of data entry time.  However, if an existing item has a new color added to it, the previously generated SKU records are deleted and the new size/color combinations are created and the previously generated SKU's are recreated with new record numbers.  We don't like an existing SKU record having the SKU ID change after it has been originally created and sent to our ERP with PO's and transactions for the original SKU number.  We have been told that other companies initially create SKU records using the generator but after the initial creation, they use Excel to import newly added colorways to create new SKU records.  This seems like an inefficient workaround whereas the generator could be easily modified to allow existing SKU records to remain without being deleted and recreated, and only create newly added size/color combinations as new SKU records.  I've heard that this is being worked on but haven't head any concrete details.  Are we unique with this problem or are others wrestling with this as well?

------------------------------
Rick Turek | VP of IT
Sundance Catalog | 8019755272
------------------------------

Hi Rick.

We have our ERP create our SKU records; although a SKU generator sounds intriguing. I'm assuming that you are using a more recent version of PIM? I'm not aware of this functionality in 8.2 - the system that we are currently on.

------------------------------
Jonathan Varo | PIM Lead
Fender Musical Instruments | 480-845-5823
------------------------------

Original Message:
Sent: 08-17-2020 14:01
From: Rick Turek
Subject: SKU Generator for New Sizes or Styles

When setting up a new item, we are able to specify the sizes and various colors associated with that item and the SKU generator will "explode" each size/color combination into individual SKU records, which saves hours of data entry time.  However, if an existing item has a new color added to it, the previously generated SKU records are deleted and the new size/color combinations are created and the previously generated SKU's are recreated with new record numbers.  We don't like an existing SKU record having the SKU ID change after it has been originally created and sent to our ERP with PO's and transactions for the original SKU number.  We have been told that other companies initially create SKU records using the generator but after the initial creation, they use Excel to import newly added colorways to create new SKU records.  This seems like an inefficient workaround whereas the generator could be easily modified to allow existing SKU records to remain without being deleted and recreated, and only create newly added size/color combinations as new SKU records.  I've heard that this is being worked on but haven't head any concrete details.  Are we unique with this problem or are others wrestling with this as well?

------------------------------
Rick Turek | VP of IT
Sundance Catalog | 8019755272
------------------------------

I don't know what the "SKU generator" functionality is. We have just started our PIM impl so not fully aware on the product capabilities. My two cents - Your problem is not unique. If a new Color is created for an existing STYle/item then the generator should just create the newly added record for the Color and Size. Does not make sense to delete and recreate for all children (colors & size) for the original parent (Style/item). You are correct, the ERP will not be able to handle this especially if there are open POs and open inventory for the old SKU. Sort of defeats one of the purposes of an MDM system if you loose the visibility of the original SKU.

Btw, how can I get more details on this SKU generator. It does sound intriguing.

------------------------------
Vikram Menda |
lululemon athletica | 2069723204
------------------------------

Original Message:
Sent: 08-17-2020 14:01
From: Rick Turek
Subject: SKU Generator for New Sizes or Styles

When setting up a new item, we are able to specify the sizes and various colors associated with that item and the SKU generator will "explode" each size/color combination into individual SKU records, which saves hours of data entry time.  However, if an existing item has a new color added to it, the previously generated SKU records are deleted and the new size/color combinations are created and the previously generated SKU's are recreated with new record numbers.  We don't like an existing SKU record having the SKU ID change after it has been originally created and sent to our ERP with PO's and transactions for the original SKU number.  We have been told that other companies initially create SKU records using the generator but after the initial creation, they use Excel to import newly added colorways to create new SKU records.  This seems like an inefficient workaround whereas the generator could be easily modified to allow existing SKU records to remain without being deleted and recreated, and only create newly added size/color combinations as new SKU records.  I've heard that this is being worked on but haven't head any concrete details.  Are we unique with this problem or are others wrestling with this as well?

------------------------------
Rick Turek | VP of IT
Sundance Catalog | 8019755272
------------------------------

Vikram,

Please see the document attached to this message for instructions on how to leverage the SKU generation feature in EnterWorks.

Steve Thomas
Solution Architect
Winshuttle

------------------------------
Steven Thomas | Solutions Architect
Winshuttle North America | 720-318-6700
------------------------------

Original Message:
Sent: 09-09-2020 18:29
From: Vikram Menda
Subject: SKU Generator for New Sizes or Styles

I don't know what the "SKU generator" functionality is. We have just started our PIM impl so not fully aware on the product capabilities. My two cents - Your problem is not unique. If a new Color is created for an existing STYle/item then the generator should just create the newly added record for the Color and Size. Does not make sense to delete and recreate for all children (colors & size) for the original parent (Style/item). You are correct, the ERP will not be able to handle this especially if there are open POs and open inventory for the old SKU. Sort of defeats one of the purposes of an MDM system if you loose the visibility of the original SKU.

Btw, how can I get more details on this SKU generator. It does sound intriguing.

------------------------------
Vikram Menda |
lululemon athletica | 2069723204

Original Message:
Sent: 08-17-2020 14:01
From: Rick Turek
Subject: SKU Generator for New Sizes or Styles

When setting up a new item, we are able to specify the sizes and various colors associated with that item and the SKU generator will "explode" each size/color combination into individual SKU records, which saves hours of data entry time.  However, if an existing item has a new color added to it, the previously generated SKU records are deleted and the new size/color combinations are created and the previously generated SKU's are recreated with new record numbers.  We don't like an existing SKU record having the SKU ID change after it has been originally created and sent to our ERP with PO's and transactions for the original SKU number.  We have been told that other companies initially create SKU records using the generator but after the initial creation, they use Excel to import newly added colorways to create new SKU records.  This seems like an inefficient workaround whereas the generator could be easily modified to allow existing SKU records to remain without being deleted and recreated, and only create newly added size/color combinations as new SKU records.  I've heard that this is being worked on but haven't head any concrete details.  Are we unique with this problem or are others wrestling with this as well?

------------------------------
Rick Turek | VP of IT
Sundance Catalog | 8019755272
------------------------------