Overview
This page is HMTc Category 5 row 8 from the locked beverage architecture. It exists as a wiki node so evidence, regulatory context, ingredient routing, and future field findings have a stable place to land.
Reading guide
Legal, regulatory and retailer teams can use the cited measurements, applicable limits and study limitations to assess the evidence for this category.
Quality teams can examine product form, measurement basis and sources of variation. Journalists and researchers can follow each reference to the original findings and methods.
Related tools and pages: Lab Result Comparator
Literature scope
The Heavy Metal Index source corpus is currently focused on food and food-contact materials. This page documents an HMTc Taxonomy v2.0 row in the category this product class for which no peer-reviewed primary or government sources have yet been ingested. The page exists as the routing destination for future ingest. Until sources land, the literature-evidence sections below are deliberately empty rather than guessed; HMTc certification thresholds for products in this row continue to be developed under the certification program at heavymetalcertified.com, not on this public page.
Who this page is for
This page is for readers evaluating flavored-water products against the locked beverage row and the bottled-water lead standard. Brand legal and regulatory readers should focus on whether a cited finding is actually a flavored-water or baby-drink product, and whether it is comparable to the 5 ppb bottled-water lead standard. Retailer and QA readers can use the page to separate water-source controls from added-flavor, fruit, mineral, or child-product formulation controls. HMTc staff should keep the current Polish baby-drink evidence visible as context while avoiding silent pooling with US bottled-water surveillance.
Evidence summary
The table below summarizes what the peer-reviewed and government literature cited on this page reports for heavy-metal concentrations in Flavored waters. Values are pulled directly from cited sources without re-aggregation. This page publishes literature evidence only, not certification thresholds.
Methodology rules for speciation, basis preservation, non-detect handling, and source pooling are stated in the Methodology section above and apply to every row below.
| Analyte | Subcategory | Reported concentration range | Detection rate | Applicable regulatory cap | Sources | Confidence | Basis |
|---|---|---|---|---|---|---|---|
| lead (Pb) | Flavored waters (no contributing evidence loaded) | No concentration data loaded for this analyte | Sample-level detection rate not reported | US FDA 21 CFR 165.110 - bottled-water metal limits: 5 ppb (bottled water) | 0 | data gap | Basis not reported |
Source Evidence Inventory
The sole routed source at this pass is Health Safety Assessment of Ready-to-Eat Products Consumed by Children Aged 0.5–3 Years on the Polish Market, a Polish-market survey of 397 ready-to-eat products for children aged 0.5-3 years. Its baby-drinks category includes fruit drinks and water, with reported cadmium and lead summaries and exceedance counts in the broader product survey. The source is strongest for identifying that child-oriented drink products can carry measurable lead and cadmium, while weaker for this specific row because the subgroup combines fruit drinks and water and is not a US-market bottled-water dataset.
Supporting evidence and scope
Pending: regenerated by tools/evidence/apply-product-broad-context.mjs once broad-scope sources route to this page.
Federal / Regulatory Limits vs Field Findings
This is the fast comparison view for standards developers, regulators, retailers, brands, and legal teams. It shows the applicable federal or regulatory limit next to the current field-evidence state. It is not an HMTc pass/fail table; technical distributions remain in the evidence sections below.
| Metal | Federal / regulatory limit | Actual field finding | Decision read | Evidence |
|---|---|---|---|---|
| Lead lead (Pb) | US FDA 21 CFR 165.110 - bottled-water metal limits: Federal FDA regulatory quality standard: 5 ug/kg Pb. Scope: bottled drinking water. Basis: bottled water. | No comparable field-finding row has been promoted yet for this beverage category. | Use as regulatory context only until product scope is confirmed. | US FDA 21 CFR 165.110 - bottled-water metal limits |
Controls and mitigation
The highest-control levers are finished-product testing for lead against the bottled-water standard, source-water verification, and lot-level review of flavoring, fruit, mineral, or other additions that can move the product away from plain-water assumptions. For child-oriented products, formulation review matters because a “drink” subgroup may combine water-like products with fruit-derived inputs. QA programs should therefore preserve product identity in test records and avoid averaging flavored waters with juices or purees.
Decision Snapshot
| Field | Status |
|---|---|
| Row state | Locked row node; structured occurrence extraction started |
| Category hub | Category 5: Beverages |
| Crosswalk hub | Regulatory Crosswalk vs Field Findings |
| HMTc use | Routing and evidence-gap tracking only; not a certification threshold |
Evidence Handling
Finished-product findings belong on this product page. Ingredient-only findings belong on ingredient pages before they are used for product inference.
How standards math uses this page
This page reports what the peer-reviewed and government literature says about heavy-metal concentrations in this product category; it publishes no certification thresholds of its own. Certification criteria are set separately under the Heavy Metal Tested & Certified program at heavymetalcertified.com, which reads this page as its literature baseline. The two are kept apart by design, so this page remains an independent record of the evidence rather than a justification for any threshold.
Historical recalls and enforcement
No flavored-water recall or enforcement event has been promoted into this page yet. The current enforceable context is the FDA bottled-water lead standard already shown in the crosswalk. Any future enforcement synthesis should distinguish plain bottled water, flavored water, fruit drinks, and infant or toddler drinks before drawing comparisons.
Methodology
Finished flavored-water evidence is routed here only when the source product is a water or water-like drink rather than a juice, puree, or general beverage. The FDA bottled-water lead cap is regulatory context for the row, but field findings are admitted only when product scope and basis match or can be transparently compared. Health Safety Assessment of Ready-to-Eat Products Consumed by Children Aged 0.5–3 Years on the Polish Market reports a baby-drinks subgroup that includes fruit drinks and water on the Polish market; that mixed subgroup is useful context for child-oriented flavored-water risk, but it is not yet a clean US bottled-water benchmark distribution. Total arsenic, cadmium, total mercury, and lead are kept as reported, on a wet-weight basis.
References
Works cited in this page’s text, in first-appearance order. See Sources for this page’s source inventory. Each title links to a source record with bibliographic details, reported findings, and document provenance.
- Health Safety Assessment of Ready-to-Eat Products Consumed by Children Aged 0.5–3 Years on the Polish MarketPeer-reviewed
Sources
Source records associated with this topic. Inclusion does not establish that every finding applies to this product or ingredient. References above identify works cited in the text.
| # | Citation | Year | Type | Used on this page for |
|---|---|---|---|---|
| 1 | Zmudzinska et al. 2022. Health Safety Assessment of Ready-to-Eat Products Consumed by Children Aged 0.5–3 Years on the Polish Market, Nutrients 14(11):2325 | 2022 | Peer-reviewed | PL tAs, Cd, tHg, Pb occurrence in 397 commercial ready-to-eat baby-food products purchased Dec 2020 – Sep 2021 on the Polish market for children aged… (n=397) |
Update history
No substantive edit history is available in this build. The full commit record is available in git.
