If you wish to do SKU Mapping for your Amazon products, you will need to let Support know so that they can enable this on your ChannelGrabber account. This feature does not cost any extra, but it is not automatically enabled on any accounts.
SKU Mapping is a process that allows you to merge one Amazon SKU with another, so that ChannelGrabber can manage them both as one product.
It is only possible to map an Amazon SKU to another single SKU and not a variation SKU.
This does not change any SKUs on Amazon, it simply allows ChannelGrabber to stock-manage them accurately.
SKU Mapping is not designed for eBay or webstore SKUs, as these can usually be changed on the channels directly, so should not need to be mapped.
- First you will need to prepare a SKU Mapping file in a spreadsheet. You will just need one column with the header as “Original SKU” for the original Amazon SKU and a second column with the header as “Master SKU” for the SKU that you want the original SKU to merge with:
In this example, we have three products in ChannelGrabber. We want to map two of the products to a third product. SKUs “SKU-123-4567” and “SKU-123-9876” are being mapped to the third SKU “Master-123-1234”.
2. You must never map a SKU to itself! If the Master SKU exists in the Original SKU column, then either remove it, or just leave the master SKU column blank in that row:
All the SKUs that are involved in the mapping process, including the new Master SKU, must exist in ChannelGrabber before you run the SKU Mapping process. If the master SKU does not exist, then the original SKUs will have nothing to be mapped to so will remain as separate products.
3. Once you have completed your SKU Mapping file, you will need to save it in “CSV (Comma Delimited)” format or if you use an Apple Mac, “CSV (Windows Format)”. This is very important, as any other format will not be supported in ChannelGrabber’s Data Exchange:
4. Once you have saved your SKU Mapping file, navigate to the Data Exchange in ChannelGrabber. This can be found in the Products sub-menu:
5. Within the Data Exchange, navigate to the Listings tab on the right, where you will be able to choose and upload your SKU Mapping file:
6. Once your file has finished uploading, you will be presented with rows for data mapping, so that ChannelGrabber knows which column from your spreadsheet to map to which field in ChannelGrabber. First, click the Add Row button to create a second data mapping row (you will only need two rows for SKU Mapping):
Next, from the left hand drop-down menu you can select the column header from your file and in the right hand field, select what you want to map it to. The “Original SKU” column needs to be mapped to the “SKU” field in ChannelGrabber and the “Master SKU” column needs to be mapped to the “Master SKU”:
7. Once your fields have been mapped, you can save this as a template so that you can load it in future instead of doing the data mapping every time you need to import a SKU Mapping file. Click on the Template button on the right then you can enter a name for your data template and save it:
8. You can now click on the Generate button to start ChannelGrabber processing your SKU Mapping file. A progress window will appear at the top of the page to show the total number of rows to be processed and will update as the file goes through to tell you how many have been worked through as it goes along. Once it is finished, it will tell you how many successful rows and how many failed rows (if any) there were in your data:
This completes the SKU Mapping process and all the original SKUs should now be mapped to the Master SKUs. This means that if you click into a product on one of the master SKUs, and go onto the Listings tab, you will be able to see multiple Amazon listings under that one master SKU – showing that the original SKUs have been successfully mapped to the master SKU and the products have all merged into one for accurate stock management. From this point forward, the same stock level will be pushed out to all listings on that SKU (provided your stock management is live in ChannelGrabber of course).
We hope this guide is useful, but if you need further guidance please feel free to contact our Support Team.