Made in Yangzhou · Shipped from Yiwu — Pet Toy Supply at the Source
Archive box filled with tabbed folders standing on an office shelf
Home / Blog / SKU Dossier

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

March 19, 2026Standards & ComplianceAbout 11 min readTOYORIGIN Sourcing Team

Key Takeaways

  • The unit of compliance is the SKU, not the company: build one dossier per SKU so any request can be answered in hours, not weeks.
  • Six folders cover it: identity, supplier declarations, testing, labels and artwork, market files, and batch records.
  • Documents split by origin: suppliers hold what they generate; buyers hold what their market and platforms demand — plus the master index.
  • Retention outlives the listing: golden samples three per batch for 24 months is a workable factory discipline; documents live even longer.
  • Update on change, review annually: material changes, label revisions and list updates each invalidate parts of the file.

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

FolderContentsHeld byRefresh trigger
01 IdentitySKU sheet, product photos, bill of materials with material names, packaging versionsBuyer, sourced from supplierAny product or packaging change
02 DeclarationsCompound datasheets, fabric and fill declarations, restricted-substance confirmations, supplier QA agreementSupplier issues, buyer archivesSupplier or material change
03 TestingReport matrix by standard, material and color; latest reports with dates; lab accreditation copiesSupplier issues, buyer archivesNew color, material change, 12-month age
04 Labels and ArtworkDielines and artwork per market, approval records, print vendor versionsBuyerAny label or claim revision
05 Market FilesPer-market items: responsible-person agreement, risk analysis, marketplace correspondence and responsesBuyerNew market or regulatory update
06 Batch RecordsGolden sample log, AQL inspection reports, retention sample statusSupplier executes, buyer spot-checksEvery production batch

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.

Overhead view of an open ring binder with tabbed dividers and a small dog toy on the desk
Six folders per SKU, one index page on top: the whole system fits in a binder or a cloud folder.

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.

Person typing on a laptop in a bright office with organized document trays
Answering a case manager at 11 p.m. is not heroics — it is an index page and six folders, maintained on schedule.
Compliance note: a dossier is evidence management, not a substitute for compliance: a perfectly filed report of the wrong test proves nothing, and no folder makes a mislabeled product legal. Build the file around the requirements of each destination market, keep the voluntary-versus-mandatory framing accurate in every document, and treat the dossier as the contract you and your supplier both sign up to — in practice as well as on paper.

Frequently Asked Questions

FAQ

Who should keep the compliance dossier, the buyer or the supplier?
The split follows the document's origin. Suppliers hold what they generate: compound datasheets, factory-level test reports, production records. Buyers hold what their market demands: label artwork versions, marketplace correspondence, the responsible-person agreement, and the master index that ties it all to the SKU. Never rely on holding only half — your ability to produce the whole file within hours is the point.
How long should compliance records be kept?
Longer than the product's selling life. Batch samples and their inspection records should span at least the liability tail of the goods; a common factory discipline is keeping three golden samples per SKU per batch for 24 months. Documents — reports, declarations, artwork approvals — live for the product's lifetime plus the period claims or disputes could arise.
What events force a dossier update?
Any change that would make an existing document describe something else: a compound or colorant change, a new sub-supplier, a label revision, a new export market, or a regulatory list update. Add a scheduled annual review for stable SKUs, because lists such as the SVHC candidate list move even when your product does not.
What do marketplace case managers actually ask to see?
In practice: evidence of material safety for the SKU (test reports matching the supplier), label and packaging images proving the claims, support for any performance or durability claim, and a contactable responsible entity where the market requires one. Speed matters as much as substance — a complete answer within days routinely closes a case that a perfect answer in three weeks escalates.

Want your first SKU dossier built for you?

Send the SKU list — we deliver the folder skeleton pre-filled with our documents per shipment, and keep it current with every order.