Keep both files
Retain the exact submitted template and Amazon processing report as one diagnostic pair.
Amazon EU · Processing report
Understand and fix Amazon GPSR upload errors
Separate file-level failures from rejected SKU rows, preserve Amazon's original message, and prepare the smallest safe correction.
Start with the failure boundary
Did Amazon reject the file, or only individual rows?
The difference determines whether you repair the template structure or correct data for a specific SKU.
FILE
Missing or invalid header
Return to the original Amazon template. Do not recreate, translate, reorder, or remove its technical header rows.
FORMAT
Unsupported or malformed file
Check that the uploaded artifact is the expected seller template and has not been converted into an incompatible delimiter or workbook structure.
ROW
Required identifier is missing
Locate the affected SKU and verify the row identity, product type, action, and other mandatory keys requested by that template.
GPSR
Compliance data is incomplete
Review manufacturer, EU Responsible Person, safety attestation, evidence type, language, and URL as applicable to the row.
URL
Document or image cannot be used
Verify that the submitted target is the intended evidence, is reachable as required, and matches the language and media fields in the template.
A safer correction loop
Preserve the evidence. Change only what you can explain.
01
02
Attach outcomes
Match accepted, rejected, and needs-fix results back to the original listing rows.
03
Resolve the gap
Correct a verified field or mapping without guessing at unrelated Amazon columns.
04
Regenerate narrowly
Prepare only the rows that still need correction and retain the audit trail for the next result.
If Amazon rejected the template before producing usable row results, begin with the flat file checker. For catalog-wide remediation, continue to the bulk GPSR fix workflow.
Do not erase the clue
Common fixes that create a second problem.
Rebuilding headers manually
Human-readable labels are not a substitute for Amazon's technical keys and template metadata.
Replacing the whole row
A broad overwrite can alter valid listing data that had nothing to do with the rejected GPSR field.
Discarding the report
Without the original error and row outcome, the next change becomes a guess instead of a traceable correction.
FAQ
Amazon processing report errors
Why did Amazon reject my GPSR flat file?
The cause may be file-wide structure, a missing mandatory identifier, incomplete GPSR attributes, an unusable URL, or a marketplace and category rule affecting one row. Keep the submitted file and processing report together to identify the boundary.
Should I download a fresh template?
Use the appropriate current template when Amazon reports an invalid or outdated file structure. Preserve the failed file and report for comparison; do not copy only the visible labels into a new spreadsheet.
Can I ignore warnings when some rows were accepted?
Do not assume every warning is harmless. Record the outcome per row, verify which listings actually changed, and decide from the exact message and intended correction.
Does ComplyShelf guarantee the next upload will pass?
No. ComplyShelf helps diagnose supported errors and preserve a traceable correction workflow. Amazon remains the final validator and can apply rules outside the information available in the file.
Turn the processing report into the next safe action.
Keep each Amazon error tied to its SKU, resolve verified gaps, and regenerate only the rows that still need attention.
Review errors in the CRM