Product connection
Record the Shopify product, title, SKU, available barcode, and supplier so the file cannot be mistaken for another item.
Document workflow guide
Product compliance document checklist for Shopify merchants
A useful document record explains what the file is, which product it supports, who supplied it, how it was reviewed, and when follow-up may be needed.
Use context, not filenames alone
Treat each file as part of a product record
A folder full of PDFs can still leave a merchant asking which product a file covers, whether it is current, and whether anyone reviewed it. Start by connecting the document to a product, supplier, request, and clear purpose.
The document types relevant to a product vary by category and applicable rules. This checklist is a record-management framework, not a universal list of legally required evidence.
Core checklist
Record what your team needs to retrieve later
Document purpose
Use a meaningful type such as declaration, test report, manual, safety data sheet, product-label image, or another merchant-defined category.
Source and request
Keep the supplier submission and the request that collected it connected to the active product record.
Issue date
Record an issue date when the document provides one. An issue date should not be later than the date on which it is entered.
Expiry date
Record an expiry date when the document has one, then use it to prioritise renewal work before the file becomes outdated.
Review decision
Keep submitted, accepted, rejected, and returned states separate. Uploading a file does not make it approved.
Before acceptance
Review the file and its surrounding record
Confirm that the document opens, belongs to the selected product, matches the supplier response, and carries any dates or identifiers your workflow expects. Return or reject the file when replacement or clarification is needed.
Ongoing maintenance
Plan for expiry and replacement
Expiry tracking helps a merchant find follow-up work; it does not prove whether a document is valid or legally sufficient. Retain historical context where appropriate, request a replacement from the assigned supplier, and review the new version as a new submission.
Merchants remain responsible for determining which requirements and evidence apply to their products and markets. ComplyDock stores and organises the records selected by the merchant; it does not certify documents or guarantee regulatory compliance.