Amazon: Copying Customization Information from ASIN across multiple marketplaces

My custom listings were originally set up in the US Marketplace. When I added Canada and Mexico marketplaces, the ASINs were copied over but not the Customization Information.

This leads to international buyers not being able to customize their product at the time of order.

Is there an easy way to copy my customization information for each ASIN from the US marketplace to the others?

These ASINs were created 2-5 years ago. Perhaps Amazon programming has improved since then.

When you are on the Manage All Inventory page in either CA or MX, do you see the Custom Products link in the Listing Tools menu?

If not, do you have to apply/register for Custom Products for each of those marketplaces?

We were in the pilot program when Amazon was first developing the program so what we see or is available for us might be different. We never had to request to be a part of the program as others have had to do.

If you have that Custom Products link, you might have to link each ASIN as a custom product and create the first template in each marketplace. Once the first template is made (and if it is similar for the ASINs), then you can apply the ASIN to the template.

We do not do CA or MX but just trying to give some thoughts about what we would be looking for if we were trying to do it.

Late reply, but this post shows up when searching ‘how to transfer customization to a new marketplace’ so figured I’d post since I had the same question and found an answer:

I discovered a work-around with the spreadsheets, it’s a bit cumbersome but it’s saved me some time & frustration.. I use it when transferring really complex customization that has 100+ options that have thumbnails, multiple fonts, etc, or if I’ve lost the images etc:

  1. Generate a template in the source marketplace of the listing you want to copy. Save the xlsx file to your computer.
  2. In the target marketplace, search your inventory page for the SKU and press ‘create/edit customization’.
  3. Build just ** the framework ** of the customization from the source. By framework I mean if your listing had 2 text fields, 3 fonts, and 4 colors, you’d rebuild all those options in target marketplace. If you have instructions in the source marketplace, the framework in the target marketplace must have that too - it doesn’t need to match, just write “a” or something so ‘bones’ / framework of the customization matches in both marketplaces.
  4. Generate a template in the target marketplace from the framework listing you just made & save the xlsx to your computer.
  5. Open Source xlsx file, select the entire header row (row 1), copy it, then in a new sheet right click, mouse over the dropdown box ‘Paste Special’ and click T (transpose). This will turn the horizontal header bar across columns into 1 vertical bar that goes vertical.
  6. Repeat the copy & paste & transpose process from step 5 for the Target spreadsheet. The end result will be 2 multi-colored header rows that are vertically side by side.
  7. Now you can scroll down and compare the layout - obvious errors like an extra or missing column will show up as the colors not matching. To fix this you need to insert or delete the column from the template file so both the source & target xlsx files have the exact same layout / number of columns.
  8. Once you’ve fixed the columns/format layout, you can copy row 4 from the Source template into the Target template. This is the step that copies all data from the source marketplace and makes it ready for the target marketplace.
  9. Go to the target marketplace and upload the template you exported from the target marketplace that you just updated.

If you did all the formatting correctly, your target marketplace will have the customization copied from the source marketplace!
Sorry that was so long-winded, the hardest part of copying customization with Amazon’s templates is the formatting doesn’t match between different countries + the header row from the target marketplace has unique ID numbers used to build the template that only exist if you create the framework & export from the target marketplace… If those ID numbers or column format doesn’t match, it’ll be rejected.

I developed this workaround after many, many hours spent rebuilding customization in new marketplaces. Hope this helps anyone finding this in the future!

Thanks for posting your workaround, @Kane - and in the first-post tradition of this forum - Welcome to the SAS!

Great post! … and as @Dogtamer has said Welcome to SAS!