The EU supplement documentation checklist

The checklist above describes documentation in general terms — certificates of analysis, batch records, ingredient specifications. DAT Supply's actual project documentation set is named explicitly: product specification, ingredient declaration, allergen statement, label and artwork review, batch-release documents, packing list and invoice — each tied to a specific stage of the order rather than delivered as one bundle at the end.

Knowing the names in advance makes it easier to check off what's been received against what's still pending, rather than relying on a general sense that documentation is being handled.

The checklist above references certificates of analysis without distinguishing them from the specification, and the two serve different purposes worth separating clearly. The specification is the fixed reference — format, composition direction and pack configuration — locked early in the project, before production starts.

The Certificate of Analysis is issued after production: a batch-specific document confirming what that particular production run tested at against the locked specification. One document describes the target; the other confirms a single batch's result against it — and a brand should expect both, not one standing in for the other.

Beyond naming the documents, timing matters for planning: specification and label/artwork documents are typically released early in a project, while batch-release documentation follows production and QC sign-off, and packing list and invoice documents arrive around dispatch.

A brand expecting every document on day one of the project is planning against the wrong timeline; building the EU launch schedule around this stage-by-stage release, rather than a single documentation handover, avoids a late surprise close to a planned market-entry date, when there is little room left to fix a gap.

The section above on manufacturer versus brand-owner responsibility is easiest to apply once the document set is named: the specification and ingredient declaration are where the manufacturer states what the product is, while the allergen statement and label review are where the brand owner confirms what goes on pack matches what the manufacturer built.

Treating these as one connected set, rather than a stack of separate paperwork, is what actually closes the documentation gaps this checklist exists to prevent — a specification that doesn't match the final label, or an allergen statement drafted before a late formulation change, are both catchable if the documents are cross-checked against each other rather than reviewed in isolation.

Building this cross-check into a project's own review process — rather than relying on it happening automatically once every document has arrived — is worth setting up before the first document is released, so each new document is checked against the ones already on file as it comes in, instead of everything being reconciled in one pass at the end of the project. A simple running checklist against the named document set above is enough to catch most mismatches before they reach a customs or retailer review, and it turns this checklist from a one-time reference read once at the start of a project into something that stays useful for every document that arrives afterward.