Manufacturer · 3 SKUs selected
Exact gap: Manufacturer · record: Acme Manufacturing · mode: fill only.
Amazon EU · High-volume GPSR
Entering manufacturer and EU Responsible Person data one ASIN at a time does not scale. ComplyShelf stores each operator and safety document once, then assigns them to the listings they apply to in a single action — so you fill a detail in once instead of typing it into hundreds of rows.
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.
Illustrative task · synthetic rows
This small example shows the decision before an export: one saved selection, one fill-only action, and a row-level result you can review before submitting anything to Amazon.
Exact gap: Manufacturer · record: Acme Manufacturing · mode: fill only.
Existing values stay untouched; the skipped row is named before the focused update is prepared.
Synthetic example only; the seller chooses the records, confirms columns, and submits the resulting file in Seller Central.
Built for volume
Most GPSR data repeats across your catalog: the same manufacturer covers dozens of products, the same EU Responsible Person covers your whole account, the same safety document applies to a product family. ComplyShelf models these as reusable records you create once and attach in bulk — the opposite of re-typing the same address into every listing.
Manufacturer and EU Responsible Person profiles are created once, validated for the fields GPSR needs, and reused across the catalog.
Safety documents and hosted URLs become durable evidence records you can attach to many products instead of re-uploading.
Filter one exact gap or paste SKUs, save the selection, then use it across operator, evidence, and brand actions. Fill-only is the default; replacement is separately confirmed.
Already have an Amazon template or a failed processing report? Start with the GPSR flat file checker, or use the upload error guide to understand why Amazon rejected a row.
Reviewing listing wording is a separate, seller-decided path. See the Account Health environmental-claim scenario if a notice names one ASIN and you need to find repeated copy across the catalog. See the environmental claims checker for supported languages and bulk-removal previews.
The workflow
Upload the Seller Central template for the products you are fixing, with its rows still in it. ComplyShelf reads its own technical-key row and imports the SKUs into your workspace. Which file should I upload?
See which listings are missing manufacturer, EU Responsible Person, evidence URL, or catalog identity — with open-gap counts.
Keep one saved selection across Manufacturer, Responsible Person, Documents, and Brand. Fill-only preserves existing values; a separate replace choice shows before, after, and skipped rows first.
Take the readiness report to work from, or the update file to submit. Every generated file is kept as a batch, and the report Amazon returns marks each row accepted, rejected or needs-fix. The difference between the two files.
Two different files
These are not the same thing and are not produced at the same point. One helps you see where you stand; the other is what you hand to Amazon.
Available as soon as listings are imported. Mirrors whatever you have filtered on screen — SKU, ASIN, marketplace, catalog readiness, GPSR data, export eligibility and the Amazon result recorded so far. It is shaped for working through gaps, not for uploading: Seller Central will not take it.
Available once you have confirmed at least one column ComplyShelf may write to for that product type. It reproduces the preamble and technical-key row of the template you uploaded, with the same delimiter, and writes rows in Amazon's partial-update mode. Rows with no value to contribute are left out and listed with the reason. You upload it in Seller Central yourself.
Two limits worth knowing before you rely on it. It is a delimited update file built from your own template — not your workbook handed back as .xlsx. And if one upload covered several product types, the update may come as more than one file: ComplyShelf splits by product type unless the templates are compatible, and names the reason. A combined multi-type file is deliberately held back until a real seller account confirms Amazon accepts one.
Nothing is sent to Amazon on your behalf. There is no SP-API write-back, ComplyShelf holds no Seller Central credentials, and every submission is one you make and can inspect first.
Where bulk stops
Assigning in bulk saves the typing, not the judgement. A manufacturer or an EU Responsible Person is correct for a particular product because of who actually made it and who actually takes responsibility for it — not because a group of listings share a brand, a supplier or a product type. Sharing a brand is a convenient way to select rows; it is not evidence that the same operator or the same safety document belongs on all of them.
So the selection is yours to make. ComplyShelf shows which listings are missing what, lets you apply one record to the ones you have chosen, and records who assigned what and when — and it will not spread a record across a catalog on the strength of a shared field.
Free, manual gap report
Email an Amazon listing export, or the Seller Central template for the products you are fixing, and a person will read it and write back: which SKUs are affected, what that particular file can and cannot tell us, and whether this workflow suits your catalog at all. No account access needed. We do not publish a response time or a number of free reads, because neither has been committed to — it is one person reading a file.
Send only the listing export. Never send passwords or Seller Central credentials.
FAQ
Yes. Create a Manufacturer and an EU Responsible Person once as reusable records, then assign them to a saved selection in the fix task. The same selection remains available for Documents and Brand. Fill-only is the default, and replacing an existing value is a separate confirmed action. You then preview the focused update, export it, and submit it in Seller Central yourself.
Yes. Once you have confirmed at least one column it may write to, it produces an update file in the shape of the template you uploaded — same preamble, same technical-key row, same delimiter, rows in Amazon's partial-update mode. It is a delimited file rather than your workbook handed back as .xlsx, and it holds only the rows it has values for. A separate CSV or TSV readiness report is for working through gaps and is not meant for uploading. See how the two differ.
Because writing into the wrong Amazon column is worse than writing nothing. ComplyShelf finds the candidate columns in your file and suggests a match where it is confident, but it never enables a write on its own. Until you confirm a column for that product type, no update file is produced at all — you are told there is nothing it is allowed to write rather than handed an empty file.
They remain in the retained original file and raw row, and ComplyShelf never guesses a mapping for them. The focused update contains the SKU key, partial-update mode, and confirmed supported columns it can write; it does not promise to emit every unknown source column. Deliberately unsupported fields such as a DSA responsible party or safety attestation stay visible in the source without being interpreted.
No. ComplyShelf holds no Seller Central credentials and writes nothing to your account. You upload the template, you review what it prepares, and you submit it yourself. If you attach the report Amazon returns, the per-SKU outcome is recorded against the rows you sent.
Filter listings by what they are missing, select many at once, and apply a reusable manufacturer, EU Responsible Person or evidence record to the whole selection in one action. The limits that exist are on the file you upload, not on the catalog: up to 25 MB, and a worksheet is read in bounded passes rather than loaded into memory. A worksheet holding several product types is imported as one confirmed run and split into a group per type.
No. ComplyShelf is an operational tool, not a law firm or an EU Responsible Person service, and it does not guarantee legal compliance. You remain responsible for the accuracy of the data you submit to Amazon.
Before you send a file
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.
Record your operators and documents once, see which listings are still missing them, and prepare the update file for the rows that are ready to go.
Start my GPSR review