Choosing accredited labs (batch 2 guide 3)
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
- Scope each test to the exact material, food type, and use condition, because migration results only mean something under defined conditions, a context shaped by technical barriers to trade rules, which expect technical requirements to stay transparent and non-discriminatory[1].
- Read detection limits before celebrating a pass, since a non-detect above the regulatory threshold answers nothing, a logic familiar from acceptance testing practice, where agreed criteria decide pass or fail before shipment[2].
- Link every declaration of compliance to the specific reports behind it, with dates and material references that an inspector can follow, an assurance strengthened when the laboratory operates under internationally recognized accreditation arrangements[3].
- Retest when formulations, suppliers, or processes change rather than on a fixed calendar alone, since composition follows inputs, a context shaped by technical barriers to trade rules, which expect technical requirements to stay transparent and non-discriminatory[1].
- Keep pre-production and mass-production samples clearly separated in the file, because only the latter represents what consumers receive, a logic familiar from acceptance testing practice, where agreed criteria decide pass or fail before shipment[2].
Many food contact files fail on linkage before they fail on chemistry: reports exist but nobody can say which report covers which material in which finished product. Inspectors and retail compliance teams ask exactly that question, and vague answers erode confidence faster than marginal results. This article treats traceability as a first-class requirement alongside the testing itself.
Good linkage is a habit, not a software purchase: every report gets filed with its material reference, date, method, and product mapping, and every declaration points to those reports explicitly. When formulations or suppliers change, the affected links get flagged for retesting instead of silently aging. The routine takes minutes per order once established.
What follows covers the testing decisions first and the documentation discipline second, since both must work for the file to hold up. Readers will find scoping economics, custody practice, limit interpretation, and update tracking in that order. The reminder at the end distills the file habits that survive staff turnover.
Choosing samples that represent mass production
A report on pre-production samples describes development intent, not shipped reality, and filing it as product evidence creates a gap inspectors notice quickly. Acceptance testing practice follows the same logic: agree the criteria first, test against them, and let the result decide whether the goods move forward.[2] Mass-production specimens drawn from packed cartons carry far more weight because their custody chain mirrors the goods consumers receive. The sampling note should state which case applies in plain language.
Drawing from finished, packed units also captures the effects of the full process sequence, including curing, assembly lubricants, and packaging interactions. Experienced buyers book UTS food contact material testing once the trigger is confirmed, so the work answers the question the order depends on. Those late-stage influences are invisible in component-level pre-tests yet fully present in consumer exposure.
Composite sampling across cartons beats single-carton convenience sampling for heterogeneous production, spreading the result across the lot it claims to represent. Technical barriers to trade rules add the market-access angle: technical requirements should remain transparent and non-discriminatory across supplying countries.[1] The extra effort is modest and the defensibility gain is large, particularly when results sit near regulatory thresholds. Laboratories can advise on composite schemes for specific product shapes.
Reading a test scope for value
| Decision point | What to check | Typical evidence | Next action |
|---|---|---|---|
| Declaration linkage | Reports referenced with dates | Mapping table product to reports | Repair references before shipping |
| Change control | Formulation or supplier changes | Change log and supplier notices | Retest affected materials |
| List currency | Panel against current requirements | Dated panel versus current lists | Extend the panel this round |
| 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 |
Use the matrix as a pre-booking checklist: any row without evidence becomes a scope item rather than an assumption.
A testing sequence that holds up
- 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.
- Read limits before resultsCompare detection limits against thresholds before celebrating any non-detect. Results above the threshold prove nothing regardless of how clean the number looks.
- Link declaration to reportsPoint each declaration explicitly at its supporting reports with numbers and dates. Traceable paperwork survives inspector review; vague gestures do not.
Gaps that inspectors notice first
Detection limits decide what a non-detect actually proves, yet many buyers file pass reports without checking the limit behind the result. Technical barriers to trade rules add the market-access angle: technical requirements should remain transparent and non-discriminatory across supplying countries.[1] A non-detect at a limit above the regulatory threshold is an unanswered question dressed as good news, while the same result below the threshold is genuine assurance. The comparison takes seconds and changes the meaning of the whole report.
Method selection carries equal weight: overall migration screens, specific migration tests, and composition analyses answer different questions for different regulations. Acceptance testing practice follows the same logic: agree the criteria first, test against them, and let the result decide whether the goods move forward.[2] Accepting a generic screen where the regulation expects a specific migration result leaves the file exposed regardless of how tidy the numbers look. The scope note should name the method and the regulation it serves side by side.
Laboratory dialogue resolves most of these issues before money is spent, since competent laboratories will question mismatched scopes when given complete product information. International accreditation arrangements add weight to the paperwork: results from accredited laboratories travel better between buyers and regulators.[3] Sharing use conditions, material lists, and target markets upfront invites that pushback while it is still cheap. Buyers who brief laboratories thoroughly get fewer useless reports per unit of spending.
A reminder before the file closes
Define retest triggers before you need them: supplier switches, formulation changes, process adjustments, and elapsed time each deserve a threshold. Systems with triggers stay current; systems without them age silently.
Sources
- WTO: Agreement on Technical Barriers to Trade —— WTO portal for the TBT Agreement covering technical regulations, standards and conformity assessment.
- Wikipedia: Factory acceptance test —— Overview of factory acceptance testing performed before shipment or installation.
- ILAC: International Laboratory Accreditation Cooperation —— ILAC homepage describing the international cooperation on laboratory and inspection body accreditation.
Frequently asked questions
How often should food contact files be reviewed?
Whenever regulations update and on a risk-based schedule otherwise, with high-attention substances and strictly enforced markets leading. Pre-agreed retest triggers for supplier and formulation changes keep decisions consistent. Written schedules survive workload; unwritten ones evaporate.
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.
Apply for Membership
Translate evidence-based phototherapy research into bedside practice alongside 11,400+ clinicians worldwide.