One Dossier per SKU: A Compliance File Template for Pet Toy Buyers

It arrives at 11 p.m., because marketplace case messages always do: "Please provide documentation supporting the material safety of this item within 7 days." The seller who owns that SKU has two futures. In one, the test reports, supplier declarations and label proofs assemble themselves from a folder built months ago, and the reply goes out the next morning. In the other, the same documents exist — somewhere — in a supplier's inbox, a downloads folder and a dead laptop. The difference between the two futures is not compliance knowledge. It is filing.

This article provides the filing: a one-dossier-per-SKU template, the ownership split between buyer and supplier, retention rules, and the triggers that keep the file true.

Why a Dossier, Not a Drawer

Most sellers keep compliance papers — that was never the problem. They keep them by event: the folder from that audit, the email thread from that launch, the PDF from that trade show. Such archives answer historians, not case managers. A case manager asks about a SKU at 11 p.m. and expects one reply containing everything relevant to that SKU for that market. The unit of retrieval is the SKU, so the unit of filing must be the SKU too.

A per-SKU dossier also pays off in quieter moments: retailer onboarding, port queries, insurance applications, and the sale of the brand itself — due diligence now routinely includes spot-checking whether a random SKU's file assembles in an afternoon. A drawer of event folders fails that test; six folders per SKU pass it every time.

The Folder Template

The matrix in folder 03 deserves its own habit: one row per report — standard, material, color, date, applicant — so coverage gaps are visible at a glance. The reading discipline behind those rows is covered in our five red flags article; the artwork versioning in folder 04 follows the system described in the labeling article.

Who Holds What

The ownership split follows a single rule: whoever generates a document holds the original, and whoever answers for the market holds a current copy. Suppliers generate the material-side papers — datasheets, factory reports, batch inspection records — and a serious supplier will hand these over per order without friction. Buyers generate the market side: label approvals, responsible-person agreements, platform correspondence. The buyer also owns the master index, because the buyer is the only party that can see the whole SKU.

One caution for sellers working through agents: an agent who cannot produce the factory-level documents behind a report is telling you where the file's weakest link is. Ask early, in writing, while the relationship is friendly — documents are cheapest to request before they are urgently needed. When we take on a private-label program, the dossier handover is part of the delivery: each shipment arrives with its batch records and report updates, so the buyer's file never drifts out of date.

Naming and Version Discipline

A dossier is only as good as its findability. Three conventions, applied without exception, do the work:

• One root per SKU. Folder names carry the SKU code, and nothing lives outside its root — no "general compliance" folder where documents go to become unfindable.
• Files named by pattern. SKU_document type_market_version_date, in that order — so a directory listing sorts itself into a report matrix without effort.
• Versions never overwrite. New label version, new file; superseded versions stay, marked as such. Auditors ask what applied when, and only retained history can answer.

The index page on top of each dossier lists what should exist and what is current — a one-page table that turns "do we have this?" from an afternoon of searching into a glance.

Refresh Triggers and the Annual Review

Files rot quietly: everything in the folder was true once. Four events invalidate parts of a dossier and should be wired into ordering and design workflows — any change of compound, colorant, sub-supplier or plasticizer (folder 02 and 03); any label or claim revision (folder 04); any new export market (folder 05); and any update to the regulatory lists your screens benchmark against, which is nobody's fault and everybody's problem. On top of event triggers, stable SKUs get an annual review: a morning per year per SKU to re-check dates, confirm the supplier still stands behind each document, and archive the confirmation.

Frequently Asked Questions