The short answer
Heavy metals - the group of elements that destination markets name in their food safety rules, lead prominent among them - are tested in tea per batch as part of the standard safety panel, alongside pesticide residues and microbiology. Limits are set market by market, and they revise over time; the version in force at your order is the one that governs. Control works at three levels, and only the third is a laboratory: choosing origins whose environment and soil context are known, running hygienic handling at the processing facility, and verifying each batch through partner laboratories with results tied to lot numbers. The importer of record answers for the lot at the border; the program's job is to make sure that answer is already documented before anyone asks.
Why tea gets tested at all
Tea is a perennial plant, and that single fact drives the whole subject. The bush roots into the same soil for decades, drawing whatever the soil offers; the leaf surface sits in the open air, collecting fine airborne deposition; and manufacture removes most of the water, concentrating whatever the fresh leaf carried into the dry leaf that ships. The legal measure is that dry leaf, not the brewed cup - brewing transfers only part of what the leaf holds, but the test, and the limit, apply to the traded article. Buyers sometimes hope brewing behavior can substitute for compliance; it cannot, and honest programs do not pretend otherwise. What the concentration effect does mean is that the question is decided upstream: the environment the garden grows in, and the hygiene of everything that touches the leaf afterward, determine what a panel can possibly find.
Where limits come from and how they move
There is no single worldwide number. Each destination market sets limits for the elements it regulates within its own food law, and those values are revised as reviews complete - which means a limit confirmed two seasons ago may not be this season's. The desk treats this the same way as the pesticide frameworks: the destination market is named at order time, the current requirements are confirmed for that market, and the confirmation is repeated before shipment rather than carried forward from the last program. The mechanics of frameworks that revise on a rolling schedule are described in the EU MRL note, and the same logic applies here. When a market tightens a limit mid-program, the practical sequence is to re-test stock against the version in force and take the interpretation to a qualified adviser before goods move - never after.
Upstream controls beat downstream surprises
A laboratory finds what is there; it does not change what is there. The levers that actually move results sit earlier. Origin selection is the largest: the desk's origin network exists partly for this reason, because knowing the environment a garden grows in - its setting, its surroundings, its history - is the first filter a program has. Process control is the second: hygienic handling, clean contact surfaces, and contact materials that belong in a food facility all reduce what processing can add to what the garden started with; the factory audit program checks exactly this at partner facilities. Verification is the third level, and it exists to prove the first two worked. A program that skips the first two and relies on the third is buying rear-view mirrors; a program that runs all three has a file, not a hope.
The testing protocol, level by level
| Control level | What it covers | Where the evidence lives |
|---|---|---|
| Origin selection | Environment and soil context of the source | Origin records and the desk's network notes |
| Process control | Facility hygiene and contact materials | Audit reports and facility registrations |
| Batch verification | Actual results for your lot | Per-batch panel tied to the lot number, retain samples kept |
The batch verification row is where buyers have direct rights: the panel is commissioned per batch through partner laboratories, results are issued against the batch number that appears on your invoice and your pack, and retain samples are kept so the same material can be re-tested later. Results are reported as found; no figures are promised in advance, which is precisely what makes a clean result worth something.
Reading results as a program, not a panic
One result answers one lot. A program is judged on its trend, and trends only exist where sourcing is consistent - which is the quiet case for keeping origin and lot records intact, the same records that serve traceability everywhere else. Blends add one wrinkle worth naming: a blend averages its inputs, so a clean blend result does not certify every component lot, and a flagged component lot does not necessarily fail the blend in the destination's terms. Programs that keep per-component records can answer that question in both directions; programs that only test the blend cannot. When a result comes in clean, it files against the lot and strengthens the baseline. When a market tightens its limits, the stock is re-tested against the version in force and the destination adviser interprets before shipment. And when a buyer's own laboratory wants to verify independently, the retain sample makes that possible on identical material. None of these scenarios require improvisation if the program was built with them in mind - which is the entire point of the panel scope being agreed in writing before the first order.
What to request, in one list
- The safety panel scope for your destination market, in writing, before sampling.
- Per-batch heavy metals results issued against the lot number you will actually receive.
- Retain sample references, so any later question re-tests the same material.
- Origin and lot records, so a trend is readable across seasons.
The testing layer in full - physical, sensory and safety - is mapped in the testing parameters note, and the framework sits on the quality control page with the document set on the certifications overview. To open a program with the panel scope built in, send the destination and format to the quote form.