Retest triggers after failures (batch 2 guide 2)

Key takeaways

1. 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].
2. Check that the laboratory method matches the applicable regulation for your market instead of accepting a generic migration screen, a discipline reflected in quality management vocabulary, where documented processes replace ad hoc judgments^[2].
3. Control sample custody from carton to laboratory bench, since an unsealed sample invites questions no report can answer, a connection buyers recognize from CE marking practice, where conformity evidence supports the marking decision^[3].
4. Scope each test to the exact material, food type, and use condition, because migration results only mean something under defined conditions, an assurance strengthened when the laboratory operates under internationally recognized accreditation arrangements^[1].
5. Read detection limits before celebrating a pass, since a non-detect above the regulatory threshold answers nothing, a discipline reflected in quality management vocabulary, where documented processes replace ad hoc judgments^[2].

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. International accreditation arrangements add weight to the paperwork: results from accredited laboratories travel better between buyers and regulators.^[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 food contact testing in China 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.

The expensive scoping mistakes, compared

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

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

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. International accreditation arrangements add weight to the paperwork: results from accredited laboratories travel better between buyers and regulators.^[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. Quality management vocabulary frames this as process control: documented steps, clear responsibilities, and records that allow the next reviewer to retrace the decision.^[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. CE marking practice reinforces the habit: the marking decision rests on conformity evidence, and test documentation is part of that evidence.^[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

Frequently asked questions