myFitment staff have been sending fitment to Amazon for nearly 10 years. During that time, and probably into the future, Amazon has accepted only ACES XML fitment data. myFitment staff have been creating ACES XML fitment for a long time.
If you have read Amazon's ACES information sheet, you may find that it is:
This is because the topic of ACES itself is:
At least to sellers that are new to the topic of fitment.
These two reasons are our sole purpose for being. We want to remove the knowledge and technology barriers that prevent sellers of all sizes from effectively and efficiently managing their fitment data. In order to meet and exceed our customers' expectations, it is necessary that we integrate with Amazon in a couple of different areas.
As you've seen in the Amazon ACES documentation, they make mention of a tool called the Amazon Merchant Transport Utility, or AMTU. This is an unsupported piece of Open Source software that performs file transfers between sellers/vendors and Amazon. It is normally used for individual sellers.
However, it is the primary method for sending ACES XML files to Amazon. As such, myFitment has special dispensation to use it for all of our vendors. Amazon, in working with myFitment, has created a proprietary version of ACES XML that allows us to send massive amounts of fitment to Amazon over 30 times every hour.
After Amazon receives ACES XML files from myFitment, they return to us a "Processing Report". myFitment reads this file and ties the success or failure of each row directly to your ACES data in your myFitment account. To see how this works, please read "How Do I Know If My Data Made It To Amazon?"
myFitment will deliver our direct Amazon API integration in Q4 2017. This will allow sellers to update their listings directly from myFitment in order to:
a) Correct listing errors
b) Change prices
c) Enhance listings
We're excited to offer this new feature to the over 500 Amazon sellers currently using our services for their ACES fitment needs!