Start a new topic
Answered

SKU updates - best practices

We have a customer with a shopify connection that is planning to update their product SKUs in shopify soon, (from COMFY-BLK to COMFYBLKDTC for example). We have MANY orders already imported into Infoplus from shopify and more landing everyday that use the original SKU.


We are looking for what our best option would be to handle this change:


1. setting up supplements

2. change control number feature (IPC menu 5/option 12)

3. building new sku's

4. Possible for support to update existing SKUs in Infoplus to match new shopify SKUs?

We currently have almost 14000 orders in Infoplus and new orders are being passed daily from Shopify using the current sku.

After we process and ship orders from the container arriving on Monday we will still have 10,000+ orders in the system.

We need to understand the ramifications of changes we make in Infoplus and how that will pass data back to Shopify.

ie. if we setup a supplement how will Shopify process that data when we send tracking back? One sku was ordered but another was shipped.

If we build the news sku's now ask the customer to update the sku's now in Shopify all future orders will have the correct new sku but we will need to update all orders pending in Infoplus.


Best Answer

We recommend changing attributes on the existing SKUs, and not necessarily creating new SKUs--that will mess with the mappings on the SCC side of things.


What's the reasoning behind wanting to change the SKU names? We recommend NOT doing this. Supplements are fine, but, again, this isn't ideal for long term use (more issues tend to rise up with supplements). The control number feature suggestion isn't recommended, either.


We're looking for a solid rationale behind why the SKU names are changing, and why the client wants that. We don't think that's a good idea.

Let me know what you think.

1 Comment

Answer

We recommend changing attributes on the existing SKUs, and not necessarily creating new SKUs--that will mess with the mappings on the SCC side of things.


What's the reasoning behind wanting to change the SKU names? We recommend NOT doing this. Supplements are fine, but, again, this isn't ideal for long term use (more issues tend to rise up with supplements). The control number feature suggestion isn't recommended, either.


We're looking for a solid rationale behind why the SKU names are changing, and why the client wants that. We don't think that's a good idea.

Let me know what you think.

Login or Signup to post a comment