Amazon compliance documents rejected: what to check first

1. Preserve the request before changing anything

Keep the complete message, date, affected ASIN, and any document names or reasons Amazon provided. Save the listing details as they appeared at the time of the submission. Keep original copies of submitted materials separately from revisions. This creates a record you can compare instead of relying on memory. If the notice asks for a specific item, write that request down in its own words.

2. Compare product identity across the evidence

Create a short comparison for model, SKU, product name, and variant. Mark which document each value came from, including its page. For example, ABC-100 on a certificate and ABC-100B on a listing is an observable difference; it is not yet proof that the product was tested incorrectly. Ask the manufacturer or laboratory whether both identifiers refer to the same tested product and request supporting documentation. Do not simply edit an identifier to make the documents agree.

3. Separate missing evidence from conflicting evidence

A missing report, an unreadable page, and two different model numbers are different problems. Label each observation as present, missing, inconsistent, or unresolved. Write down what would resolve the question: an original report, a clearer label photo, or confirmation from the responsible party. Avoid calling a laboratory “verified” merely because its name appears in a PDF.

4. Ask a precise follow-up question

Replace “Why was this rejected?” with an evidence-specific question when possible: “The request refers to model ABC-100B, while the certificate identifies ABC-100. Does the report cover this variant?” Questions about test scope belong with the laboratory; questions about the listing or submission workflow belong with Amazon. ComplyDebug cannot see Amazon’s internal review process.

5. Keep a record of what changed

Before another submission, compare the revised files with the original request and note each change, its source, and any unresolved question. Do not order new tests or alter a certificate solely because this checklist mentions a possible issue. Product-specific requirements and the scope of a test report need qualified assessment. A consistent set of documents is useful evidence, but it does not guarantee approval.

Sources and scope

• CPSC: Children’s Product Certificate
• CPSC: General Certificate of Conformity

The CPSC pages explain certificate requirements. They do not explain a particular Amazon rejection. Use the request in your own Seller Central account as the source for what Amazon asked you to provide.

Informational guidance only; not legal advice, testing, certification, or an approval guarantee. Read the full disclaimer.

See a worked example

The fictional sample shows a model mismatch, an unresolved standard question, and evidence-linked next actions.

More document guides · How preview documents are handled