What is the secret to get approved as a Private Developer with PII access?
We currently connect to multiple Accounts using MWS to pull orders to ship and then update Inventory an Tracking Information.
I requested to be a Private Developer using SP-API to do the same process using our in house tools. I have connected using Self Authorization and my app is in a draft status. I can pull FBM orders successfully, but then I learned that I need PII Access to get the ShipTo Address for Orders. I have been denied multiple times and each time it doesn’t make sense and no one can provide me details on what I need to do in order to access the same information we are currently puling from MWS API.
What is the secret?
3 replies
Seller_Y7RS9pvWYQkLs
[quote=“Geneva_Pets1, post:1, topic:1375453”]
I have been denied multiple times and each time it doesn’t make sense
[/quote
Before I can comment about your specific case, I need to know the reason given that you were denied. Please quote the reason provided from the email you received. (If you prefer not the post publicly, you can send me a private message on this forum with the text Amazon provided).
I am in touch with many seller API developers. In my experience, if you are requesting access to your own seller account only, you can get PII…IF AND ONLY IF…you are following all of the rules. It is difficult and time consuming to meet all of the rules.
There are seller service providers that you can sign up for, pay, and get your own orders including PII.
(For those who are trying to get PII access to service other sellers, it is very difficult to get approved these days even if you are following all of the rules. The reasons given by Amazon have been like “there is already a public app similar to yours, request denied” or denied with no reason given.)
Dynamic Enterprise Technologies Inc
Seattle Washington USA
Seller_Y7RS9pvWYQkLs
From the above I assume you have one Amazon Seller account with developer access. Using this developer account, it seems you are accessing other Amazon Seller accounts. This means your developer account is authorized for “public” access (aka you have the capability to connect to other Amazon Seller accounts in addition to your own).
I think your developer account cannot be authorized for both “public” and “private” at the same time.
This statement seems to be correct based on the comment in your first post “We currently connect to multiple Accounts using MWS” (assuming “Accounts” means “Amazon Seller Accounts”)
I haven’t seen this denial reason before, but I think Amazon is saying that your Amazon seller developer account cannot be authorized as “private” when you are servicing other Amazon Sellers.
Sadly, it is often difficult to understand the meaning of the Amazon responses when it comes to the developer authorizations.
Dynamic Enterprise Technologies Inc
Seattle Washington USA
