So, you’re thinking about using a SaaS application?
Software as a Service (SaaS) is revolutionizing the way we do business.
The online marketplace is constantly changing and evolving, and businesses can no longer afford to be
reactive. You have to have a presence on multiple selling platforms and forge a personal
brand that resonates with your customers, all while maintaining the quality of your product.
It’s not easy to keep everything organized and still have time to grow your business, but
third party applications (SaaS applications) can help automate many tasks, saving time and money.
In order to use these applications, you’ll need to integrate your seller’s account with the SaaS application. Of course, there are some concerns when integrating your online business with a third party solution and you should take the time to think about them:
What kind of permissions does Amazon provide third party developers (SaaS applications)?
Amazon allows you to control what permissions your SaaS applications have in the User Permissions area of your Seller Account. When a SaaS application is first integrated, it can only interact with Amazon MWS, which is primarily used for pulling reports. No Seller Sensitive information (e.g., password, billing information, etc.) can be obtained by a third party application.
What should you consider when selecting a third party solution?
Throttle Limits - if you're using multiple third party solutions, this is
something to consider. Amazon sets throttle limits on all seller accounts, i.e.,
the number of reports a seller can pull before they are cut off. For most sellers,
this shouldn't be an issue, but if you're pulling more than 100 reports a day,
then you'll likely be throttled at some point. If your business is report dependent,
then ask the third party solution how many reports they pull per day on average. If
you have one solution pulling 30 and the other pulling 40, then that doesn't leave
many for you to pull.
Seller's Suite has been designed to extract the most amount of data, with the least number of reports. We currently use only 5 reports to provide you daily updates on your orders.
Know what reports they need - some third party solutions have been known for
collecting data from reports that have nothing to do with the underlying service.
Usually, this is due to internal testing of future application features, but it's
still a good idea to know what reports your SaaS application is pulling.
Temporary credentials vs your AMZ credentials - When you sign up for any SaaS application, you will have to also sign up for Amazon MWS. After registering with MWS, you will be provided with your MWS credentials. These are YOUR credentials and YOURS ONLY. Do not provide that information to anyone else. The Amazon User Permissions area allows you to create and provide temporary credentials to each SaaS Application that you use.
Cancelling - if it turns out that the SaaS application just wasn't for your business, most SaaS applications make it easy cancel, but some make it a little less so. Be sure to ask what it takes to cancel your subscription. Also, when you cancel any subscription service who you provided access to your seller account, be sure to revoke their access in the User Permissions area too.
SaaS applications are no longer a "new" thing and they have even become part of the core foundations that many companies (big and small) run on. However, it's still important to understand the implications of integrating your business with another. We hope that you found this article to be insightful and if you have any other questions, don't hesitate to e-mail us at email@example.com