Automotive shoppers on Amazon expect one thing above all else: confidence that the part they are buying actually fits their vehicle. That confidence comes from fitment data. If your catalog data is incomplete, inaccurate, or out of sync with Amazon’s requirements, you risk missed sales, higher return rates, and a frustrating customer experience.
If you’re wondering how to submit fitment data to Amazon today, the short answer is this: Amazon automotive fitment still depends on properly structured ACES 3.2 XML data, correct ASIN matching, and exact brand and part-number alignment. However, the workflow most sellers should follow today is different from the older AMTU and MWS process that still appears in some older resources and team documentation.
In this guide, we’ll explain the current fitment submission workflow, what Amazon expects from brands and catalog teams, and how the older AMTU/MWS method fits into the history of Amazon automotive data management.
Why Amazon Fitment Data Matters
When Amazon has accurate fitment data for a part, shoppers can use vehicle lookup tools and Amazon’s fitment experience to confirm whether a part works for their year, make, model, and other vehicle attributes. That improves conversion rates because buyers feel more confident in what they are ordering.
Accurate fitment data also helps reduce costly returns. If buyers receive a part that does not fit because the application data was wrong or incomplete, that can lead to negative reviews, customer service issues, and avoidable operational costs.
For automotive aftermarket manufacturers, brand owners, and some data providers, fitment data is one of the most important components of a successful Amazon strategy.
What Amazon Currently Requires for Automotive Fitment Data
Amazon’s automotive fitment workflow still centers on ACES (Aftermarket Catalog Exchange Standard) data. In practical terms, most brands preparing automotive fitment data for Amazon should expect the following requirements:
- ACES 3.2 XML format: Amazon automotive fitment data is commonly prepared and submitted in ACES 3.2 XML.
- Existing ASINs: Amazon fitment data is matched against products that already exist in Amazon’s catalog.
- Exact brand alignment: The brand in your ACES file must match Amazon’s catalog values exactly.
- Exact part-number alignment: Your part numbers must align with the corresponding Amazon listings, including punctuation, spacing, and leading-zero handling where applicable.
- Vehicle-level application accuracy: Year, make, model, engine, trim, and other qualifiers must be complete and properly mapped.
- A dedicated fitment workflow: Brands may submit through Amazon’s current automotive fitment process directly or use a third-party fitment data provider.
In other words, success is not just about generating an ACES file. It is about ensuring your ACES data can be matched cleanly to Amazon’s product catalog.
How to Submit Fitment Data to Amazon Today
While Amazon’s internal tools and onboarding steps can evolve over time, the modern process generally looks like this:
- Prepare your application data in ACES 3.2. Make sure your application records are complete, standardized, and validated before submission.
- Verify ASIN, brand, and part-number consistency. Amazon fitment matching depends heavily on clean catalog alignment.
- Set up the correct submission path. Depending on your business, that may mean using Amazon’s automotive fitment workflow directly or working with a fitment data provider that submits on your behalf.
- Submit a sample or validated file if required. Amazon may require sample validation or onboarding review before broader fitment ingestion.
- Review processing feedback carefully. If there are failures, mismatches, or validation issues, correct them quickly so your fitment data can be accepted.
- Maintain your data over time. Fitment is not a one-and-done task. Catalog updates, supersessions, product launches, and corrections all need ongoing attention.
For many companies, the main decision is whether to handle the process directly or use a third-party provider that specializes in Amazon fitment submissions.
Direct Submission vs. Using a Third-Party Fitment Provider
Some manufacturers and brand owners prefer to manage the Amazon fitment process themselves. Others choose to work with a third-party provider that already understands Amazon’s automotive ingestion requirements and can help manage validation, error handling, and ongoing updates.
Using a provider can be especially helpful if:
- You manage a large catalog with frequent changes.
- You need help validating ACES data before submission.
- You want support interpreting Amazon processing feedback.
- You need a more operational workflow for ongoing fitment maintenance.
Whichever path you choose, the underlying data quality still matters. Amazon cannot reliably ingest or apply fitment data if brand names, part numbers, or vehicle mappings do not line up correctly.
Common Amazon Fitment Submission Errors
Many Amazon fitment issues come down to data mismatches rather than file transmission problems. Some of the most common issues include:
- Brand mismatches: The brand in the ACES file does not exactly match the brand attached to the Amazon listing.
- Part-number mismatches: Differences in punctuation, dashes, spacing, or leading zeros prevent clean matching.
- Invalid or outdated ACES formatting: The file version or structure does not meet Amazon’s requirements.
- Missing ASIN relationships: The product does not exist in Amazon’s catalog in the way the fitment data expects.
- Incomplete vehicle qualifiers: Missing engine, trim, or submodel details can create inaccurate applications.
- Poor catalog governance: Different versions of the same part data exist across systems, causing conflicts.
This is one reason catalog discipline matters so much. If your internal data is inconsistent, Amazon fitment submissions become much harder to manage successfully.
Why Catalog Management Matters Before Submission
Before a fitment file ever reaches Amazon, your internal catalog data needs to be right. That includes brand hierarchy, part numbers, application data, assets, product attributes, and how all of that information is maintained across channels.
PDM Automotive helps manufacturers, distributors, and resellers organize and manage automotive product data from a single source of truth. That makes it easier to validate fitment-ready data, support Amazon catalog workflows, and reduce errors caused by fragmented systems or manual processes.
If your team is struggling with Amazon fitment accuracy, the real issue is often upstream in the way your catalog data is stored, normalized, and maintained.
Legacy Process: AMTU and MWS
If you’re researching Amazon fitment workflows, you may still come across references to Amazon AMTU, Amazon MWS, or older fitment upload instructions built around those tools. That can be confusing if your team is trying to determine which process still applies today.
AMTU (Amazon Merchant Transport Utility) and MWS (Marketplace Web Service) were part of Amazon’s older automotive data workflow. For years, automotive catalog teams used these tools to transmit ACES fitment data to Amazon.
Today, those terms are best understood as legacy Amazon automotive terminology. They are still useful to know because older documentation, forum threads, third-party help articles, and inherited internal process docs may still reference them. But they should not be treated as the default workflow without first confirming Amazon’s current fitment requirements.
Why AMTU and MWS Still Show Up in Older Resources
- Older Amazon automotive setup guides still reference them.
- Some third-party blogs and knowledge-base articles have not been updated.
- Catalog teams often inherit documentation that still mentions AMTU and MWS.
- Legacy process language can persist long after the workflow itself has changed.
If your team encounters AMTU or MWS in older documentation, treat that as a prompt to verify the current Amazon process rather than assuming the older implementation steps still apply as written.
Final Thoughts
Submitting fitment data to Amazon is still one of the most important technical requirements for automotive aftermarket brands selling vehicle-specific parts online. The essentials remain the same: clean ACES data, exact ASIN matching, precise brand and part-number alignment, and a workflow that can support ongoing catalog changes.
What has changed is the process language. If your team is still talking about AMTU and MWS, it may be time to update your documentation and workflows. Those terms still matter as historical context, but the priority today is making sure your fitment strategy aligns with Amazon’s current automotive submission requirements.
Want help getting your catalog in shape for Amazon and other eCommerce channels? Request a demo or contact PDM Automotive to see how we can help you manage fitment-ready data more effectively.
