Declarations of compliance are only as credible as the test evidence behind them, and regulators increasingly ask to see that chain. This guide shows how to link each declaration to specific reports, keep the evidence current as formulations change, and use accredited testing so the paperwork travels across borders. Treat the file as a living record, not as a one-time certificate.
Key takeaways
- Control sample custody from carton to laboratory bench, since an unsealed sample invites questions no report can answer, a caution supported by acceptance sampling theory, which ties conclusions to defined plans rather than single specimens[1].
- Scope each test to the exact material, food type, and use condition, because migration results only mean something under defined conditions, a discipline reflected in quality management vocabulary, where documented processes replace ad hoc judgments[2].
- Read detection limits before celebrating a pass, since a non-detect above the regulatory threshold answers nothing, a caution supported by acceptance sampling theory, which ties conclusions to defined plans rather than single specimens[1].
- Link every declaration of compliance to the specific reports behind it, with dates and material references that an inspector can follow, a discipline reflected in quality management vocabulary, where documented processes replace ad hoc judgments[2].
- Retest when formulations, suppliers, or processes change rather than on a fixed calendar alone, since composition follows inputs, a caution supported by acceptance sampling theory, which ties conclusions to defined plans rather than single specimens[1].
Food contact compliance starts with a deceptively narrow question: does anything harmful migrate from this material into food under real use conditions. Answering it requires matching the material, the food type, the time, and the temperature to the right method and limit. This guide walks through those matches so each test round answers a precise question.
The cost of imprecision is high in this category: border authorities can hold or reject shipments, retailers can delist products, and recalls in food-adjacent categories damage brands disproportionately. Testing is cheap insurance only when the scope is right; a mis-scoped report insures nothing while consuming budget and calendar time. Precision in scoping is the theme of this article.
The sections below follow a natural case order: scoping the test, controlling the sample, reading the report with attention to detection limits, and keeping declarations current as inputs change. Each section is self-contained for readers under time pressure, and together they form a routine that scales across seasons and suppliers.
Scoping migration testing to real use conditions
Migration results only mean something under stated conditions of food type, time, and temperature, so honest use descriptions are the foundation of the scope. Acceptance sampling literature makes the same point from the other side: without a defined sampling plan, one result cannot carry the whole lot.[1] Understating conditions to ease limits produces passing reports that protect nothing and deceive everyone downstream. Overstating them wastes money on severity the product will never face in service.
The practical rule is to describe the reasonably foreseeable worst case in plain terms and let the laboratory translate it into simulants and exposures. Experienced buyers book independent food contact material testing once the trigger is confirmed, so the work answers the question the order depends on. That division of labor plays to each side's competence: buyers know the product, laboratories know the methods.
Multi-material products need per-material scoping rather than a single finished-article test alone, since different components face different food contact. Quality management vocabulary frames this as process control: documented steps, clear responsibilities, and records that allow the next reviewer to retrace the decision.[2] Seals, coatings, and printed surfaces each deserve their own consideration even when the bulk material looks straightforward. The scope note should list materials individually with the reasoning for each.
Reading a test scope for value
| Decision point | What to check | Typical evidence | Next action |
|---|---|---|---|
| Product scope | Exact materials with food contact | Bill of materials marked by contact | List each material in the scope note |
| Use conditions | Food type, time, and temperature | Honest worst-case description | Let the lab translate to simulants |
| Method match | Method versus target regulation | Method line beside regulation cite | Change method before testing |
| Detection limits | Limit of detection versus threshold | Method details from the laboratory | Use a more sensitive method if needed |
| Sample origin | Pre-production versus mass production | Sampling note with carton numbers | Redraw from packed cartons |
Use the matrix as a pre-booking checklist: any row without evidence becomes a scope item rather than an assumption.
From use description to linked declaration
- Schedule the next reviewSet retest triggers for supplier changes, formulation tweaks, and elapsed time so the file stays current. Pre-agreed triggers remove debate from busy weeks.
- Describe the use honestlyWrite down the food type, contact time, and temperature for the reasonably foreseeable worst case. Honest inputs let the laboratory choose simulants and exposures that the report can defend.
- List contact materialsMark every material with food contact on the bill of materials, including seals, coatings, inks, and adhesives. Components that look incidental often dominate migration results.
- Confirm method and marketCheck that the proposed method serves the regulation of your destination market rather than a generic screen. Method-market mismatches produce elegant but irrelevant reports.
- Draw production samplesTake specimens from packed mass-production cartons with custody notes recording the source. Pre-production samples describe intent; only production samples represent consumer exposure.
Why good products ship with thin paperwork
Label and declaration mismatches create a special category of findings where the product may be safe but the paperwork claims something the evidence does not support. Quality management vocabulary frames this as process control: documented steps, clear responsibilities, and records that allow the next reviewer to retrace the decision.[2] Composition statements, DoC references to outdated reports, and material descriptions that drifted from the tested version all fall in this family. The fix is administrative but urgent, since inspectors read paperwork before they test chemistry.
The preventive routine is a periodic paperwork audit: sample finished-product files and verify that every claim traces to current evidence. Acceptance sampling literature makes the same point from the other side: without a defined sampling plan, one result cannot carry the whole lot.[1] Quarterly sampling catches drift early, while annual or never lets small inconsistencies accumulate into file-wide doubt. Each sampled file should take under an hour to verify once the mapping habit exists.
Supplier declarations need the same treatment upstream, since bought-in materials arrive with claims that age as formulations change. Acceptance sampling literature makes the same point from the other side: without a defined sampling plan, one result cannot carry the whole lot.[1] Refreshing supplier declarations on a schedule tied to risk, and retesting the highest-risk inputs rather than trusting paper alone, keeps the upstream chain honest. Paper without periodic verification is optimism, not control.
A reminder before the file closes
Before filing any pass report, check the detection limit against the threshold it is supposed to clear. A non-detect above the limit is an open question, not a certificate.
Sources
- Wikipedia: Acceptance sampling —— Overview of acceptance sampling including AQL concepts used in product inspection.
- Wikipedia: ISO 9000 —— Overview of the ISO 9000 family of quality management standards.
Frequently asked questions
How should migration testing be scoped?
Start from the honest worst-case use: food type, contact time, and temperature, then let the laboratory translate those into simulants and exposures. List each food-contact material separately, including seals and coatings. Scopes built this way answer precise compliance questions instead of producing generic numbers.
What matters most when reading a migration report?
First the method-market match, then detection limits against thresholds, then sample identity and custody. A non-detect above the threshold answers nothing no matter how tidy it looks. Confirming these three takes minutes and determines what the report actually proves.
Should pre-production samples be used for compliance files?
Only as development guidance, never as product evidence, since they cannot capture the full process sequence or represent shipped lots. Draw compliance specimens from packed mass-production cartons with custody notes. The distinction belongs in writing in the file itself.
How should declarations of compliance reference test evidence?
Explicitly, with report numbers, dates, materials, and methods listed or directly referenced so a successor or inspector can trace each claim within an hour. Vague gestures at testing history fail serious document review. A maintained mapping table per product family serves for years.