Since I just had a new release I’ve been all up in Amazon’s business this week. And figured I’d mention a few things I’d run into while I was there.
First, if you publish in print they’ve added new markets for the Netherlands, Sweden, and Poland. I think the Netherlands one has been there for a bit and was actually announced but the Sweden and Poland were new to me.
I mention this because if you care about pretty-looking prices you’ll probably want to go in and update those prices. If you don’t they default to Amazon’s conversion of your USD price to that currency.
Which, I should note, also occurs with ebook prices where you don’t set the price yourself. Even if it looks pretty when you publish the book, if you want that price to stay fixed, then you need to manually change it so that it is not based on the USD price or it may adjust on you later with no notice.
(I believe. This based on going in a few times and thinking, “where did that price come from” and then realizing that the price was one that was based on my USD price and they must’ve updated their exchange rates.)
This is also a good time to note that the default exchange rate they use for some countries is not a dollar to dollar exchange rate. In India, for example, when they convert your USD price to INR they do it so that it’s much cheaper in INR than a straight conversion rate would give you.
Which, maybe that’s good in that market? Maybe it results in more sales?
For me, I like to keep it close to even across countries. So that someone pays the same here as they would elsewhere and vice versa. Only exception to that is New Zealand where I use the AUD price so price cheaper there.
So today, for example, $4.99 USD is 4.05 GBP which I would list as 3.99 GBP.
Of course, Amazon artificially caps the pricing in Canada and Australia these days if you’re at the upper end of their 70% payout range ($9.99 USD) so at that price point it’s impossible to get them equivalent anyway.
I do what I can and then I remember the serenity prayer and move on.
The other thing I wanted to mention is that I finally saw the Quality Issues Dashboard. I’d heard people mention it, but never seen it before.
This time when I logged into my account there was a little message asking if I wanted to see it. I thought, “Oh no, I have a quality issue” and clicked on the link.
Here’s where it gets absurd.
While I was re-reading the cozies I found a place where I had said “zip code” instead of “area code” and I corrected that mistake when I uploaded my new files.
The quality dashboard showed me that the issue had been resolved.
Never told me it existed in the first place, but told me it was now resolved.
Which means at some point a reader reported that error, Amazon never told me about it, I caught it myself and updated the file, and then Amazon let me see the quality dashboard and the fact that I’d addressed it.
No other quality issues showing. But who knows? Maybe I have to find and correct them and then magically Amazon will reveal to me that they were already reported two years ago? Although it doesn’t actually tell you when the issue was reported, so no way to know how long that was hiding away unbeknownst to me.
Which is why, really, it’s best to shoot an email to the author if you want an error addressed.
Although…Make sure it is an error and not just “I would like you to phrase this my way” which I have heard of authors receiving in the past.
(Also, understand that for trade-published authors it may never get fixed. And for my books published through IngramSpark, unless it’s a life-threatening error of some sort or half the book is missing, those won’t get fixed either.)
This was in fact a legit error that I was happy to correct when I saw it.
I just never knew about it until now. And when I did find it I was like, “Well, no one has pointed it out to me yet, so must not have been that big a deal to anyone.”
Except…They had, I just didn’t know.
Oh well. Better that than the “we will shut down your account if you don’t address this error that’s not an error” message some have received.