Batch identity
Create a persistent lot identifier.
BATCH · QR · EVENT PROOF
Inspect the traceability workflow end to end.
This synthetic demonstration batch proves the interface, event chronology, hash and QR pathway. It makes no commercial origin, certification or shipment claim.
PUBLIC BATCH VIEW
Loading demonstration batch…
Scan to open this public pilot record- Batch code
- —
- Crop
- —
- Origin label
- —
- Verification
- —
- Verification hash
- —
EVENT CHRONOLOGY
From record creation to handoff
- Loading events…
The demonstration batch could not be loaded.
NEXT STEP
Activate this workflow with your own data.
Tell the CONSAI team the geography, crop, organization and intended outcome. We will route the request to the correct pilot workflow.
TRACEABILITY PILOT
Connect batch identity, custody events and evidence to a safe QR page.
Origin context, event history and documents link to a batch while submitted, reviewed, verified and missing evidence remain explicit.
Evidence boundaryPublic-safe overview: operational claims require source, owner and review status.
Event timeline
Record origin, handling and transfer.
QR proof
Share a safe summary without private documents.
TRUST & GOVERNANCE
What this page proves—and what it does not.
CONSAI keeps platform activity, reviewed evidence and verified outcomes as separate states.
- Sources, freshness and review status stay visible where available.
- Platform activity is not presented as a verified outcome.
- Private records remain access-controlled.
- Human review is required before consequential action.
FREQUENTLY ASKED QUESTIONS
Questions before activation
Does QR scanning certify a product?
No. It opens a record and its verification state.
Can documents remain private?
Yes. Public pages can show safe summaries.
What starts a live pilot?
A real batch, accountable parties and evidence rules.