EU Compliance & Accessibility Workspace
Use one workflow for GPSR product evidence and EAA accessibility readiness signals.
The combined workspace does not prove product safety, GPSR compliance, EAA compliance, or WCAG conformance.
Reviewed core collection
GPSR, ecommerce evidence and EAA resource hub
These 100 pages are the maintained public core. Each page has a distinct task, a fictional worked example, explicit decision boundaries and direct primary-source links.
Free supplier evidence toolkit
Start with an editable evidence tracker and supplier-request template. No signup is required.
Preview and download the CSV and request templateworkspace
Unified workspace
Start with the complete product-evidence and accessibility workflow.
gpsr-task
GPSR evidence tasks
Review operator, traceability, warning, label, supplier and Evidence Pack jobs.
EU Product Compliance Checker
Paste a product URL and generate a product listing readiness workflow with evidence tasks.
Only visible page signals and supplied evidence are assessed; product-specific legislation still needs specialist review.
GPSR Compliance Checker
Run a product-page readiness check for common GPSR evidence and listing gaps.
A readiness score is a triage signal, not a certification or a legal conclusion.
GPSR Product Listing Checker
Use a product page URL to find listing gaps and generate evidence-management outputs.
The checker cannot inspect unpublished marketplace dashboards or physical packaging.
EU Responsible Person Checker
Identify missing EU responsible person details and turn them into supplier evidence requests.
An address alone does not establish that an organization is the valid responsible person.
Manufacturer Information Checker
Find manufacturer information gaps and generate a supplier request email.
A brand, distributor or marketplace seller must not be relabelled as manufacturer without evidence.
Product Safety Warning Generator
Prepare source-warning and translation-review blocks without inventing generic safety instructions.
ComplyFolio does not create product-specific hazards or substitute generic wording for verified warnings.
EU Product Label Generator
Create a draft label structure from extracted product fields and missing supplier data.
A generated draft is not print approval and does not replace product-specific labelling rules.
Supplier Compliance Email Generator
Turn missing product compliance evidence into a supplier email and upload link workflow.
Supplier delivery does not prove validity; identity, scope, model match and document status need review.
Product Compliance Evidence Pack
Export a SKU-level evidence pack zip for manual compliance review and supplier follow-up.
An Evidence Pack improves traceability and response readiness; it cannot prevent complaints, takedowns, recalls or enforcement.
GPSR Digital Products Scope Guide
Do not classify every digital download as automatically covered or exempt; document the product, delivery model, software connection, and target market first.
The label 'digital product' alone is not enough to decide whether GPSR applies or does not apply.
GPSR Business Address and Privacy Guide
GPSR distance-sale offers require postal and electronic contact details; whether a PO Box or service address is sufficient depends on the operator role and applicable rules.
ComplyFolio does not claim that every PO box, virtual office or service address satisfies GPSR duties.
Product Traceability Checker
Find missing traceability fields and generate supplier evidence tasks.
Which identifier is legally sufficient depends on the product and evidence; the checker only surfaces signals and conflicts.
GPSR Online Offer Checker
Check what a customer can see before purchase, then separate missing online-offer information from evidence that remains private.
ComplyFolio reports observable signals and cannot decide whether a particular product or presentation satisfies every applicable rule.
GPSR Product Page Requirements Guide
Use a structured page checklist instead of mixing public listing information with certificates and technical documents.
The matrix is a review aid, not a universal list for every product category or Member State.
GPSR Listing Rejected Checklist
Do not guess the rejection reason: preserve the exact platform message, inspect the live offer, and map each requested field to evidence.
ComplyFolio cannot infer the rejection reason, reverse a restriction or guarantee marketplace reinstatement.
GPSR Supplier Document Checklist
Request only documents relevant to the product and record which file supports each listing or label statement.
Receiving a document does not establish its authenticity, scope, validity or applicability to the product.
GPSR Instructions and Manual Checker
Confirm that instructions match the exact model and target market; a generic or unrelated manual should remain an unresolved evidence item.
ComplyFolio can organize the comparison but cannot approve technical instructions or translations.
GPSR Technical Document Organizer
Use a manifest that shows what each file supports instead of storing an unlabelled folder of supplier PDFs.
Organization and traceability do not validate a document or replace a qualified product assessment.
platform-gpsr
Ecommerce platform workflows
Apply the same evidence boundary to Shopify, Etsy, Amazon, eBay, WooCommerce and multi-channel public listings.
Shopify GPSR Compliance Checker
Review Shopify product pages for GPSR readiness and generate platform-ready compliance fields.
The checker cannot see private Shopify admin fields, app settings or submission status.
Shopify GPSR Metafields CSV Generator
Generate a review-ready CSV row for an existing Shopify product without inventing missing safety information.
Import behavior depends on the merchant's Shopify catalog and metafield definitions; review the preview before upload.
Etsy GPSR Compliance Checker
Use product links to organize Etsy GPSR readiness tasks and evidence.
Private Etsy account fields, platform moderation and handmade-product legal classification require separate review.
Amazon GPSR Compliance Checker
Review a live Amazon listing, separate visible page gaps from private supplier evidence, and create a manual follow-up workflow.
ComplyFolio cannot inspect Seller Central, confirm an ASIN submission or predict Amazon moderation decisions.
eBay GPSR Compliance Checker
Review a live eBay listing, separate visible page gaps from private supplier evidence, and create a manual follow-up workflow.
A public scan cannot confirm eBay account status, field acceptance or whether a hidden listing will be restored.
WooCommerce GPSR Compliance Checker
Review a live WooCommerce listing, separate visible page gaps from private supplier evidence, and create a manual follow-up workflow.
ComplyFolio cannot inspect WordPress admin, plugin configuration or unpublished custom fields.
Online Marketplace GPSR Compliance Checker
Review a live Online Marketplace listing, separate visible page gaps from private supplier evidence, and create a manual follow-up workflow.
The matrix compares public evidence; it does not determine platform approval or legal compliance.
supplier-evidence
Supplier evidence review
Resolve document mismatches, incomplete files, translations, access and reviewer handoffs.
Resolve a supplier document model mismatch
Keep a mismatched document pending until the supplier connects its model identifier to the exact item being sold. A similar photograph or filename cannot establish coverage.
A mapping letter alone does not validate testing or extend a report beyond its assessed scope.
Review an incomplete supplier test report
Request the complete report and check its pagination, appendices and identified specimen. A cover sheet or pass summary cannot replace the missing findings and scope.
Receiving all pages establishes completeness only; applicability and technical adequacy need separate assessment.
Track supplier document revisions
Give each received revision its own record and preserve the prior version. Use the supplier's change explanation to decide which listings, labels and reviews need reopening.
A newer date does not establish that the replacement wording is correct or applicable to all stock.
Redact supplier evidence without losing scope
Create a separate sharing copy and keep the original in restricted storage. Preserve the product identity, scope and findings needed by the receiving reviewer.
Redaction is not authorization to disclose; document rights and recipient access still require review.
Review supplier evidence in another language
Preserve the source document and pair it with a translation that identifies uncertain technical terms. Do not turn an unreviewed translation into approved warning copy.
Translation does not establish document authenticity or replace product-specific safety review.
Triage questionable supplier documents
Separate signs requiring verification from an allegation of fraud. Check issuer, report references and consistency through a verified official contact route.
Visual appearance, a logo or a successful link check cannot establish authenticity by itself.
Follow up on missing supplier evidence
Send a gap-specific follow-up that lists the exact files, product identifiers and decision waiting on them. Silence should remain an unresolved evidence status.
A deadline in a request does not create a legal obligation or make missing evidence acceptable.
Build a supplier document acceptance log
Record received, pending review, accepted for a defined purpose and rejected as separate states. The log should explain the scope of every acceptance decision.
Accepted in this workflow means accepted for the recorded review purpose, not certified legally compliant.
Name supplier files for reliable retrieval
Use stable product and document identifiers in filenames, while keeping status and review history in a register. Avoid relying on words such as final or approved alone.
A descriptive name helps retrieval but says nothing about document validity or approval.
Review access to supplier evidence uploads
Treat upload permission, file receipt and document acceptance as different controls. Test the intended recipient's access and the expiry behavior using non-sensitive samples.
This manual workflow does not promise that every storage provider or product plan supports the same controls.
Hand over supplier evidence between reviewers
Transfer open questions and decision context with the files. A successor should be able to explain which evidence is current and which product decisions remain blocked.
A handover does not transfer legal roles or remove the need for a competent reviewer.
Prioritize a supplier evidence request
Order requests by the decision they unblock and the consequence of uncertainty. Collecting many low-value files should not hide missing identity or product-specific information.
Priority is an operational judgment; urgency does not establish which legal requirements apply.
traceability
Product and stock traceability
Connect variants, batches, components, revisions and stock transitions to their evidence.
Build a product variant evidence matrix
Map evidence to each variant using the characteristics that can affect coverage. A shared product family name is not enough to assume one document covers every option.
Technical coverage across variants requires qualified assessment; this matrix records the reasoning rather than deciding it.
Create a batch label photo log
Photograph identifiable physical stock and connect each image to the batch, date and product record. Keep unreadable or partial images as failed evidence captures.
A sample photo does not prove that every unit in a batch carries the same label.
Map storefront SKUs to manufacturer models
Keep merchant SKUs and manufacturer model identifiers in separate fields, connected by evidence. Do not overwrite one with the other to make documents appear consistent.
An internal crosswalk cannot expand a report's scope or replace required physical identifiers.
Review evidence when a supplier changes
Reopen the product record when sourcing changes, even if the storefront SKU remains the same. Compare the new item and its evidence with the version customers were previously offered.
Visual similarity does not establish equivalent safety or documentation coverage.
Map evidence for replacement parts
Identify the intended host product and compatible revision before associating evidence with a replacement part. Compatibility claims need their own supporting source.
This workflow does not establish technical safety of a part or authorize modified product combinations.
Organize evidence for a product bundle
List every bundle component and the claims made about their combined use. Component evidence may leave the combined configuration unresolved.
Separate component documents do not by themselves prove the safety of a combined product or bundle.
Track product material changes
Record material changes against the affected model and production period, then identify the evidence and claims that need reassessment. Treat the change as a review trigger.
The log cannot determine chemical safety or which tests a changed material requires.
Match instruction versions to shipped products
Connect each instruction version to the product revisions and markets it covers. A current download should not silently replace the only instructions for older stock.
Matching a manual to a model does not establish that its instructions are adequate or legally sufficient.
Review identity records for private-label products
Document who designs, manufactures, brands and places the item on the market before drafting operator details. A purchase invoice alone may not resolve the legal role.
Applying a trademark can affect responsibilities; this worksheet does not decide the resulting legal classification.
Plan a stock cutover after a product update
Define which evidence and listing version belongs to stock before and after a change. Keep the cutover observable through batch or receiving records.
A stock transition plan does not decide whether older stock may continue to be sold.
Create a product sample evidence register
Record which physical sample was examined and how it relates to saleable stock. Keep sample limitations visible when using photos or review notes as evidence.
A sample review cannot establish conformity or consistency of all production units.
Archive evidence for discontinued products
Keep discontinued product records distinguishable from active catalog evidence while preserving the relationships needed for later inquiries. Define retention with the appropriate reviewer.
Retention periods and continuing duties depend on applicable rules and facts; this guide does not set a universal deadline.
listing-operations
Listing publication and change control
Test fields, translations, feeds, mobile visibility and publication outcomes.
Review a product warning translation
Translate from an identified, approved source and preserve its version. Check meaning, units and placement with a competent reviewer before publishing the translated warning.
Translation review does not create the underlying safety assessment or determine national language requirements.
Check safety information on mobile product pages
Review whether the relevant warning remains available and understandable on the rendered mobile offer. Storefront configuration alone does not show what a customer can actually see.
A visibility test does not establish the completeness or legal adequacy of the warning itself.
Synchronize operator details across selling channels
Maintain a verified source record for operator information, then compare its rendered value across each selling channel. Track differences before overwriting live fields.
A successful synchronization does not establish that an organization holds the claimed legal role.
Capture evidence before and after a listing change
Save a dated comparison that shows the exact field changed, the supporting source and the rendered outcome. Keep account submission and public visibility separate.
A public update does not prove marketplace approval or completeness of all required information.
Diagnose stale safety information in a storefront cache
Compare the authoritative content record with the actual response customers receive. Check variants, locales and cached fragments before concluding an edit failed.
Cache clearance does not validate warning content or guarantee every downstream copy has updated.
Map product evidence fields into a sales feed
Document how verified product information moves from the source catalog into the feed and then the visible offer. Test missing values and transformations explicitly.
Feed acceptance is a technical result and does not establish legal adequacy or marketplace approval.
QA a bulk update to product evidence fields
Use a bounded sample, an identifier match check and a recovery plan before updating a catalog. Verify the rendered result on more than the first imported row.
This worksheet does not operate an import or promise a particular platform's overwrite behavior.
Prepare an evidence response to a listing rejection
Respond to the actual rejection reason with the relevant corrected fields and supporting files. Keep the platform's decision separate from your internal evidence status.
This guide cannot predict reinstatement or interpret private platform decisions without their actual wording.
Test a product safety information accordion
Check whether customers can find, open and read a collapsed safety-information section using keyboard and assistive technology. Test content presence separately from interaction behavior.
Passing this component test does not establish complete page accessibility or legal sufficiency of the safety text.
Check links to product instruction PDFs
Verify that the public instruction link resolves to the intended model and language without unnecessary access barriers. A successful HTTP response does not identify the document's contents.
This check does not evaluate whether the instructions themselves satisfy all product-specific requirements.
Release updated product safety content
Treat a safety-content edit as a controlled release with a source, reviewer and production check. Coordinate the wording across affected labels, instructions and online offers.
Release completion is an operational status, not a finding that the product or wording is legally compliant.
Separate public listing information from private evidence
Decide what belongs in the customer-facing offer and what belongs in a restricted evidence file. Use a review-purpose decision rather than publishing the whole supplier folder.
The appropriate publication scope depends on applicable requirements and rights; the worksheet does not authorize disclosure.
evidence-operations
Evidence review operations
Maintain manifests, owners, decisions, sharing boundaries and retrievable archives.
Check an Evidence Pack manifest
List what the pack contains, which product version it covers and what remains unresolved. Verify the manifest against the actual exported files before sharing it.
A complete manifest describes the pack; it does not establish the validity of its contents.
Assign owners to product evidence tasks
Give each evidence gap one accountable owner and a clear next action. Separate supplier collection, technical review and publication responsibilities where they differ.
Internal task ownership does not determine economic-operator responsibilities under applicable law.
Define evidence review statuses
Use statuses that distinguish missing evidence, receipt, review and an accepted use. Make transitions depend on an observable event and a recorded reason.
A workflow status must not be presented as a regulatory certificate or universal compliance judgment.
Define triggers for reopening an evidence review
Reopen the relevant review when a source fact changes, then identify the affected decisions. Use explicit triggers instead of assuming a completed checklist remains current indefinitely.
A trigger list is not exhaustive and does not replace ongoing product-specific duties.
Run a product evidence review meeting
Use the meeting to resolve named decisions rather than recount file collection. Share the evidence gaps in advance and record owners for every unresolved item.
Meeting agreement cannot replace specialist review or establish legal compliance by consensus.
Check an Evidence Pack before sharing
Review the intended recipient, scope and access route before sending an evidence export. Share only what serves the documented purpose and preserve the sent version.
This checklist does not itself authorize sending data or determine contractual confidentiality obligations.
Check evidence file integrity during handoff
Compare file references or cryptographic checksums before and after transfer to detect accidental changes. Treat matching files as an integrity result, not proof of truth.
A checksum detects byte differences; it does not authenticate an issuer or validate document claims.
Record a correction to product evidence
Correct the current record while preserving what changed, why it changed and which downstream decisions need review. Avoid silently replacing a wrong value.
A correction log does not erase earlier publication or decide whether further notifications are required.
Plan a catalog evidence review sample
Choose a sample that covers meaningful differences in supplier, product type and evidence status. Record what the sample cannot establish about the remaining catalog.
Sampling is an operational prioritization method and does not prove compliance of unsampled products.
Distinguish document expiry from review dates
Keep a document's stated validity, your internal review date and a follow-up reminder in separate fields. Do not invent an expiry date for a document that has none.
The correct retention or validity rules depend on the document and applicable requirements.
Test access to an evidence archive
Check that authorized reviewers can retrieve the relevant historical record and that unrelated users cannot. Test access with sample records and preserve a minimal result log.
A sample access test cannot establish complete storage security or authorize broader sharing.
Prepare evidence for a product information inquiry
Answer the specific product question using verified information and a documented scope. Keep safety concerns on the appropriate escalation path rather than treating them as routine content requests.
This worksheet does not diagnose hazards, replace required reporting or authorize a customer response.
accessibility
EAA and accessibility
Separate automated page signals from the manual testing needed for real journeys.
EAA Accessibility Checker
Check a single page for common accessibility issues and get a readiness-oriented report.
A single automated scan cannot establish EAA compliance or WCAG conformance.
EAA Ecommerce Accessibility Checklist
Combine automated page checks with keyboard, screen-reader, zoom, error-recovery, and end-to-end purchase testing.
A checklist or automated scan cannot establish EAA compliance or WCAG conformance for the complete service.
Product Page Accessibility Checker
Use an automated product-page scan to find common issues, then manually test variants, galleries, accordions, and add-to-cart behavior.
Passing automated rules on one URL does not prove that every product page or interaction is accessible.
Accessible Checkout Checklist
Checkout requires scripted and manual journey testing; a public product-page scan cannot verify private payment and account steps.
Public URL automation cannot verify private account, fraud, third-party payment or assistive-technology behavior by itself.
Mobile Ecommerce Accessibility Checker
Use automated signals as a starting point, then test real mobile viewport, touch, zoom, screen reader, and orientation behavior.
Desktop results cannot establish mobile accessibility, and mobile guidance remains part of WCAG rather than a separate certification.
Accessibility Evidence Report
Create a transparent evidence record that distinguishes automated signals from manual testing and unresolved accessibility barriers.
The report documents work performed; it is not an accessibility certificate or a guarantee that no barrier remains.
Test an accessible checkout error summary
Submit a checkout form with deliberate errors and verify that the summary identifies the problems and leads to the relevant fields. Test focus and announcements as well as appearance.
Passing this test does not establish full checkout accessibility or EAA applicability.
Test address autocomplete accessibility
Check whether address suggestions can be reached, understood and selected without a mouse. Include a manual-entry path when the suggested address is wrong or unavailable.
Address validation accuracy and service coverage require separate review from accessibility.
Test a third-party payment iframe for accessibility
Review the embedded payment journey in its actual checkout context. Record provider-owned barriers and local integration issues separately so each has a clear owner.
A merchant cannot infer full provider conformance from one test or modify a third-party component directly.
Test checkout timeout warnings and recovery
Check whether users are warned about time limits and can preserve or recover their work where the applicable requirements call for it. Test the actual expired-session path.
The applicable timing exceptions and security constraints need case-specific assessment.
Test shopping cart update announcements
Change quantity, remove an item and apply a discount while checking that meaningful updates are perceivable without moving focus unnecessarily. Verify totals and messages together.
Correct announcements do not validate pricing logic or establish overall cart accessibility.
Test product variant selection with a keyboard
Select each type of option without a pointer and check that its name, selected state and availability are understandable. Verify that price and purchase controls update consistently.
This review does not determine whether a variant's product information or evidence is correct.
Test product image zoom accessibility
Review how the zoom viewer opens, receives focus and closes, and whether equivalent product information remains available without relying on magnification alone.
A working zoom control does not make the image's information accessible by itself.
Check whether a cookie banner blocks checkout access
Test consent choices and dismissal using the same viewport and keyboard path as checkout. Record overlays that obscure fields, trap focus or prevent a user from proceeding.
This test assesses access barriers, not the legal validity of consent or tracking choices.
Check language changes in an online store
Compare the page's declared language with its actual content and any passages in another language. Include translated product details, validation messages and embedded controls.
Correct language markup does not establish translation quality or satisfy all market-specific language duties.
Test store pages at zoom and narrow widths
Check whether product and checkout content remains readable and operable when enlarged or reflowed. Record horizontal scrolling, clipped controls and sticky elements that cover content.
This test is part of a broader accessibility evaluation and does not establish conformance alone.
Check whether sticky elements hide keyboard focus
Follow the keyboard path while observing whether focused controls remain visible beneath headers, drawers and purchase bars. Record the exact overlay and scroll position when focus is obscured.
A visible focus test does not assess every keyboard interaction or all WCAG criteria.
Review touch targets in a mobile store
Check compact controls such as quantity steppers, swatches and dismiss buttons for usable target size and spacing. Record the criterion and any exception considered by the reviewer.
The correct conformance assessment depends on the applicable criterion, exceptions and tested implementation.
Test accessible sign-in during checkout
Review password entry, recovery and any cognitive or interaction barriers in the required sign-in path. Check support for password managers and pasting where relevant.
Authentication security and applicable accessibility exceptions need separate, coordinated review.
Test discount-code errors for accessibility
Make discount success and failure understandable without relying on color or a silent total change. Preserve the entered code when correction is possible.
This test does not establish the correctness or fairness of a promotion's commercial terms.
Test accessible no-results states in store search
Check whether an empty result is announced and offers understandable recovery options. Keep the user's query available for editing and test filter combinations.
A usable empty state does not establish the relevance or accessibility of all search results.
Review downloadable product documents for accessibility
Check whether essential information in downloadable documents can be read and navigated, and provide an appropriate alternative when needed. A browser page scan cannot inspect every document barrier.
This worksheet is not a PDF conformance validator or a complete legal assessment.
Test the accessibility support contact route
Follow the published accessibility contact route as a user would, including forms, confirmation and response handling. Record whether people can report barriers without encountering another barrier.
A working contact route does not compensate for inaccessible services or define statutory response duties.
Build a store accessibility regression checklist
Turn previously fixed barriers into reproducible checks tied to the affected component and user journey. Reuse representative states after theme, app or content changes.
A regression pass covers the selected checks only and does not establish complete accessibility.
Record a store screen-reader test
Capture the task, assistive-technology setup and observed announcements so another reviewer can reproduce the finding. Avoid treating one combination as representative of every user.
One assistive-technology test does not establish universal compatibility or full conformance.
Hand off an accessibility defect to a vendor
Send a minimal reproducible case showing the affected integration and user task. Distinguish vendor behavior from local theme or configuration issues before assigning responsibility.
A vendor acknowledgement or patch note is not evidence that the store integration is fixed.
Quality policy
Distinct tasks, usable worksheets and explicit limits.
Pages outside this reviewed core remain available for improvement but are temporarily excluded from indexing and the sitemap. New pages enter this hub only after they add distinct user value, evidence and source coverage.
Read the editorial and correction standard · See what changed