Amazon GPSR safety document rejected or still open: next steps

A GPSR request that remains open is not, by itself, proof that your document was rejected. First identify whether the submission is awaiting review, explicitly rejected, or accepted while another listing issue remains. Each needs a different response.

Which messages are documented?

Amazon's GPSR guidebook, pages 9–10 illustrates rejected safety-document submissions, including a mismatch between the uploaded file and selected document category. The guide is in Chinese with Seller Central screenshots. It shows a replacement-submission action for some rejection reasons. These are examples of account workflows, not a single email sent to everyone.

An Amazon staff forum explanation also distinguishes image acceptance, rejection and validation in progress. That explanation dates from the 2024 rollout: its historic review-time estimate is not a current service promise.

What should I do for each status?

What you can verify	Practical next action
Explicit rejection with a reason	Save the reason and change the part it identifies
Review still in progress	Record the submission date and follow the current account instructions
File accepted, offer still inactive	Check for a separate manufacturer, Responsible Person or listing issue
No replacement or appeal action available	Ask support which action applies to this ASIN and marketplace

The table is our troubleshooting sequence. It does not predict Amazon's decision or review time.

How do I check a rejected file?

1. Open the exact file you submitted. Check that it opens, is readable and describes the affected model or variant.
2. Compare its contents with the selected document category. A safety sheet and a test report serve different purposes. Amazon's guidebook documents category mismatch as a rejection scenario; follow the correction route shown in your account. Source: guidebook, pages 9–10.
3. Check the destination and language. Amazon's bulk-upload instructions describe selecting one product type and one store with the appropriate store language. Check your current template rather than reusing an unrelated marketplace file.
4. Compare the safety text with the actual product. A generic warning copied from another item may be irrelevant. Ask the manufacturer for missing instructions or evidence.
5. Record what changed. Keep the previous rejection, replacement filename and submission reference together so the next review can be explained accurately.

Do not remove a genuine hazard warning just to make the document shorter. Do not select a no-warning declaration unless the underlying assessment supports it.

What should a support request contain?

Here is an original draft, not Amazon's prescribed appeal format:

ASIN [ASIN], marketplace [store], submission [reference/date]. The displayed result is [exact status]. The rejection reason is [reason, if present]. I checked [document type/language/product identifier] and changed [specific correction]. Please confirm whether this needs a replacement document or another action. The current screen [does/does not] offer resubmission.

Use only statements you can substantiate. Attach the specific evidence requested through the account's support workflow.

Can EUSellKit fix the rejection?

If you need to assemble verified safety text into a document, try the free safety-information generator. For supported products, the optional €14 pack adds documentation drafts and label content; see a sample first.

Neither option supplies test results, a Responsible Person or guaranteed reinstatement. An accepted submission still waiting on another issue may need support rather than another paid file. See also the manufacturer-information checklist.

Sources checked on 14 September 2026. Your account's current reason and instructions take priority over historic screenshots.