Documentation, released by order stage — not as a generic pack.
Every project carries a defined documentation set: specification, ingredient declaration, allergen statement, label and artwork review, batch-release documents, packing list and invoice. Each is released at the right stage inside your client workspace — so what you receive always matches where the order is.
Documentation is released as the order moves — drafted, reviewed, locked, then issued. The batch-release set comes after production and QC release, never before.
Project documentation lives inside your client workspace and is released per stage — not published as a public list.
The documentation set, stage by stage
Each document is released at the point in the order where it applies. The list below is the typical set for a private-label or custom order.
- 01
Product specification
The per-SKU specification — format, composition direction and pack configuration — drafted and then locked early in the project.
After the brief is reviewed.
- 02
Ingredient declaration
The on-pack ingredient declaration, prepared against the locked specification for your target market.
Alongside spec lock.
- 03
Allergen statement
The allergen statement for the SKU, reviewed against the formula and the target-market framework.
Alongside spec lock.
- 04
Label & artwork review
Dieline, on-pack copy and claim wording reviewed against the relevant target-market framework. The brand owner remains responsible for final filings.
In parallel with spec lock.
- 05
Batch-release documents
Batch-specific release documentation, issued after production and QC release — not before. Tied to the produced batch.
After production and QC release.
- 06
Packing list / delivery note
The packing list and delivery note for the shipment, confirming what is leaving and in what configuration.
At dispatch.
- 07
Invoice / receipt
Commercial documents for the order — invoice and receipt — issued through the order workflow.
Per the order.
What these documents actually are
Documentation scope is confirmed against the destination market during the project — these are the terms that come up most often while that scope is being set.
Specification (spec)
The per-SKU reference document — format, composition direction and pack configuration — that formulation, packaging and label content are all checked against. It is drafted early and then locked, so every later document is built against the same fixed reference.
Certificate of Analysis (COA)
A document confirming what a specific batch tested at, against the specification — typically identity, potency and relevant purity or contaminant parameters for that batch. A COA is batch-specific by nature: it describes a production run, not a permanent property of a product line.
Batch documentation
The production and release records tied to one manufacturing run — batch number, production date, QC release and the COA for that run. It is issued after production and QC release, never before, because it documents what was actually made.
Third-party COA and lab testing
Third-party Certificate of Analysis or additional lab testing is included only where it has been ordered or agreed as part of the project — it is not automatic. Scope and applicable testing are confirmed on the order, and any such documents are released through your client workspace once available.
Certification frameworks buyers commonly ask about
Brand teams evaluating a manufacturing partner often build a due-diligence checklist around named frameworks. In general industry terms:
ISO 9001
Quality-management systems — a general standard for consistent process control, not specific to food or supplements.
ISO 22000 / FSSC 22000
Food-safety management systems, built on HACCP principles.
BRCGS / IFS
Retailer-driven global food-safety standards, common requirements from UK and EU retail buyers.
GMP (Good Manufacturing Practice)
Baseline production and hygiene controls that the frameworks above are typically built on top of.
This is background for your own due diligence, not a statement of which frameworks apply to any specific facility or partner. Current certification status for your project is confirmed directly as part of order setup — it is not published as a blanket claim on this page.
Related: cost and pricing drivers, artwork and label process, MOQ and lead times.
Where your order documents live
Specification, allergen statement, label review and batch-release documents are released into your client workspace stage by stage — one register, not an email thread.
- 1 Specification
- 2 Allergen statement
- 3 Label & artwork review
- 4 Batch-release documents
No marketplace, no autoresponder — samples, specs, documentation, production and delivery in one client workspace.
Create account to start your orderDocumentation questions
When do I receive each document?
Documents are released by order stage inside your client workspace. Specification and label documents come early; packing list and invoice come around dispatch; batch-release documents are issued after production and QC release.
Do I automatically get a third-party COA?
No. Third-party COA and additional lab testing are included only when ordered or agreed for the project. Scope is confirmed on the order; it is not automatic.
Where do I find my documents?
Project documentation is released inside your client workspace in the DAT Supply portal, matched to where your order is — not sent as a generic pack up front.
Who is responsible for final regulatory filings?
On-pack claim wording is reviewed against the relevant target-market framework as part of the project, but the brand owner remains the food business operator responsible for final filings in their market.
What does a Certificate of Analysis (COA) actually show?
A COA confirms what a specific production batch tested at, against the specification — typically identity, potency and the relevant purity or contaminant parameters for that batch. It describes one production run, not a standing certification of the product line.
What is the difference between the specification and a COA?
The specification is the fixed reference drafted and locked early in the project — what the product is meant to be. The COA is issued after production and confirms what a specific batch actually tested at against that specification. One is the target; the other is the batch-level result.
What certifications does DAT Supply hold?
This page does not publish a list of held certifications. Buyers evaluating a manufacturing partner often ask about frameworks such as ISO, BRCGS, IFS, FSSC 22000 or GMP-based systems — see the buyer due-diligence section above for what each covers in general terms. Current certification status for a specific facility or project is confirmed directly as part of order setup, and is not asserted on this page.
Is a batch-specific COA the same as a facility certification?
No. A COA is issued per production batch and describes that run only. A facility certification, where one applies, is a separate, facility-level status confirmed directly rather than inferred from a single batch document.
Start an order
Brief your order inside the DAT Supply portal. Project documentation is released into your client workspace stage by stage as the order progresses.