Not Taken

Amazon Mapping function for existing listings not created using LL

At the moment you cannot properly map existing Amazon listings not created in LL2 so you are able to change title - description etc - you can only change basic functions - there should be an option to be able to change it all

1 person likes this idea
This is almost impossible or will take too much time to implement.
Further... I consider this to be fundamental requirement and a complete waste off the users time to have them recreate a listing and manually one-by-one add browse nodes to products that are already listed with browse nodes. This is a process for the sake of having a process and it is not even a good process design in the first place. This is a half hearted development and something that EVERY product I have trialed does as standard.
"This is almost impossible or will take too much time to implement." - Be constructive, really. This is not what your customers want to hear. Old fashioned support response.

LW already queries the live stock listed on amazon and their SKUS if it did not it would know to append a number to the SKU.

There is an existing inventory report available at amazon through MWS, it has ALL the information of what is listed and would then allow access to what browse nodes are already in use. Why do you not use this and fast track the listing process? Download -> Auto Pair -> Success -> Manage
If I have an existing product on amazon, when I add the listing to the configurator, the configurator appends a ".1"

If I remove the appended ".1" its lists against the existing amazon listing and does not create another AND updates from Linn Works.

Not sure as to why your Linn Live team couldn't tell me after an hour of text exchange.

Stuart wrote:


"If I have an existing product on amazon, when I add the listing to the configurator, the configurator appends a ".1"

If I remove the appended ".1" manually its then lists against the existing amazon listing and does not create another AND updates from Linn Works going forward."


This works for single listings and is the desired behavior.


However,  I cannot seem to get the same process to work for variations

I can add the variation (parent) to the configurator, and I can then review the list of variation skus it will list. 

I see the .1 appended to each sku.  And, I can even remove them.  But, my edits to the sku number wont save.  The Save button that's on the screen does nothing.


Has anyone figured out how to tie to an existing sku?



Login to post a comment