Hey everyone, I’m going to be going through the thread and responding to every post, and we’re working on some docs right now to clarify some of the more complex issues in more detail. I’ll update the main post once we’ve got some more detailed content for you.
I’ve got a couple of responses started, I’ll post these for now while we work on the other content. We’re definitely listening.
Good question. A good rule of thumb is : If it can be stored in a structured way on the Customer object, then it should be stored there to make it available in the merchant’s admin. There’s a doc that details this here. We don’t want to be in a place where all of the data on a merchant’s leads are exclusively controlled by someone other than the merchant.
We are generally open to changing things if you have specific concerns around any of the policy changes. If you feel like a few of these points have really hurt you, then post some details so that we can make sure we’re not missing anything.
This definitely makes sense to us, and is the reason that we explicitly call out the fact that there are exceptions in the TOS. First and foremost, we want to deliver value to merchants. That being said, there are a lot of poor checkout experiences. We’re working really hard on ways to solve this problem at scale. Documentation is incoming.
If you’re an app that’s collecting data on the storefront, there’s a chance the merchant can’t access their customer data unless they go through your service. We want merchants to be able to access this data through the admin. If you’re just interacting with the Customer resource through the Admin API, you don’t need to worry about this change.