Thanks for the note, Bernadette. I would have liked to vote for an existing request, not start a new one. This is an important request. It may not be high-volume, but what it lacks in volume it more than makes up in desirability, to my mind.
There must be a critical threshhold of votes where it makes sense to put it on your implementation schedule. Archiving it prevents that threshhold from ever being reached, due to a low *rate* of votes.
Think of it like seat belts. It wasn't the most highly requested feature so automotive marketing didn't see a need for it. And it added cost, so manufacturing was against it. Only when it was mandated, and it started saving lives, did anyone other than a knowledgeable view recognize its value.
I'm all for customer responsiveness. But being "market driven" is not the end-all and be-all. You need the right balance of implementation driven (what's possible), market driven (what people want) and value driven (what makes your offering worthwhile).
The ability to use Amazon as an order-taking and fulfillment platform is a fairly recent development. It hasn't acquired a ton of steam as yet, but it's growing. The question is, do you want to be ahead of the curve, or racing to catch up?
