Regulatory pressure
The EU EUDR FAQ says due diligence statements need plot coordinates, and plots over 4 hectares need polygon boundaries instead of a single point.
Proof status
This is the current trust asset: one real public cocoa dataset treated like a buyer handoff file, exact issues found, and an honest output boundary. It is not a customer case, not a paid transaction, not buyer approval, and not legal certification.
Before
Public source rows: 57,658 rows with latitude, longitude, and area values, but no plot IDs, supplier identity, batch linkage, or polygon geometry in the buyer-handoff view.
During
Issue log: TraceReady found 161,450 blockers, 57,658 warnings, and 46,134 point-only plots over 4 hectares that need polygon follow-up before buyer review.
After
Handoff out: buyer/supplier follow-up list and issue evidence. TraceReady does not fabricate missing supplier IDs, plot IDs, batch IDs, or polygon boundaries.
Real-world problem
TraceReady's public proof is not founder biography. It is a measured file problem: the regulation asks for plot-level geolocation, buyers ask suppliers for structured farm files, and 57,658 rows with coordinates still produced a repair brief instead of a buyer-ready pack.
The EU EUDR FAQ says due diligence statements need plot coordinates, and plots over 4 hectares need polygon boundaries instead of a single point.
The Daarnhouwer supplier geolocation guide asks coffee and cocoa suppliers for WGS84 GeoJSON, CSV, or Excel geolocation files with a unique and persistent farm ID.
Public audit result: 0 buyer-ready records, 46,134 point-only plots over 4 hectares, and every row missing plot ID and supplier identity.
Current trust ladder
TraceReady does not ask a cold buyer to accept a founder story as proof. The public-data pilot proves the file-handoff problem; the next upgrade is one permissioned real-world cleanup with anonymized before/after facts.
57,658 public rows checked, 46,134 point-only plots over 4 hectares, every row missing plot ID and supplier identity, and zero buyer-ready records.
one permissioned customer or file-owner case showing messy file in, exact issues found, cleaned pack out, and written approval to publish anonymized facts.
paid checkout stays gated until reply capture and launch scope are confirmed, so nobody is asked to trust a paid cleanup desk before intake works.
0 replies, 0 file checks, 0 pilot requests, and 0 paid orders are counted until external outreach or a real file owner creates evidence.
Evidence pack
The ZIP contains the readiness report, issue-summary CSV, buyer/supplier follow-up list, one-page case study, buyer-style handoff summary, and audit JSON used for this public-data pilot. For this source file, the cleaned output is a repair brief: derived counts, method notes, and source-owner follow-up questions, not raw source rows or coordinates.
View public pilot caseDownload public pilot evidence packView checksum manifestPublic dataset mini-audit
57,658 public cocoa rows checked: TraceReady found 46,134 point-only plots over 4 hectares, 57,658 rows without plot IDs, and 57,658 rows without supplier identity. This is not a customer file, not buyer approval, and not legal certification; it is proof that a geolocation-heavy file can still fail basic handoff readiness.
57,658
Rows downloaded from the public Colombian-Cocoa-Dataset and normalized for TraceReady checks.
46,134
Rows where area exceeds the launch-readiness polygon threshold but only point coordinates are present.
57,658
Coordinates existed, but row-level farm or plot identifiers were absent from the buyer-handoff view.
57,658
No supplier, producer, farmer, or supplier ID field was available for traceability handoff.
Source: Colombian-Cocoa-Dataset. TraceReady supplied country and commodity from public metadata, then left plot IDs, supplier identity, batch IDs, and polygon geometry blank when the row data did not provide them.
Rule reference: CBI EUDR coffee guidance states that polygon mapping is mandatory for coffee plots larger than 4 hectares. TraceReady applies that launch-readiness threshold to coffee and cocoa file checks.
Next step for a real file
The first pass stays in your browser: load a CSV, KML, GeoJSON, or JSON GeoJSON file, review the row-level blockers, and decide whether the issue list is worth cleaning up. If the issue list is useful, request a scoped cleanup before payment. TraceReady confirms launch scope before raw coordinates or Stripe payment.
Public proof will be upgraded only when it is true and permissioned: customer quote, company name, paid order count, turnaround metric, or de-identified customer before/after. Until then, TraceReady is clear that the public-data pilot is not a customer case or buyer approval. Operated by Passive Print Labs LLC. Questions: founder@traceready.online.