For EU importers, private-label brands and retailers

A product compliance workspace built on your catalog

Group related Products into dossiers, read supported requirement states and keep evidence validity and replacement history alongside your catalog.

Available in the workspace for pilot customers (by request). Request a demo to discuss access, your inputs and supported scope.

Request a demo Try the Amazon file check

Email us to arrange a demo: hello@complyshelf.com

Workspace first; then upload. Free during early access · no payment card. Paid plans will be announced in advance.

Bring: a supported Seller Central template for the self-service Amazon file check only. Assisted dossier pilot terms need a separate agreement.

Private workspace; restricted administrative access. Terms · Privacy

Synthetic example · dossier membership

CATALOG → DOSSIER → REQUIREMENT VIEW

One reviewed scope.
Several catalog Products.

Dossier: SAMPLE-FAMILY · kitchen tools
Current members: SAMPLE-01, SAMPLE-02, SAMPLE-03
Review scope: Each Product and market separately

Illustrative records only. Dossier membership organises work; it does not establish a product's legal status.

Start with the catalog

Shared Products, distinct channel listings.

Bring supported Amazon files into the workspace. An All Listings report builds catalog records; a populated Seller Central template supports the Amazon file check. Products hold reusable records, while their listings retain channel and marketplace context.

This is the catalog foundation of a Product Compliance Management System (PCMS). Choose the supported input for your task.

Dossiers covering many Products

Define the scope. Retain the membership history.

Group an explicitly reviewed family

Create a draft dossier and assign selected Catalog Products after reviewing the selection. A dossier can cover many Products; each Product has at most one current primary dossier. Activation records a workflow decision, even when requirement rows remain unresolved.

Reassignment or removal closes the old membership with a reason and retains its history. Archived Products are counted separately and excluded from current requirement assessment.

Review a successor when scope changes

Supersession starts an empty replacement draft. The predecessor stays current until you review the replacement's Product set and activate it. Replaces and Replaced by links preserve the dossier lineage.

Membership changes do not copy operator assignments, safety decisions or packaging EPR coverage. Those records keep their own scope and review rules.

Read-only requirement view per dossier

Five states, with the recorded basis visible.

Review current members by Product, listing and market. Filter by state or pack, and open View basis for the source, recorded input, original outcome and freshness. Opening the view does not run a new packaging assessment or claims scan.

Satisfied by recorded evidence: A supported pack resolves from recorded input. That basis may be recorded operator data, recorded EPR evidence or a qualifying document. It is not proof of legal compliance.
Missing evidence: Required recorded input is missing. The pack's reason distinguishes a missing operator profile, safety information needed or not recorded, and missing packaging obligations.
Needs review: A supported stored result is stale, operator data is incomplete, safety observations need review, or packaging questions remain unresolved. Review the original reason before acting.
Not applicable: A scoped nonrequirement is recorded: for example, a confirmed destination is not offered, or safety information is not required under the recorded seller statement. It does not mean GPSR law is inapplicable to the Product.
Not assessed by ComplyShelf: The topic, input or scope is unsupported, unreadable or absent, exposure is unknown, or packaging content is overdue for review. Environmental-claims substantiation and other legislation remain not assessed; absence of findings does not resolve them.

**Synthetic example**SAMPLE-FAMILY · selected requirement rowsIllustrative states and bases, not customer data or an assessment of a real product.
Product / scope	Requirement state and basis
SAMPLE-01 GPSR · manufacturer	Satisfied by recorded evidence Recorded operator data resolves the supported manufacturer check. No document is inferred.
SAMPLE-02 GPSR · safety information	Missing evidence Safety information is needed; no qualifying evidence is recorded.
SAMPLE-01 Packaging EPR · Germany	Needs review A previously supported stored result is stale. Its old outcome remains historical.
SAMPLE-03 Packaging EPR · Austria	Not applicable Delivery to this destination is recorded as not offered. This state concerns that market scope.
SAMPLE-02 Environmental claims · substantiation	Not assessed by ComplyShelf Listing-wording review does not assess whether the claim is substantiated.

Evidence library

Validity needs attention. Replacement needs review.

Keep supporting documents with their issued date, issuer and recorded validity. The attention view surfaces active evidence with expiring, expired or unknown validity.

Current: The recorded expiry falls beyond the attention window, or a source and reason record no expiry. This does not establish continued adequacy.
Expiring soon: The recorded valid-until date is today or within the next 30 days. Validity includes the whole valid-until day.
Expired: The recorded valid-until date has passed. Review the evidence; expiry is an attention signal, not a legal conclusion.
Unknown: Validity information has not been recorded. A missing date does not mean no expiry.

Replace document creates a new evidence item and keeps the predecessor's source and history. Replaces and Replaced by links show the replacement chain. Existing assignments and packaging records stay on the old item until explicitly relinked after review.

Evidence validity badges are separate from GPSR and packaging EPR requirement states. Passing a document's validity date does not itself change those pack outcomes.

Supported scope and limits

Operational records, no legal verdict.

The dossier view supports GPSR traceability data for manufacturers, EU Responsible Persons and safety information. Packaging EPR pilot: Germany, Austria, France, Italy and Spain (DE/AT/FR/IT/ES), with country, role and establishment limits. Domestic French, Italian and Spanish business cases and uncertain applicability require review.

Environmental-claims substantiation and other legislation are not assessed by ComplyShelf. Listing-wording findings are separate review candidates. Other legislation not assessed remains visible in every dossier requirement view.

ComplyShelf is not an all-EU-law engine. A dossier's workflow status, recorded evidence, requirement state or absence of findings does not establish legal compliance, permission to sell or Amazon acceptance. Your team decides what to resolve and submit; marketplace outcomes remain separate.

Explore the scoped Amazon GPSR file workflow, five-country packaging EPR pilot and listing-wording review.

Start a conversation

Walk through your catalog and evidence process.

Available in the workspace for pilot customers (by request). Email us to arrange a demo and establish access and scope. Assisted pilot terms need a separate agreement.