@Evan_MWS: You said: “In regard to desktop applications or software that the seller runs locally, those application do still need to use MWS developer credentials. However, the sellers credentials should be used just in the software and not shared with anyone.”
It would be great if you updated the official acceptable use policy with this information. It is not clear in reading that.
I read the statement in the AUP that says “Never ask for or accept a Seller’s Secret Keys for any purpose” with the understanding that if a desktop application or on-premise application asked for the sellers MWS credentials, that was a violation of the AUP. Now I understand that is not a violation.
In my case, the ERP application is a hybrid, that is, there is a desktop piece, and there is a server piece, that work together. The server piece can be self-hosted on-premise, self-hosted in a cloud server, or hosted by a 3rd party. I assume such an application would qualify as “runs locally” application. In the end, the seller is in control of the database storing the secret key.
When it comes to developing a desktop application, the developer must have a Developer ID with at least access to their own account for testing and development purposes. I had that, but I had not done any development or testing in the last 90 days, so my developer ID got deactivated, and my re-application is pending. So currently I can’t do any development or testing with the application.
I re-applied for a developer ID asking for access to other seller accounts. After reading your remarks, it seems I only needed to access my own account for my desktop application development, because it is OK to have the sellers apply for their own developer ID and then enter their secret key into the “runs locally” application.