Keep the diagnostic pair
Retain the exact template you sent and Amazon's processing report together; the report only makes sense against that file.
Amazon EU · Processing report
Read the Amazon processing report and fix what you can explain
Separate file-level failures from rejected SKU rows, keep Amazon's original message, and prepare the smallest correction you can explain. Where a code's meaning is not confirmed, this page says so rather than guessing.
Creating an account sets up your workspace first — then you upload your file.
Free during early access · no payment card. Paid plans will be announced in advance.
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
Submitted file → row outcome → narrow retry.
01 · SUBMITTED FILE
02 · ROW OUTCOME
Attach the result to its SKU
Match accepted, rejected, and needs-fix outcomes to the original row and preserve Amazon's message verbatim.
03 · NARROW RETRY
Regenerate only what failed
Correct a verified field, prepare the smallest retry set, and keep the previous batch for comparison.
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.
Before you can diagnose anything
Get the report, and keep the file you actually sent.
Amazon returns a processing report for a submitted flat file. Download it from the upload history in Seller Central for that submission, while it is still there — it is tied to that upload and is not regenerated later.
Keep the exact file you submitted alongside it. The report refers to rows by their position and SKU, so without the original file a row number points at nothing, and you are left comparing an error to a file you have since edited. The pair is the evidence; either one alone is not. Not sure which Amazon file is which?
One report, start to finish
What happens when you attach it.
This is the ComplyShelf half of the job, and it is exact. The SKUs and messages below are made up for this page; the behaviour is reproduced from the product.
1
The header is found, whatever it is called
Reports differ between accounts and marketplaces. ComplyShelf matches the header by known aliases — original-record-number or row, error-code or code — rather than one exact spelling. If it cannot find a header at all, it refuses the file and says so instead of importing nothing quietly.
2
Each row goes back to its own SKU
A row naming SAMPLE-02 is recorded against that listing, not against the batch. Many reports list only the failures and carry no status column at all; in that case an error code or message is itself the signal that the row failed, and it is marked rejected.
3
An unexplained code stays unexplained
ComplyShelf shows you the raw code and Amazon's own message. It attaches an explanation only for codes whose meaning has been confirmed against a first-party source, and that list is empty today — so 5995 and 8541 are surfaced verbatim with no interpretation attached. An invented explanation is worse than none.
4
Only the rows that still need it are regenerated
The next update file is built from the rows that failed, not from the whole catalog again, and the previous batch and its outcomes stay on record.
The half we cannot do for you
What a specific Amazon code means.
We will not tell you what 5995 or 8541 mean. Sellers report both in
connection with GPSR submissions, and there are plausible readings of each, but we have not
confirmed either against Amazon's own documentation or a reproduced upload — and a plausible
reading applied to a live catalog is a guess with your listings on the line.
How to get an answer for your case:
- Read Amazon's message on the row itself. It is usually more specific than the code, and it is the part written for you.
- Compare the failing rows with the accepted ones from the same file. What differs between them is the shortest route to the cause.
- Check the Seller Central help page for that error code in your marketplace, since the same code can be documented differently per marketplace.
- Change one thing and resubmit a small batch. A correction you cannot explain is not a fix, even when the next upload passes.
- If Amazon's answer is still unclear, open a case with the report attached. That is the first-party source; nothing on this page is.
When a code's meaning is confirmed, it is added to the product so the explanation appears next to the error — sourced, not inferred.
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.
What do errors 5995 and 8541 mean?
We do not publish an answer, because we do not have a confirmed one. Both are reported by sellers around GPSR submissions, and there are plausible explanations for each, but none has been verified against Amazon's own documentation or a reproduced upload. ComplyShelf shows both codes with Amazon's message and no interpretation attached. How to investigate your own case.
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.
Before you send a file
Who you are sending it to.
ComplyShelf is built and run by Denys Holda, an individual business established in Italy and registered with the Camera di Commercio Monte Rosa Laghi Alto Piemonte under REA BI-325108. It is a small operation, not a compliance agency, and you can reach a person at hello@complyshelf.com.
- Your files stay in your workspace. They are stored privately and are not shared with other customers. Administrative access is restricted, but it exists — support cannot honestly promise nobody can ever look at a file, so it does not. How the data is protected.
- Nothing becomes public because you uploaded it. A product safety page is published only when you choose to publish one, through a link that can be revoked afterwards. Public pages and revocable links.
- You can ask for your data to be deleted. Write to the address above. Your rights and what is kept and for how long.
- Never send credentials. ComplyShelf holds no Seller Central login and never needs one. If anything asks you for one, it is not us.
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.
Check my Amazon file