Product compliance documents belong on the product, not in a shared drive. With SKULaunch, safety data sheets, declarations of conformity and test certificates can be collected from suppliers as part of the product submission, stored against each SKU, and checked for gaps across a whole range. How it is configured depends on your set-up, so the document types and rules are agreed with you at onboarding.
The problem
Compliance paperwork arrives separately from product data, if it arrives at all. Safety data sheets sit in one folder, declarations in another, test certificates in someone's inbox. When an auditor, a trade customer or a marketplace asks for the document behind a product, someone spends an afternoon searching.
The files that do exist are rarely linked to anything. They are named by supplier code, cover a range rather than a SKU, and carry no record of when they were issued. Expired certificates and old revisions go unnoticed until a customer asks for the current one.
Before and after
An illustrative example from an electrical accessories range at a trade distributor.
Before: where the documents live
"SDS" folder with 140 PDFs named by supplier code. Declarations of conformity requested by email in March, 60 per cent returned. No link between any file and the product it covers.
After: the same range in SKULaunch
- Each product holds its SDS, declaration of conformity and test certificate as attached documents
- Document attributes for issue date and standard, filled from the document and reviewed
- A filtered view of every product missing a declaration, by supplier
- Update requests sent to suppliers for missing or outdated documents
How it works in SKULaunch
- Make the documents part of the template. Add document fields, such as SDS and declaration of conformity, to the categories that need them, and mark them mandatory for the supplier where appropriate.
- Collect them with the product. Suppliers upload documents in the same submission as the data, stored against the right SKU in the DAM.
- Track gaps. Filter for products missing a required document and request it from the supplier.
- Keep them current. When a standard or certificate changes, request an update on the affected products.
Which product compliance documents to require, and where
Do not ask for everything everywhere. Your compliance team decides which documents apply to which products. The data job is to turn that decision into category rules, so suppliers are only asked for what is relevant and your gap view stays meaningful. Typical document types include:
- Safety data sheets for chemical and hazardous products
- Declarations of conformity for electrical and many other regulated products
- Test certificates and reports from the laboratory that tested the product
- Performance declarations for categories that require them, such as some construction products
- Material or substance declarations where your customers ask for them
Map each type to the categories it applies to. A cable gland and a cleaning chemical should never see the same document request.
SDS management: versions, dates and coverage
Holding an SDS is not the same as holding the right one. Suppliers revise them, and the revised version often arrives by email to whoever happened to ask. Treat each document as data, not just a file. Capture these details as attributes alongside it:
- Document type
- Issue or revision date
- Review or expiry date, where the document has one
- Standard or regulation referenced
- Language and market
- Issuer, whether manufacturer, brand owner or test house
With dates held as attributes, you can filter for every SDS older than your review period, or every certificate past its expiry, and send update requests to the suppliers concerned. Values such as dates and standards can be extracted from the PDF itself, as covered in extracting data from PDF datasheets, then checked at review.
Common mistakes with supplier compliance documents
- One file, many products. A declaration often covers a whole range. Link it to every SKU it covers, not just the first.
- Wrong variant. A certificate for the 10 A version does not cover the 16 A version. Check the model reference on the document.
- No date captured. Without an issue date you cannot tell current from superseded.
- Inbox storage. If a document only exists in an email thread, it does not exist when the person who received it leaves.
What changes
Every compliance document is one click from the product it covers, gaps are visible before an auditor finds them, and requests to suppliers are tracked rather than lost.
Common questions
How do I collect safety data sheets from suppliers?
Add an SDS field to the supplier template for the categories that need it and mark it mandatory there. Suppliers upload it with the product, so it arrives linked to the right SKU.
Can we see which documents are missing across a supplier?
Yes. Filter by supplier and document field to see every product without the required file.
Can values be taken from the documents?
Yes. Details such as standards, dates and ratings can be extracted from the PDF into attributes for review.
Is compliance document collection part of every set-up?
It depends on how your account and supplier templates are configured. Talk to us to confirm what fits your categories and document types before you plan around it.
Can suppliers share documents through a permanent link?
Uploaded documents are stored as assets on the product. See supplier uploads with permanent links.
Does this make us compliant?
No software does that on its own. SKULaunch makes the documents easier to collect, find and keep current. Compliance decisions stay with your team.
More on supplier data: supplier onboarding software, how to request updates from suppliers, and what the digital product passport means for product data.

.avif)