An “embarrassing and ham-fisted” error…
Yes, that’s what the folks at Amazon are saying now about the mess that their cataloging system became over the weekend.
What they aren’t doing is explaining how the error came to pass, nor are they apologising for it.
From “glitch” to “cataloging error” that affected 57,310 books is a pretty big leap.
Thank heavens for citizen journalism… since it seems the most plausible explanation of all comes from a former employee (Mike Daisey, also a writer, who has written a rather popular book about his years working for Amazon). The tl;dr version goes like this: an employee at Amazon.fr mistakenly enabled the “adult” filter (reserved for things like sex toys, to keep them from popping up on innocent, unrelated front page searches) on a whole bunch of books. It would seem there was some confusion in that employees mind between the way Amazon mean the tag “adult” (read: sex toys and pr0n) and the employee’s understanding of it (read: anything intended for an adult audience) (although “Heather has Two Mommies” is a picture book for kids, it had the identifying tag “LGBT” which got swept up in the (overzealous? daft? censorious?) employee’s “adult” ranking). The system them automagically categorised all books with any of the tags the employee flipped the switch on as “adult” and removed them from searches, also hiding (but not deleting) their sales ranks.
This problem only became visible on Amazon sites that have “safe search” protection built in to them – the German Amazon site has no such thing and its listings were unaffected. The US and UK sites do have this protection, and thus the twitterati were soon able to compile a partial list of titles affected. This added fuel to the “omg censorship!” fire, and led to Amazon calling in staff to deal with a problem with the highest internally ranked severity code they have.
For an inside look at Amazon’s in-house reponse, look here. And check out Lilith Saintcrow’s blog for the nitty-gritty here.
One of the most interesting parts is that the employee who messed up is identified as a CS rep. A customer service rep? A customer service rep with enough access to the cataloging and database code to cause a shitstorm like this? Really, Amazon, really? (It’s not that I don’t believe it, but that I think it’s insane that a bottom rung employee can be granted enough access to the framework of the global site template to make a mess like this. CSRs (and I know because I was one) are not always the brightest bulbs in the lighting-rig. They should have sod all access to the sites global directory, let alone category-switching access on a global level).
The other part, that made me giggle, is the acknowledgement in there that Amazon hide sales rankings on pr0n and sex toys in some countries. They do not want you to know how many people buy butt-plugs and dildos (to use the two most often cited examples) from them. Prurient, silly and rather amusing.
A lot of people are saying that this doesn’t explain emails sent to people like Mark R. Probst, some of them sent as far back as February – but I think that was a result of what the hacker claimed to have exploited – a couple of people tagged his book as “adult” and some flesh-and-blood person agreed with them, and manually switched that listing. It would also explain why it took them so long to switch it back, since someone possibly had to read the book to determine it was un-deserving of the adult tag.
My hope is that this teaches Amazon to vastly restrict their employees’ access to the cataloging system so this does not happen again.
And another thing, yes Amazon, you are a hella big company – but in all of this mess, and your subsequent statements, you have forgotten to use a very important word. That word is: “sorry”. I’d advise you incorporate that word into your next statement post-haste.
No-one is too big to have to apologise.


Recent Comments