Keep the header rows
ComplyShelf reads the row of technical keys Amazon's own processor keys off (item_sku, feed_product_type, …). Without that row the file cannot be matched to anything, and it is refused rather than guessed at.
Amazon EU · Pre-upload diagnostics
Check your Amazon flat file for GPSR errors
Find missing Responsible Person, manufacturer, safety-document, and template data at SKU level before you prepare the next bulk correction.
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.
Before you upload
Which file should I upload?
Use the Seller Central template with its item rows when you want those rows assessed. A blank supported template can create a product-type target for compatible Catalog listings, but it contains no products to review by itself. A listing report answers a different question. Compare the Amazon files in detail.
01
02
.xlsx or a delimited export
An .xlsx workbook, or a .txt, .tsv or .csv export of one, up to 25 MB. An older .xls is a different format: open it and save a copy as .xlsx first.
03
Rows for assessment, or a target
Item rows carry the SKUs to assess. A blank supported template can instead define the target, then compatible listings are added from Catalog.
04
Confirm the marketplace
An Amazon flat file carries no column saying which marketplace it came from, so you pick it when you upload.
Illustrative example
What a review actually says, SKU by SKU.
Four rows from a small template, run through the same import and readiness review the app uses. The products and SKUs below are made up for this page — they are not a customer's file — but every finding is the one ComplyShelf reports for that row.
SAMPLE-01
Manufacturer named, but not contactable
The file gives a manufacturer name and nothing else. Complete that operator's address and contact once, and it applies to every SKU that shares it.
SAMPLE-02
No manufacturer in the row
Different from the row above: there is no operator to complete, only one to add. The review keeps the two apart so you know which is which.
SAMPLE-03
Product number present, but no GTIN read
The row carries a number without saying what kind of identifier it is. A number is not an EAN until the template says so, so the identifier is reported as missing rather than assumed.
SAMPLE-04
Safety attestation retained, not assessed
This row has a gpsr_safety_attestation value. ComplyShelf retains it exactly as supplied in the raw source row and offers no reading of it, so the row lands in the same place as SAMPLE-01. Cannot assess is a result, not a gap.
Every one of these rows also needs an EU Responsible Person and a compliance evidence URL, because this template carries neither — that is the work the review sets up. None of them has been submitted to Amazon, so none carries an Amazon result yet.
If the uploaded file also contains supported listing text, the wording review can show a phrase, its recorded reason, and the seller decision path. See the environmental-claims review workflow. See the environmental claims checker for supported languages and bulk-removal previews.
Checks with a next action
See what is wrong, where it is, and what to resolve next.
01
Template identity
Detect a missing technical-key row or a file that is not a supported Amazon seller template.
02
SKU-level gaps
Keep every finding tied to the original SKU and marketplace instead of returning a generic file warning.
03
GPSR readiness
Surface a missing or incomplete manufacturer, a missing EU Responsible Person, and a missing compliance evidence URL.
04
Safe mapping
Show which columns ComplyShelf can fill, retain the original row for traceability, and generate a focused update from confirmed columns.
ComplyShelf can provide values for twelve fields: the manufacturer's name, address, country, email and phone; the same five for the EU Responsible Person; a compliance evidence URL; and a product safety page URL. The original raw row is retained, but the generated update is focused: it emits the SKU key, partial-update mode, and the allowed columns you confirmed rather than promising to reproduce every unknown source column.
The technical keys behind those names
Amazon names columns by technical key, so ComplyShelf matches on those rather than on the
localized labels above them — item_sku identifies the row,
feed_product_type the product type, manufacturer the manufacturer
name. A key it recognises with high confidence is offered as a suggestion; a key it only
pattern-matches is shown but never filled in for you, and nothing is written to any column
until you confirm it.
Two names are deliberately not guessed at. A DSA responsible-party contact is not the GPSR
EU Responsible Person, and gpsr_safety_attestation is a yes/no assertion rather
than a document link. Both stay visible and unmapped instead of being turned into a
confident but wrong answer.
Honest result
A preflight check, not an Amazon acceptance guarantee.
The checker finds template and readiness problems supported by ComplyShelf. Amazon may still apply category, marketplace, account, and policy rules when the file is uploaded.
Your original file and raw rows remain available for traceability. The generated update includes only its row key, partial-update mode, and confirmed supported columns; unknown columns are neither guessed nor promised as output.
Already have a processing report? Continue with the Amazon GPSR upload error guide.
FAQ
Checking an Amazon GPSR flat file
What does the checker inspect?
It reads the technical keys carried by the Amazon template, identifies its SKU rows, and reports missing or unsupported data that affects the GPSR correction workflow.
Do you need my Seller Central credentials?
No. Upload the template inside your own ComplyShelf workspace. Never send passwords, session cookies, or Seller Central credentials.
Will a clean result guarantee acceptance?
No. A clean preflight means ComplyShelf did not find a supported structural or readiness problem. Amazon can still reject data under marketplace, category, account, or policy validations.
Can I fix hundreds of SKUs after the check?
Yes. Confirm reusable manufacturer, EU Responsible Person, and evidence records, assign them across the affected listings, and continue through the bulk-fix workflow.
Does the checker judge my safety attestation?
No. The original gpsr_safety_attestation value remains in the retained source row and is never interpreted, so a Yes or a No changes nothing in the review. It is not automatically emitted in the focused update. Whether the attestation is correct is a judgement about your product, not something a file check can settle.
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.
Know what the file is missing before the next upload.
Bring the original Amazon template into your workspace and turn a large spreadsheet into an actionable SKU-level review.
Check my Amazon file