Agree generally, but I do wonder why in 2015 this has to be driven manually by humans. I understand we're flexible decision makers, but we're also a significant cost in these sorts of processes. I can appreciate this definitely follows the "do things that don't scale" line.
If there was a standard by which browsers stored payment and delivery details, a little beefed up from what we have now, would that get us part way? And then an endorsed way of interacting with an ordering system that can answer questions by default (no newsletter signup, no insurance, no warranty, default shipping, etc).
Loads of security issues, but we're going to have to solve this sort of thing eventually.
I'm pretty sure Google Chrome has an API hidden away for payment info. Google seems to market it towards ecommerce developers (that's how I found out about it), but I can't find my documentation on it. Plus it's not on track for any sort of standardisations.
If there was a standard by which browsers stored payment and delivery details, a little beefed up from what we have now, would that get us part way? And then an endorsed way of interacting with an ordering system that can answer questions by default (no newsletter signup, no insurance, no warranty, default shipping, etc).
Loads of security issues, but we're going to have to solve this sort of thing eventually.