Education
Why batch-level documentation matters.
Research compound documentation becomes useful when each record is tied to a specific batch, certificate ID, test date, method and documented change history. Generic or reused CoAs create unresolved documentation risk.
Batch-level fields
- • Public certificate ID
- • Supplier batch number
- • Manufacture date where available
- • Test date and review/expiry window
Audit trail
- • Original document upload
- • PurityLedger review event
- • Lab authentication or third-party link
- • Retest, dispute or superseded event
QR records
- • QR code links to public verification page
- • Record shows current documentation status
- • Expired and disputed records remain visible
- • Users can inspect document fingerprints
Procurement use case
- • Review documentation completeness
- • Compare supplier transparency trails
- • Request supporting documentation
- • Escalate unclear records for retest or dispute review
Important limitation: This record does not certify safety, legality, efficacy, approval, or suitability for human/veterinary use.
PurityLedger provides documentation review, batch record hosting, CoA verification tools and analytical testing coordination only. PurityLedger does not certify any product as safe, effective, legal, approved, or suitable for human or veterinary use. Testing records are batch-specific and do not constitute medical advice, regulatory approval, or endorsement of any supplier or product. Clients and users are responsible for compliance with applicable laws in their jurisdiction.