Documentation Across the Supply Chain: What Flows, to Whom, in What Form

Conformity in a supply chain is a documentation logistics problem. The manufacturer generates the declaration and holds the file. The importer needs the declaration and assured access before placing. The distributor needs to know the declaration exists and accompanies the product's compliance story. The filler or brand owner who becomes the manufacturer in law needs the upstream evidence in file-grade form. Certificates and declarations flow from sub-suppliers upward, each level aggregating the level below into its own file. And every flow needs a contract line specifying documents, versions, timing and update duties - because the regulation obliges the holder, not the sender, when a flow fails.

This guide maps the flows and the confidentiality machinery that keeps commercially sensitive composition data moving without being published.

Sub-supplier to converter: substance and composition declarations in the threshold-naming form, certificates with scopes, change notifications - the inputs of the converter's file. Converter to brand or filler: the packaging's declaration where the converter is the manufacturer, or the evidence pack (composition, assessments, test reports) where the brand declares - the contract must say which legal pattern applies, because the evidence owed differs entirely. Manufacturer to importer: declaration plus file access per the imported-documentation guide's models. Any level to authority: produced by the duty-holder for its level, with the chain's cooperation duties behind it. Draw the map for your chain with names on every arrow; unnamed arrows are where incidents will live.

Composition data is commercially precious and legally necessary at the same time; the system's mature answers are structural. Need-to-know disclosure: the declaration states conformity and the threshold positions without the full formulation (the file holds the formulation; the chain holds the positions). Third-party custody: an independent holder (laboratory, law firm, platform) holds the full dossier and certifies positions to the chain. Sealed annexes in the technical file, opened to authorities and withheld from commercial counterparties. And scheme certificates, which evidence a property without revealing its recipe. Each structure is legitimate; the illegitimate position is refusal without structure. Contracts should name the structure per data class at onboarding, not negotiate it during an authority's request.

Flows fail at format boundaries - the PDF in a portal the counterparty cannot search, the declaration in a spreadsheet's free text, the certificate as a photograph of a document. The direction of travel is structured: declarations and certificates with identifiers, specification versions and validity as data fields; industry platforms emerging for packaging data exchange; the digital product information architecture converging from the labelling side. Businesses specifying flows today should require, at minimum: documents in text form (not images), identifiers matching the specification system, and validity dates as fields. The goal is a chain whose evidence status can be listed by a query - the exception list of the imported-documentation guide, generalised to every level.

A final discipline for every flow on the map: test it on a rhythm. Request the document the flow promises, time the response, check the version against the register, and log the test beside the flow's contract line. Flows degrade silently - contacts leave, portals change, a supplier's compliance team is reorganised - and the test is the only sensor. A chain whose flows are tested quarterly can state its documentation position as a fact; a chain that merely specified its flows in 2026 is stating a hope with contract references. The difference is visible precisely when it matters most.

A converter-to-brand evidence flow, written the way this guide prescribes, fits in a contract schedule of five lines: the documents (composition declaration, grade assessment, content calculation, certificates listed); the versions (current specification, cited on each document); the timing (at first supply, on change within ten working days, certificates on renewal); the structure (positions disclosed, formulation held in third-party custody named); and the test (quarterly production drill, results shared). Five lines, negotiated once. Compare the unspecified flow it replaces - 'supplier will provide all necessary documentation' - which has generated, in incident after incident, exactly the documents that happened to exist, at the speed the incident could not afford.