The way other Amazon listing software works, is that it uses a completely different API to access those fields - MWS - Amazon Marketplace Web Service - https://developer.amazonservices.com . I am unsure if this might help.
I do now have my own Amazon Associate ID [now called Amazon Affiliates], but the rules for using it seem completely different than they did in the late 90s and early 2000s - one can only use it on websites and mobile applications [and one must provide all websites and apps that will be using the affiliate ID]. I'm a bit weary of putting my ID into the 'Amazon Settings' part of the app, so it still uses the pedia01-20 ID. I do have an active AWS account but they seem to be moving away from access keys and secret keys - I am unsure if I should generate new ones for Bookpedia or keep the current key that is in that setting.
I use Bookpedia to generate a large text file that I upload to Amazon with the books that I sell. The ASIN is the key field that Amazon requires in those uploads - The ISBN field in Bookpedia often contains the 13-digit ISBN which is different than the 10-digit ISBN which is often - but not always - the ASIN.
So for right now after I scan a lot of books, when I go into each record to describe the condition and list my selling price, I also have to copy and paste the ASIN from the Amazon product page. I would like to know if this is a temporary thing with this beta version or if this is going to be how Bookpedia operates from this point forward.
Thanks!
![Smile :)](./images/smilies/icon_smile.gif)