Skip to main content
Completed

Import field for Alias SKUs

Related products:Orders & Shipment Management
  • February 27, 2015
  • 37 replies
  • 11 views

I was really happy to see support for Alias SKUs in the product update today! We have a very large number of these (enough that manually inputting them is nearly impossible) and would love to be able to have them included as a field in the product import. Is this planned?

37 replies

  • March 30, 2015
I was shocked to see this was not possible with product import. This had to have just been overlooked, please fix.

Hi, I would also like this feature. We have a parts store at 2 locations, each having a separate sku system. Because it's a parts store, there are over 20,000 products with skus. I can see the alias field when I download the product, and would be nice to be able to use this to update my product table.

'@Admin any update on this feature request? I have lots of sku aliases I'd like to upload.

  • March 18, 2016
Hey @Daniel - At the moment, you're only able to export a read-only view of your aliases and we currently don't have any updates here. Can you tell me more about your aliases and why there are so many?

I would also like to add my support behind this request. We are a toy parts store (K'NEX, LEGO, etc), and each part is listed in multiple websites that have their own sku system (as we have one ourselves). Right now, we have 20,000 items. I either have to update each item (way to long), or export 20,000 items out of each channel, and import them into ShipStation. I chose the 2nd option due to time constraints, which creates 40,000 skus.

  • March 22, 2016
THIS IS A MUST ADD!

  • May 24, 2016
PLEASE ADD THE FEATURE TO IMPORT SKU ALIAS's IN BULK!

please have the feature activated asap. it will be a great help as we have thousands of sku alias thanks

  • June 29, 2016
Guys, There is obviously a lot of need for this for functionality for all a lot of retailers. It's not much work as far as development and coding. Please implement ASAP. Like this month. PLEASE

  • July 27, 2016
Need this feature Urgently

  • August 18, 2016
Also need to allow the same Alias SKU across multiple products to map different versions of the same product to one SKU for reporting purposes.

  • September 7, 2016
Please add! This is a huge barrier for us currently.

  • September 26, 2016
Need this feature Urgently it doesn't help anything that you could click “Combine” from the Products page, we have over 20,000 products, and each part is listed in multiple websites that have their own sku system, as we have one ourselves, it's impossible to update each item, especially it doesn't have allways the same product name, so i cant search it in the product quicksearch

  • October 12, 2016
Need this feature Urgently..

  • October 28, 2016
'@ShipStation - Any update on this?

With the amount of aliases for every product we have it's almost impossible to combine the alias to the main sku manually. I think it's basically a must to have the alias field and also the store the aliases belong to when in the .csv import so we don't have to spend 1 week just to manually combining the aliases.

  • April 17, 2017
I am so glad to see this is getting attention. We need this so badly! Please keep us updated.

  • June 19, 2017
I need this feature because many marketplaces such as Amazon don't allow you to fix SKUs without deleting the product listing (and deleting therefore the product reviews and sales history).

  • July 5, 2017
Looks like people have been asking for this for 2 years, and rightfully so. How hard is it to add a couple more columns on the CSV import? This is a horrible waste of time. I have to pay someone to sit here and add aliases one at a time manually when this could be done in one minute via CSV. I dont understand the reasoning behind this. This is such an easy fix.

We sell on multiple sales channels and, in addition to that, we sell the same item under different SKUs on some of the channels (as it seems many others do). The ability to bulk upload alias SKUs would save days, if not weeks, worth of time. Creating the SKUs manually is actually forcing us to find other workarounds instead of doing this as we simply do not have the time.

  • September 7, 2017
Same as many others, it would be very useful for us to have the ability to batch import sku aliases. We already have our warehouse software working with our listing software to update our "sku aliases" across multiple channels, and are able to remove the inventory the same way when orders are imported from Shipstation, so when our warehouse does picking using that software, they are instructed to pick the correct item, however this can still make it very confusing at times when our barcode scanners are telling the picker to pick a particular item and our packing slips that we are shipping with (printed from Shipstation), don't always have the same sku... This is the last piece to our process where a physical products inventory can go out and be listed under different sku's, on different channels, and have sales coming back referencing 1 physical unique id (without the manual process of entering every alias 1 by 1). Looking forward to seeing if this goes anywhere... I hope that as this has been in review since 2015... that there may be an update before another 2 years pass?? :)

  • October 9, 2017
any update?? still desperately needed!!!

We are trying to add our all products into Shipstation and want to manage inventory from there only. So we just want to know is there any possibility we can add our alias SKUs in bulk with the real Skus as we have 3 different account of a marketplace and have different Skus. Please help us in this as it would be very tought to add alias Skus individually.

  • January 16, 2018
Thanks for checking in on this. We’re still interested in importing alias SKUs, and we don’t have a timeline on it. It isn’t on our immediate roadmap but it’s one we’d like to keep open for now.

We noticed 1500+ alias sku's with a typo. I really do not want to go into 1500 and manually change 1 character.. Please implement a feature to resolve this issue!