Amazon EU · Choosing a file
Which Amazon file should I upload?
Amazon gives you several exports and they answer different questions. Picking the wrong one is the most common reason a compliance review says less than expected — not because the tool failed, but because the file never held the answer.
Choose the source for the job in your product compliance workspace: All Listings brings in catalog records; supported templates guide channel corrections using your operator records and evidence library.
Four common files
What each one contains, and what it cannot prove.
Seller Central template, populated with your items
Contains: the technical key row, your SKUs and whatever compliance values those rows carry. Cannot prove: what Amazon holds on the live listing, or why one was blocked. Useful for: assessing those rows and establishing the target an update is built against. Read by ComplyShelf: yes — use this path for an immediate SKU-level review.
All Listings report
Contains: SKU, ASIN, title, status, product id and its type. Cannot prove: which compliance attributes exist on a listing, or the reason it went inactive — it carries no GPSR data at all. Useful for: seeing the scale of a problem and bringing a catalog in. Read by ComplyShelf: yes, as a catalog import.
Category Listings report
Contains: a category-shaped export of your listings. Cannot prove: anything ComplyShelf can act on today. Useful for: your own inspection in a spreadsheet. Read by ComplyShelf: no. It is not a supported input, and we would rather say so than have it fail in a way that looks like your file is broken.
Processing report for a submission you made
Contains: per-row outcomes and error codes for one uploaded file. Cannot prove: anything about rows you have not submitted. Useful for: finding out what Amazon actually said. Read by ComplyShelf: yes — attach it and each row is recorded against its SKU. How to read one.
For a SKU-by-SKU GPSR review, use the populated Seller Central template. Start the Amazon GPSR file checker with its item rows; use the bulk fix workflow when you are ready to assign reusable records and prepare an update.
Assessment or target
A populated template answers questions; a blank one can still define the target.
A template populated with the products you are fixing gives ComplyShelf rows to assess immediately: the technical keys identify the fields, and each item row ties findings to a SKU. Use this when you want to review what those rows already contain.
A blank or header-only supported template has a different job. It can establish the product-type target. It has no product rows to assess. Add compatible listings from your ComplyShelf Catalog to that task; those listings are not part of this upload's check. Blank is therefore a starting point for a target, not a claim that products were reviewed.
When the file is not usable
Three ways a file goes wrong, and what to send instead.
A spreadsheet rebuilt by hand
ComplyShelf matches columns on Amazon's own row of technical keys, not on the human-readable labels above it. A sheet retyped, translated or reordered has lost that row, so it is refused outright rather than guessed at, and it is not repaired for you. Download the template again from Seller Central and put your data into it without touching the header rows.
A report where a template was needed
A listing report describes what exists; a template describes what you are submitting. If a review reports far less than you expected, check which of the two you uploaded before concluding the data is missing.
An old .xls, a macro workbook, or a password-protected file
Supported: .xlsx, or a delimited export of it as .txt, .tsv or .csv, up to 25 MB. An older .xls is a different format despite the similar name — open it and save a copy as .xlsx. Macro-enabled and password-protected workbooks are refused. The reason is always named, so you are not left guessing which of these it was.
Where to get it
Downloading the file from Seller Central.
Checked 28 September 2026. Amazon requires sign-in, and the labels can vary by marketplace and account. The links below are first-party Seller Central help pages for the same inventory-template article (G1641); use the host for the marketplace where the listing lives.
Start from Amazon's help article, select the product type and template that match the update, and download the current file while signed in. Do not copy a menu path from a third-party guide when your account shows a different label.
- Amazon.co.uk · inventory file templates (G1641)
- Amazon.de · inventory file templates (G1641)
- Amazon.fr · inventory file templates (G1641)
- Amazon.it · inventory file templates (G1641)
- Amazon.es · inventory file templates (G1641)
- Amazon Europe · regional help fallback (G1641)
For a file you already submitted, use Amazon's upload-results and processing-report help (G611). For a catalog report, use the inventory-report help (561). Both pages require your Seller Central session; the current account labels are the source of truth.
If the file contains listing text and you are investigating an environmental-claim notice, use the environmental claims guide for the source context and review boundaries. See the environmental claims checker for supported languages and bulk-removal previews.
FAQ
Choosing an Amazon source file
Which file does ComplyShelf need?
Use a populated Seller Central template when you want its item rows assessed. A blank supported template can instead establish a product-type target, after which you add compatible listings from your ComplyShelf Catalog. A listing report can populate Catalog, but it does not carry the template's compliance values or prove why a listing was blocked.
Can I upload an empty template?
Yes. Its structure can create a target for that product type, but there are no item rows to assess. Add compatible listings from Catalog; the task remains unable to write a listing until it has an actual source or template row for it.
Do you support every Amazon report type?
No, and the table above says which ones. A Category Listings report is not a supported input today. We would rather name that than have it fail in a way that reads as a problem with your file.
Will you fix a broken file structure for me?
No. A file with no technical key row is refused with the reason, not repaired. Rebuilding Amazon's header rows by guesswork is how a correction turns into a second problem.
Workspace and data
Private by default. You choose what to publish.
Your files stay in your workspace and are not shared with other customers. Administrative access is restricted. A product safety page or document link becomes public only when you choose to publish it; you can unpublish or revoke the link. Third-party copies or caches may remain.
You can request deletion at hello@complyshelf.com. The Privacy Policy says workspace content is kept while the account is active and for up to 90 days after closure or a valid deletion request; backups are normally removed within a further 90 days. Legal duties, disputes, incidents and public copies can require different handling. Read the retention details and publication terms.
ComplyShelf is operated by Denys Holda, an individual business established in Italy, registered under REA BI-325108 at Frazione Robiolio 127, 13835 Valdilana (BI), Italy. Contact hello@complyshelf.com. Do not send Seller Central credentials.
Got the right file? See what it is missing.
Upload the Seller Central template for the products you are fixing and get a SKU-by-SKU review of the GPSR data you hold for them.
Check my Amazon file