Skip to content

Pixlog Field Notes

Retest triggers after failures (batch 2 guide 3)

2026-11-04
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 takeawaysKeep 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[1]. · 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]. · Control sample custody from carton to laboratory bench, since an unsealed sample invites questions no report can answer, a logic familiar from acceptance testing practice, where agreed criteria decide pass or fail before shipment[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 logic familiar from acceptance testing practice, where agreed criteria decide pass or fail before shipment[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.

Matching the test to how the product is actually used

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 testing practice follows the same logic: agree the criteria first, test against them, and let the result decide whether the goods move forward.[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

Decision pointWhat to checkTypical evidenceNext action
Product scopeExact materials with food contactBill of materials marked by contactList each material in the scope note
Use conditionsFood type, time, and temperatureHonest worst-case descriptionLet the lab translate to simulants
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

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

Illustration: The expensive scoping mistakes, Decorative illustration for the section "The expensive scoping mistakes,"; visual only, carries no data.

The order of operations for defensible files

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

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. Acceptance testing practice follows the same logic: agree the criteria first, test against them, and let the result decide whether the goods move forward.[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. Quality management vocabulary frames this as process control: documented steps, clear responsibilities, and records that allow the next reviewer to retrace the decision.[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. Acceptance testing practice follows the same logic: agree the criteria first, test against them, and let the result decide whether the goods move forward.[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

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

  1. Wikipedia: Factory acceptance test —— Overview of factory acceptance testing performed before shipment or installation.
  2. 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.

Ship faster pages without touching a line of code.

Pixlog compresses, reformats and CDN-delivers every product photo on your store. Average customer lifts mobile conversion 23% within 30 days.

Get My Free Image Audit Performance Lab