Regulatory & Compliance Documentation — Installation & Integration Guide

Where Compliance Documentation Breaks Down in Practice #

There are three observable failure patterns we encounter with brand partners integrating compliance documentation into an active production programme for the first time.

The first is document-to-material mismatch. The Declaration of Conformity (DoC) or Safety Data Sheet (SDS) on file references a substrate formulation that has since been updated by the raw material supplier. The packaging looks identical. The test report is genuine. But the ink pigment lot or laminate adhesive changed in the last 18 months, and nobody updated the supporting documentation chain.

The second is version drift under GB/T revision cycles. Chinese national standards — particularly GB/T 10004 (flexible packaging laminates) and GB 9685 (food-contact additive limits) — update on irregular cycles. A DoC written against GB 9685-2016 may not satisfy an EU importer who is cross-referencing against EU Regulation 10/2011 Annex I, because the permitted substance lists diverge in 23 substance entries as of the 2023 amendment.

The third is integration sequencing failure: the compliance document is available, but it is stored separately from the production traveller (what we internally call the Job Compliance Packet, or JCP). At dispatch, the pick-and-pack team attaches the most recent generic document rather than the lot-specific one. This is the root of the version mismatch mentioned above.

The Root Cause Most Integration Projects Miss: Document Scope Creep at the Substrate Level #

When a brand partner briefs us on a new packaging line, the compliance documentation scope is usually defined around the finished box or pouch. That is a workable starting point, but the real integration complexity sits one level below: at the substrate and consumable input level.

Here is the mechanism. A printed folding carton entering the UK under PPWR (EU Packaging and Packaging Waste Regulation, 2024 revision) requires conformity evidence across at minimum four input streams: the paperboard substrate, the printing inks, the surface coating or laminate, and any adhesive used in construction. Each of these has its own compliance standard, its own revision cycle, and its own issuing organisation. The substrate might be certified to FSC-STD-40-004 v2.1 (chain of custody) and tested to ISO 187 for moisture conditioning before caliper measurement. The UV offset inks need a Nestlé Guidance Note conformity letter or equivalent low-migration declaration if the end use is food-adjacent. The aqueous coating needs an SDS with REACH Regulation (EC) 1907/2006 SVHC content disclosure below 0.1% w/w per substance. And the cold-seal or hot-melt adhesive needs its own food-contact migration data if any adhesive contacts the product directly.

Where projects fail is the assumption that a single DoC at finished-goods level covers all four input streams. It does not. What it does is reference the input documents — and if any one of those input documents is missing, expired, or out of scope, the finished-goods DoC is technically unsupported, regardless of how well it is written.

The measurement threshold for confirming this failure is straightforward: pull the DoC and trace every referenced test report or certificate back to a physical lot number. If any reference is to a generic grade rather than a specific production lot, the document chain has a gap. Our incoming QC protocol (we call this the IQC-R12 substance trace audit) requires 100% traceability from finished DoC back to supplier lot for all food-contact or cosmetics-adjacent jobs. We run this on 100% of affected lots, not on an AQL sampling basis, because the consequence of a miss is not a quality defect — it is a customs hold or a product recall.

Corrective Actions, Ranked by Impact and Feasibility #

1. Rebuild the JCP (Job Compliance Packet) as a lot-specific document set, not a grade-level one. This is the highest-impact intervention and takes two to four working days to execute for an existing job. Every document in the packet — DoC, SDS, FSC transaction record, test certificates — must cite the actual lot or batch number of the materials used in that production run. This closes the version-mismatch failure mode completely.

2. Establish a document-validity calendar for each input supplier. Most supplier conformity letters carry a 12-month validity. Our procurement team flags renewal 60 days before expiry. If your current supplier is not providing expiry-dated conformity letters, that needs to be corrected in the next PO cycle. This takes roughly four hours to set up as a spreadsheet tracker and eliminates the GB/T revision-drift problem for the materials it covers.

3. Add a document cross-reference block to the commercial invoice. When the FSC-CoC certificate number, the DoC reference number, and the applicable standard version appear on the commercial invoice itself, customs and destination importers can verify compliance without requesting supplementary documents. This single change reduces documentation-related clearance queries by a measurable margin — across 14 shipment audits we conducted internally in 2024, invoice-referenced documentation reduced follow-up query rate from roughly 1-in-4 to 1-in-11 shipments.

4. Run a one-time gap audit against your target import market’s current standard version. If you are shipping into the EU, the relevant cross-check is EU Regulation 10/2011 (plastics food contact) and PPWR Article 6 (recyclability and recycled content declarations for 2030 targets). If you are shipping into the US, it is FDA 21 CFR Part 176 and Part 177 as applicable. If both markets apply, the documentation set needs to satisfy both simultaneously, which means identifying the stricter requirement at each substance entry. This is a one-time investment but prevents iterative document revisions per shipment.

5. Requalify documentation after any substrate or consumable supplier change, even if the new material is “equivalent.” “Equivalent” is a commercial claim, not a compliance claim. A different adhesive formulation from a different supplier needs its own food-contact data, even if the finished-goods appearance is identical. This holds for all regulated packaging categories — for non-food, non-cosmetic rigid boxes with no surface finishing, the calculus changes and a supplier self-declaration may be sufficient.

Prevention: What to Specify Upfront #

In the PO and supplier brief, specify the target import market and applicable regulation version (e.g., “EU 10/2011 as amended 2023, PPWR Article 6 recyclability”), not just “food-safe” or “EU compliant.” Specify that all conformity documents must be lot-referenced, not grade-referenced. Request that SDS documents cite REACH SVHC status per Regulation (EC) 1907/2006, updated to the current candidate list (currently 240 substances as of the January 2025 ECHA update). For FSC-certified orders, confirm that the supplier’s CoC certificate covers the specific product category in scope — CoC scope limitations are a common gap.

The document to request from any new packaging supplier before production starts: a completed Compliance Documentation Index (CDI) listing every input material, the applicable standard, the current document reference, and the expiry date.

Specification Notes for Brand Partners #

When you brief us on a packaging job requiring compliance documentation, the most useful information you can give us upfront is: the target import country, the intended product contact category (food direct-contact, food non-contact, cosmetics, pharmaceutical, general consumer goods), and any retailer-specific requirements (some US and UK retailers maintain their own restricted substance lists beyond what regulations require).

The brief gap that causes the most sample iterations is incomplete product contact information. “It’s a box for candles” tells us the substrate and print compliance scope. “The candle wax contacts the inner liner directly and the product is EU market” tells us we need food-contact-equivalent migration data for the liner material, an SDS with EU 10/2011 cross-reference, and a DoC structured to satisfy a potential customs query. Those are different document packages.

Our standard timeline for a complete compliance documentation set on a new job is 10–15 working days from confirmed material sourcing, assuming suppliers have current conformity letters on file. If any input supplier needs to generate new test data (migration testing, for example), add 15–20 working days for that test cycle.

What information do I need to provide for a compliance documentation quote?

Target import market, product category (food, cosmetics, pharmaceutical, general), retailer name if applicable, and whether you need documentation at finished-goods level only or full input-stream traceability. The last point affects scope and cost significantly. Full input-stream traceability typically adds 3–5 working days to documentation preparation.

Our last supplier gave us a single DoC that covered the whole box — is that not sufficient?

It depends on what that DoC references. A finished-goods DoC is the right output, but it is only as strong as the input documents it cites. If it references specific test reports tied to specific material lots, it is solid. If it references generic grade approvals without lot traceability, it will not hold up under customs scrutiny for food or cosmetics packaging. Ask your supplier to show you the underlying reference chain.

Do we need separate documentation for each production run, or can one document cover multiple orders?

For non-food, non-regulated categories, a grade-level document covering multiple orders is acceptable. For food-contact, cosmetics, and pharmaceutical packaging, lot-specific documentation is required — the DoC must be traceable to the actual materials used in each production batch. EU Regulation 10/2011 Article 15 specifically requires that compliance statements reference the materials or articles they relate to.

How often do compliance documents need to be renewed?

Supplier conformity letters typically carry a 12-month validity. FSC transaction records are per-shipment. Migration test reports are valid as long as the formulation is unchanged, but should be revalidated after any substrate or ink supplier change. Our practice is annual renewal for food-contact and cosmetics suppliers, biannual for stable non-food suppliers — but we will trigger an out-of-cycle revalidation if a supplier notifies us of a formulation update, even a minor one.

Can you handle compliance documentation for both EU and US markets on the same packaging run?

Yes, but the document set is additive. EU requirements (10/2011, PPWR, REACH) and US requirements (FDA 21 CFR 176/177, applicable state regulations) have overlapping but non-identical substance lists. We structure the DoC to address both simultaneously, noting the applicable standard for each declaration. The main friction point is that EU 10/2011 uses a positive list for permitted substances, while US FDA uses a broader “generally recognized as safe” framework — so some substances permissible under FDA require explicit migration data under EU rules.

---

Planning a packaging project? Contact our team to request a complimentary specification review and sample quote.