The short answer

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 takeawaysLink 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[1]. · 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[2]. · Keep pre-production and mass-production samples clearly separated in the file, because only the latter represents what consumers receive, an assurance strengthened when the laboratory operates under internationally recognized accreditation arrangements[1]. · Check that the laboratory method matches the applicable regulation for your market instead of accepting a generic migration screen, a context shaped by technical barriers to trade rules, which expect technical requirements to stay transparent and non-discriminatory[2]. · Control sample custody from carton to laboratory bench, since an unsealed sample invites questions no report can answer, an assurance strengthened when the laboratory operates under internationally recognized accreditation arrangements[1].

Migration testing looks technical from the outside but rests on buyer decisions that require no laboratory background: choosing the right sample, stating the use conditions honestly, and keeping the paper chain intact. Laboratories execute brilliantly when instructed precisely and merely adequately when instructed vaguely. This guide focuses on the instruction side, where buyers control the outcome.

The most common instruction failures are familiar across categories: pre-production samples presented as representative, use conditions understated to ease limits, and custody gaps that let anyone question the result. Each has a simple preventive routine described below. None of them costs money; all of them save it.

Readers under shipment pressure should start with the scoping and custody sections, which resolve most urgent cases, then adopt the tracking routine for the longer term. Substance requirements evolve and supplier formulations drift, so a file that was complete last year may be thin today.

The paper chain inspectors actually ask for

A declaration of compliance is a claim that points to evidence, and the pointing must be explicit: report numbers, dates, materials, and methods listed or directly referenced. International accreditation arrangements add weight to the paperwork: results from accredited laboratories travel better between buyers and regulators.[1] Declarations that gesture vaguely at testing history fail the first serious document review, regardless of how good the underlying reports are. Precision in referencing costs minutes and saves shipments.

Each product-to-material-to-report link should survive staff turnover, which means writing it down where successors will look rather than keeping it in someone's memory. Experienced buyers book UTS food contact testing once the trigger is confirmed, so the work answers the question the order depends on. A simple mapping table maintained per product family serves this purpose for years with minimal upkeep.

Change control completes the chain: formulation tweaks, supplier switches, and process changes should trigger a review of affected links rather than silent aging. Technical barriers to trade rules add the market-access angle: technical requirements should remain transparent and non-discriminatory across supplying countries.[2] Flagging the affected declarations at the moment of change keeps the file honest without requiring constant full retesting. The discipline is administrative, but it is what separates credible files from decorative ones.

Reading a test scope for value

Decision pointWhat to checkTypical evidenceNext action
Method matchMethod versus target regulationMethod line beside regulation citeChange method before testing
Detection limitsLimit of detection versus thresholdMethod details from the laboratoryUse a more sensitive method if needed
Sample originPre-production versus mass productionSampling note with carton numbersRedraw from packed cartons
Declaration linkageReports referenced with datesMapping table product to reportsRepair references before shipping
Change controlFormulation or supplier changesChange log and supplier noticesRetest affected materials

Use the matrix as a pre-booking checklist: any row without evidence becomes a scope item rather than an assumption.

Illustration: Reading a test scope for Decorative illustration for the section "Reading a test scope for"; visual only, carries no data.

The order of operations for defensible files

  1. Link declaration to reportsPoint each declaration explicitly at its supporting reports with numbers and dates. Traceable paperwork survives inspector review; vague gestures do not.
  2. 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.
  3. 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.
  4. 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.
  5. 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.

Why good products ship with thin paperwork

Update tracking is the maintenance contract for the whole compliance file: regulations add substances, lower limits, and refine methods while products sit unchanged. International accreditation arrangements add weight to the paperwork: results from accredited laboratories travel better between buyers and regulators.[1] A routine that maps list updates against the bill of materials converts regulatory drift into scheduled tasks. Without it, the file silently expires and the discovery moment is always inconvenient.

Illustration: Why good products ship with thin Decorative illustration for the section "Why good products ship with thin"; visual only, carries no data.

Prioritization keeps the routine affordable: high-attention substances, food-contact-critical components, and products in strictly enforced markets lead the review queue. Technical barriers to trade rules add the market-access angle: technical requirements should remain transparent and non-discriminatory across supplying countries.[2] Stable inputs from well-controlled suppliers follow on a lighter cycle rather than escaping review entirely. The written schedule matters more than its exact intervals, because unwritten schedules evaporate under workload.

Retest triggers should be defined in advance so decisions stay consistent across team changes: supplier switches, formulation tweaks, process changes, and elapsed time since the last round each get their threshold. International accreditation arrangements add weight to the paperwork: results from accredited laboratories travel better between buyers and regulators.[1] Pre-agreed triggers remove debate from busy weeks and give suppliers predictable expectations. The file then shows a system working rather than a series of improvisations.

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

  1. ILAC: International Laboratory Accreditation Cooperation —— ILAC homepage describing the international cooperation on laboratory and inspection body accreditation.
  2. WTO: Agreement on Technical Barriers to Trade —— WTO portal for the TBT Agreement covering technical regulations, standards and conformity assessment.

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.