6.8.3. How to Integrate with Amazon?

This "How to" should provide you with the necessary steps to implement a working integration with Amazon from scratch using Babelway.

Amazon suppliers are split in two categories: sellers and vendors. Amazon vendors are considered direct Amazon suppliers while sellers are third parties which use the Amazon platform to sell their goods (with more or less Amazon support for shipping etc.). The business terms are different and the integration is different as well:

Figure 6.12. 

Table 6.1. Amazon Suppliers

  Amazon Sellers Amazon Vendors
Message FormatXMLEdifact (EU) or X12 (US)
CommunicationWeb servicesAS2
In BabelwayAmazon Marketplace gateway with an XML message definitionAS2 or SFTP gateway with Edifact or X12 message definition

Amazon Seller - Amazon Marketplace

You're an Amazon supplier looking to integrate your IT systems with your Amazon marketplace account.

Figure 6.13. 

Babelway integrates with Amazon Marketplace using the Amazon Marketplace Gateway IN and Amazon Marketplace Gateway OUT ). You will find the xsd's you need to build your message definitions in the Gateway documentation. These gateways will allow you to implement the following business flows:

  • Retrieve orders from Amazon Marketplace
  • Send Price and Inventory and Product messages to Amazon Marketplace

Amazon Vendor Central

You're an Amazon supplier looking to integrate your IT systems with your Amazon vendor central account. If you haven't already, log in to your vendor central account.

  • Amazon.com: https://vendorcentral.amazon.com
  • Amazon.de: https://vendorcentral.amazon.de
  • Amazon.fr: https://vendorcentral.amazon.fr
  • Amazon.co.uk: https://vendorcentral.amazon.co.uk
  • Amazon.it: https://vendorcentral.amazon.it
  • Amazon.es: https://vendorcentral.amazon.es

Figure 6.14. 

Basic Setup

Upon logging into vendor central and going to the EDI > Self-service menu, you will find a flow to get started. No Babelway effort is required during this step. This will allow you to determine your identifiers and provide some sample data Amazon can use in test files. Follow the 5 step flow.

Figure 6.15. 

Configure and test your connection

Once your basic setup is complete, you should see you're free to set up a connection and begin testing message processing.

Figure 6.16. 

Amazon allows you to connect using AS2, SFTP, VAN or another known EDI Provider. Amazon's preferred integration method is AS2. It is ours as well and this implementation guide will only focus on the AS2 configuration. The process is extremely simple. In order to set up your connection, you will need to work in parallel in Babelway and in vendor central. You should try to keep a tab open on both sites.

In Babelway, create an AS2 Gateway IN using a dummy "from" value:

Figure 6.17. 

Download the AS2Specifications.zip file on the gateway properties page to find the required information to proceed with the Amazon configuration flow:

Figure 6.18. 

In vendor central > EDI > Self Service Setup, select "Add Test Connection" to get started. This will bring you to the screen below.

Figure 6.19. 

Fill it in as follows:

  1. Select "Connect directly to Amazon (AS2, SFTP)"

  2. Select "AS2 (preferred)"

  3. Name your connection whichever way you find meaningful.

  4. AS2 ID: see AS2 Specification file point 1

  5. AS2 URL is: see AS2 Specification file point 2

  6. MDN Receipt Type: "Sync"

  7. Message signing algorithm: "SHA256" (note that older AS2 gateways had SHA1 configured by default)

  8. Certificate: You will find it in the AS2 specification ZIP. Upload the .crt file.

The next screen will provide you with the following information:

Figure 6.20. 

You now have the information necessary to complete your gateway IN configuration: Amazon's AS2 ID (1. from figure 6.15) and the certificate for verification (3. from figure 6.15).

Figure 6.21. 

And you can use Amazon's hosted AS2 Server URL to configure your gateway AS2 out:

Figure 6.22. 

The last step of the Amazon configuration flow is "Network Firewall". Do not concern yourself with this screen and click "continue". You will reach the testing screen:

Figure 6.23. 

In Babelway, you will need your gateways to be deployed in working channels to begin the testing phase. You can go ahead and configure you target channels if you wish, but you can start with not defined messages and no transformation to begin to test your connection. Your target channels:

Channel You to Amazon

Figure 6.24. 

Channel Amazon to You

Figure 6.25. 

Once your two test channels are successfully deployed in Babelway, you can go back to the testing screen in vendor central. Request to send a test file (you should see it appear in Babelway's monitoring screen shortly) and check the file status in Amazon. Once a file has successfully passed, you can continue on to the next step:

Test receiving from Amazon

Figure 6.26. 

You can download Amazon's test file or any other and send it to them through your channel. As soon as Babelway's monitoring screen indicates the message was processed successfully you can have Amazon check for the test file:

Test sending to Amazon

Figure 6.27. 

Once you've correctly passed the connectivity test, you will be asked which messages you'd like this connection to manage. The EDI messages you can link are:

  • Purchase Order
  • Purchase Order Acknowledgment
  • Advance Shipment Notification
  • Invoice
  • Sales Report
  • Cost Inventory Feeds

You can create separate connections for different message types if necessary but a given message type can only use one connection. The same process applies for setting up a production connection.

Configure and test your messages

Amazon provides a zip with all their EDI documentation. You can find such a zip in the Amazon Resources page but ideally you should download the latest one which you can find at Vendor central > edi > Self service setup > learning and support > Edi specifications (in technical).

For each message type you will try to exchange you will face the same kind of survey process as you did for your initial setup. The goal of the survey is certain that your message content meets Amazon's basic requirements. Note that using Babelway, you will transform your messages to the proper format, but their survey remains totally relevant. If you don't have the information logically inside your messages no EDI provider will be able to infer it.

You can configure your Amazon X12/Edifact message definitions using their sample information.

The rest of the set up is essentially connecting Babelway to your own systems and mapping your files to Amazons'.

This documentation is based on our integration projects but we'd love to enhance and update it with your own feedback and experience: support@babelway.com.

Last update: Nov 17 2017