What can a batch COA tell you?
How to read identity, date, analytes, potency and test scope without turning one record into a universal promise.
Read the source trail →RLAXE turns “should I trust this?” into a legible trail: what is known, where it came from, what is still unknown, and what must be checked next.
Read an answer that shows method, evidence, limits and the next thing to verify.
Browse the reading room →Choose a jurisdiction and inspect aligned fields without filling gaps.
Open comparison →See claim classes, source hierarchy, freshness and corrections.
How we check →How to read identity, date, analytes, potency and test scope without turning one record into a universal promise.
Read the source trail →A plain-language classification tool for separating observable product details from efficacy, medical and testimonial wording.
Read the source trail →Use the label as a bounded record: ingredients, serving, warnings, manufacturer, lot and language, with absent fields kept visible.
Read the source trail →Testing language becomes useful only when the lab, method, batch match and test date can be traced.
Read the source trail →Compare stable fields, preserve “not found”, and keep source dates and commercial disclosures beside the decision.
Read the source trail →Country, state or province, intended use, channel and claim wording all change the question.
Read the source trail →