The question rarely arrives as a question. It arrives as a notification in Seller Central: Amazon has requested product compliance documents for one of your ASINs, with a review deadline attached. If you are reading this before that happens, the useful thing to understand is that there is no single list called "Amazon's required certifications". What Amazon asks for is determined by the marketplace, the product type, and sometimes a keyword in your listing that made the system classify it as higher risk.
How Amazon's compliance requests actually work
amazon.com, amazon.de and amazon.co.jp are separate operations. Each marketplace applies the product rules of its own region, and each can request documents independently. A listing that passed review on Amazon US tells you nothing about what Amazon EU will ask for the same product.
Requests are triggered in a few ways. Some categories have requirements that must be met before the listing goes live at all. Others are flagged by product-type classification - battery-powered, radio, children's products - or selected in periodic sweeps. Complaints and safety incidents trigger them too. Once a request arrives, the listing can be suppressed until documents are reviewed and accepted, and ignoring the request leads to removal. Repeated non-compliance can escalate to account-level consequences.
One practical consequence sellers underestimate: the same product sold on three marketplaces can mean three different document sets, produced from the same test data.
What Amazon asks for, marketplace by marketplace
Amazon does not ask for "a certification" in the abstract. It asks for documents, and the list follows the regulation behind the product type.
United States
Electronics with digital circuitry fall under FCC equipment authorization rules. A device that only emits incidental radio-frequency energy - most digital electronics - is covered through a Supplier's Declaration of Conformity based on a test report from an accredited laboratory. A device that intentionally transmits radio, such as anything with Bluetooth or Wi-Fi, needs FCC Certification with an FCC ID shown on the product. US rules require the supplier of a radio-frequency device to provide compliance information on request, and Amazon enforces this through listing checks - sellers of radio devices without an FCC ID or SDoC documentation regularly see their listings removed.
For children's products, a Children's Product Certificate based on CPSC testing rules is what gets requested. And a point that comes up constantly: Amazon does not universally require "UL". What it requires is proof of compliance from an accredited laboratory. UL is one lab brand among several, not a legal requirement for most electronics.
Europe
Amazon EU asks for the standard CE documentation set: a Declaration of Conformity and test reports matching the model being listed. Since the General Product Safety Regulation (EU) 2023/988 became applicable in December 2024, marketplaces have obligations to verify trader information, so a responsible person established in the EU is now part of what gets checked. For France and Germany, Amazon also enforces EPR registration numbers - WEEE, packaging and, where relevant, batteries - because it is legally obliged to verify them.
United Kingdom and Japan
Amazon UK follows UK product rules, with the same logic: safety documentation matching the model, under the UK regime rather than the EU one. Amazon Japan requests PSE documentation for products in the scope of Japan's electrical safety law. Neither needs a separate strategy - the underlying test data is largely the same, and the documents are derived from it.
The documents that actually pass review
Across marketplaces, the accepted package almost always contains the same elements:
- Test report(s) from an ISO/IEC 17025 accredited laboratory, for the standards relevant to the marketplace, showing the exact model being sold
- Declaration of Conformity (for CE marketplaces) naming the responsible entity and the correct directives and standards
- Product and label photos showing markings, ratings and the FCC ID where one is required
- The laboratory's accreditation certificate, which Amazon occasionally asks for alongside the report
- Responsible person and EPR details for EU marketplaces where applicable
Why compliant products still get rejected
Most rejections we see are not about the product being unsafe. They are about documents that do not connect to the listing. Four situations account for the majority:
The model number does not match. The report covers one model designation, the listing sells another, and nobody can explain on paper that they are the same product. A seller once had a valid report for the "Pro" version while the listing offered the "Pro V2" - a firmware revision with an unchanged PCB, but nothing in the documents established that. The product was compliant; the file was not.
The radio report covers only one mode. A device with both Bluetooth and Wi-Fi was tested as Bluetooth only, because that was cheaper. Then the listing mentioned the Wi-Fi configuration, or the app required Wi-Fi setup, and the review failed - the report did not cover what was being sold. If the product has several radio modes, every mode that ships enabled needs to be in the test scope.
The power configuration changed after testing. The product passed with the original adapter, then procurement switched to a cheaper adapter before mass production. The report names a supply configuration that no longer exists, and the seller cannot answer the compliance request without retesting - usually late, mid-launch.
The Declaration of Conformity names the wrong party. The factory signed the DoC in its own name, but the seller is the trader Amazon is asking. A declaration is only usable if it covers the product and connects to the entity being asked for documents - otherwise the file has a gap no amount of uploading will close.
All four are avoidable, and none of them is expensive to avoid. They cost money only when discovered after the launch date.
Getting the file right before the request arrives
The reliable sequence is to test against the real sales configuration, not a convenient one:
- Fix the model list - every variant you intend to list, with the exact model numbers that will appear on the listing
- Fix the hardware configuration - adapter, antenna, radio modes - before testing, and hold it
- Test to the standards of every marketplace you plan to sell on, from one sample submission where possible
- Produce the DoC naming the entity that will actually be the trader on the platform
- Review the label artwork before printing, since the label is what appears in your photos
This is the same preparation that answers compliance checks from distributors, customs and end customers, not only Amazon. Our overview of certifications for selling electronics in Europe explains how the EU document set fits together, and the testing and certification services page shows how a scope review turns one submission into documents for several markets.
As a laboratory, we see the Amazon side from the testing end: the reports we issue are the reports sellers upload. The most common avoidable problem is scope decided too narrowly at quotation time to cover the marketplace where the product actually sells - which is why we push on model lists and radio configurations before quoting. If you want a scope check against your target marketplaces, send the product specification and the markets you plan to sell on, and we will confirm which documents each one will ask for and which of your existing reports can be reused.
If you are preparing an electronics listing and want to know what each marketplace will ask for, send us the product specification, the radio and power configuration, and the marketplaces you plan to sell on.
We will map out which documents apply, flag where your current reports fall short of the listing, and quote the testing that fills the gaps - before Amazon's deadline does it for you.