Disclaimer work at AWS.
Customer disputes? Returns? Presumably you'll need some sort of history. At the very least saying Person X bought Y product
Customer disputes? Returns? Presumably you'll need some sort of history. At the very least saying Person X bought Y product
Alternatively a proper secrecy management system that allows customers/vendors to expose particular data to Amazon for those purposes without handing everything and the kitchen sink over, with fine-grained controls.
As a consumer, would you really trust a merchant that opted out of Amazon’s return policy? It’s already to the point where I filter on Amazon Prime eligible and if possible sold and shipped by Amazon.
On some purchases I would, I mean this is basically like an ebay purchase with no return policy.
Point being, is there a technical argument against giving the vendor/consumer control over this, as long as the nature of the sale is transparent? I don't think so.
And even if you're saying that's too free-wheeling there's point two. Keeping only a track record of the data for the return period and only making it accessible if a customer demands a refund is technically possible.
The anti-competitive /privacy breaching data-processing that is the topic of the thread can be completely avoided.
> On some purchases I would, I mean this is basically like an ebay purchase with no return policy.
Not at all. eBay’s money back guarantee overrides any seller policies. You can definitely return eBay items that are sold as “no returns”, if they are defective, counterfeit, etc.
Why do you need aggregated sales data for these use cases? Presumably bad internal actors aren't going through order history records one at a time and pasting into Excel! This problem could only exist if you could query large amounts of sales records. Cynically I suspect Amazon has tooling specifically to identify lucrative products.