
Depending on whether the seller made a request to get access to Personally Identifiable Information of its customers, and on other factors, Amazon may require him to fill out a second form about his data protection policy. This commit makes it clear that compliance with Amazon's security standards is not guaranteed if the seller applying for Amazon MWS access keys is hosted on Odoo (SaaS or .sh). Additionally, it adds a section in which the questions asked to Amazon sellers are listed and answered for the Odoo Online and Odoo.sh platforms.
147 lines
7.6 KiB
ReStructuredText
147 lines
7.6 KiB
ReStructuredText
================================
|
|
Apply for Amazon MWS Access Keys
|
|
================================
|
|
|
|
.. _amazon/developer-form:
|
|
|
|
Submit the Amazon MWS Developer Registration and Assessment Form
|
|
================================================================
|
|
|
|
In order to synchronize your Amazon orders with Odoo, Amazon MWS access keys are required.
|
|
They can be obtained by submitting the **Amazon MWS Developer Registration and Assessment form** to
|
|
register as a developer. Once recognized by Amazon as a developer (i.e. you make use of an
|
|
application connecting to MWS), you will be granted Amazon MWS access keys.
|
|
|
|
First, visit the `Amazon Marketplace Web Service documentation
|
|
<http://docs.developer.amazonservices.com/en_US/dev_guide/DG_Registering.html>`_ and follow the
|
|
instructions to register as a developer. Take care to choose the form "I represent a seller
|
|
organization integrating with Amazon MWS for its own selling account only.".
|
|
|
|
Fill out the *Developer Registration and Assessment form* as suggested below and provide your own
|
|
contact information in the **Developer contact information** section. In the **Business use
|
|
information** section, select the correct region of your seller account. For the other sections,
|
|
adapt your responses in accordance with your business case.
|
|
|
|
Give a particular attention to **Merchant Fulfilled Shipping**. It should only be checked if you
|
|
ship your products yourself. You should uncheck it if you sell exclusively with the *Fulfillment by
|
|
Amazon* service. Please note that requesting this function is not recommended if you are hosted on
|
|
*Odoo Online* or *Odoo.sh* as the additional security requirements asked by Amazon may not be met by
|
|
Odoo.
|
|
|
|
.. warning::
|
|
Depending on several factors (your region, whether you checked the **Merchant Fulfilled
|
|
Shipping** function (i.e. you request access to Personally Identifiable Information of your
|
|
customers), etc.), Amazon may request you to fill out a second form before granting you MWS
|
|
access keys. As that form depends on the data protection policy of the region of your seller
|
|
account (e.g. GDPR in Europe), we cannot provide you with a pre-filled form. Instead, the answers
|
|
of questions related to Odoo are listed in the `Answer the Additional Form`_ section.
|
|
|
|
.. tip::
|
|
If you need assistance for your application for Amazon MWS access keys, `submit a support ticket
|
|
to Odoo <https://www.odoo.com/help>`_.
|
|
|
|
.. image:: ./media/dev_form.png
|
|
|
|
Answer the Additional Form
|
|
==========================
|
|
|
|
This section lists all questions asked by Amazon in additional forms. The answers are tailored for
|
|
*Odoo Online* and *Odoo.sh*. If you did not receive any additional form after your :ref:`initial
|
|
application for Amazon MWS keys <amazon/developer-form>`, you may disregard this section.
|
|
|
|
.. warning::
|
|
If you are not hosted on Odoo.com (*online*) or on Odoo.sh, you should adapt the answers related
|
|
to hosting according to your own infrastructure and data protection policy.
|
|
|
|
- **Describe all functionalities in your application where Personally Identifiable Information (e.g.
|
|
customer name, street address, billing address) is required.**
|
|
|
|
► If you did not apply for the *Merchant Fulfilled Shipping* function:
|
|
| - Generation of customer invoices
|
|
|
|
► If you applied for the *Merchant Fulfilled Shipping* function:
|
|
| - Generation of delivery orders
|
|
| - Generation of customer invoices
|
|
|
|
- **List all outside parties with whom your organization shares Amazon Information (e.g. information
|
|
exposed by Amazon through Amazon MWS, Seller Central, or Amazon's public-facing websites) and
|
|
describe how your organization shares this information.**
|
|
|
|
► If you do not share Amazon Information with outside parties:
|
|
Odoo does not share any information with outside parties.
|
|
|
|
► If you share Amazon Information with outside parties:
|
|
[Description of your organization's policy regarding Amazon Information]
|
|
|
|
- **List all non-Amazon MWS sources where you retrieve Amazon Information.**
|
|
|
|
Odoo only relies on MWS to retrieve Amazon Information.
|
|
|
|
- **Describe how your organization restricts public access to databases, file servers, and
|
|
desktop/developer endpoints.**
|
|
|
|
| - Access to the postgreSQL database through the network is disabled and standard ports are
|
|
| closed. The database is only accessible through a socket on the server itself.
|
|
| - The reverse proxy only serves whitelisted directories that are only from sources controlled by
|
|
| Odoo S.A.
|
|
| - API endpoints are password protected (PBKDF2 & SHA512 encryption, salted, and stretched for
|
|
| thousands of rounds).
|
|
| - Login credentials are always transmitted securely over HTTPS.
|
|
|
|
|
|
|
- **Describe how your organization uniquely identifies employees and restricts access to Amazon
|
|
Information on a need-to-know basis.**
|
|
|
|
► If all your employees are properly assigned separate users and given only relevant access rights:
|
|
Access rights are provided to employees based on their role within the company and are
|
|
progressive, based on their responsibility.
|
|
|
|
For instance, salespersons only have access to their own leads/quotes (and thus no access to
|
|
quotes generated through the Amazon API). A salesmanager has access to all quotes/leads for
|
|
reporting purposes (including quotes generated through the Amazon API). A quote will generate a
|
|
delivery order which will be accessible to a 'normal' user of the Inventory application for him
|
|
to be able to print the delivery label and pack the products.
|
|
|
|
► If your employees share users or if they are given more rights than needed:
|
|
[Description of your organization's policy for the assignation of users and access rights to
|
|
your employees]
|
|
|
|
- **Describe how your organization prevents Amazon Information from being accessed from employee
|
|
personal devices.**
|
|
|
|
Odoo does not prevent employees from accessing the organization's data from personal devices.
|
|
Role-based restrictions and access rights still apply.
|
|
|
|
- **Provide details on your organization's privacy and data handling policies (a link to your policy
|
|
is also acceptable).**
|
|
|
|
[Description of your organization's privacy and data handling policies]
|
|
|
|
- **Describe where your organization stores Amazon Information and provide details on how you
|
|
encrypt this information (e.g., algorithm).**
|
|
|
|
Amazon Information is stored in an unencrypted database. Direct access to the database is not
|
|
possible for the customer outside of UI interactions or API calls. Granular access rights control
|
|
ensures that access is not shared to all users of the database.
|
|
|
|
- **Describe how your organization backups or archives Amazon Information and provide details on how
|
|
you encrypt this information (e.g., algorithm).**
|
|
|
|
The entire database is backed up once a day and backups are kept for a minimum of three months
|
|
according to the `Odoo Online SLA <https://www.odoo.com/cloud-sla>`_. Backups are hosted on
|
|
several remote servers as unencrypted database dumps; these backups can only be retrieved by
|
|
Odoo S.A. employees through support requests.
|
|
|
|
- **Describe where your organization monitors and detects malicious activity in your
|
|
application(s).**
|
|
|
|
Odoo Online uses automated probes on our server that report their status in Munin, an opensource
|
|
monitoring tool. This tool automatically triggers alarms when probes detect values outside of
|
|
their pre-defined range. We monitor (among many other things) access rates, response times, ssh
|
|
connections, network activity.
|
|
|
|
- **Describe how your organization's incident response plan addresses database hacks, unauthorized
|
|
access, and data leaks (a link to your policy is also acceptable).**
|
|
|
|
[Description of your organization's incident response plan]
|