Playbooks
Batch to plot: chain of custody walkthrough for coffee and cocoa lots
Concept walkthrough of a coffee or cocoa lot: contributing plots, custody hops, operational reconciliation and buyer packs. Live claim models vs scheduled CoC Mass Balance, without inventing UI labels.
A plot map alone does not satisfy a buyer who needs sealed origin through aggregation and processing. This walkthrough explains the concepts behind batch-to-plot chain of custody for coffee and cocoa on Tracebud's live EUDR path. It does not invent Dashboard button names or screen copy. Where a claim model is scheduled, it is labelled clearly.
Why batch-to-plot matters
Coffee and cocoa rarely move in one hop. Beans leave member plots, enter a collection point or mill, become a lot, move to an exporter, then to an importer. EUDR due diligence needs the lot to still point at root plots with usable evidence. That is chain of custody in the agri-food chain sense: custody hops plus plot lineage, not only a satellite tile.
Context: full agri-food-chain solution · FAQ: chain of custody.
Annotated lot (concepts)
1. Contributing plots
Member or supplier plots captured in the Field App with geolocation and consent. Offline visits sync when coverage returns. Without this step, later hops have nothing honest to seal.
2. The lot (batch)
A quantity assembled for movement or sale. The lot should retain links to the plots that contributed volume under the claim model you are using. Desk work happens in the Dashboard.
3. Custody hops
Each handoff (collection → processing → export → import) is a custody hop. The evidence layer should show who held the goods and which plot set still stands behind the lot. Cascading requests fill gaps without remapping every farm: cascading playbook.
4. Operational reconciliation
Processor desks can receive, process and hand off lots with mass reconciliation in operations. That is lot accounting so weights and outputs stay coherent. It is not the same thing as a CoC Mass Balance claim model.
5. Buyer pack
Downstream actors need a pack that combines plot evidence, screening where used, and custody lineage for EUDR filing. DDS-style assemble and file sit on this spine in open beta. DDS FAQ.
Claim models: live vs scheduled
| Model | Status on Tracebud (as of this page) | Plain meaning | | --- | --- | --- | | Identity Preservation | Live | Product from identified plots stays identifiable through hops | | Segregation | Live | EUDR-ready material kept separate from non-qualifying material | | CoC Mass Balance (claim) | Scheduled | Claim-mode mass balance is not live yet |
Do not confuse scheduled CoC Mass Balance with operational mass reconciliation already used on processor desks.
Coffee and cocoa notes
- Coffee specialty buyers often inherit incomplete packs from multi-hop suppliers. Cascade first; remap last. Nordic / small EU playbook.
- Cocoa coops and SME exporters own the first mile where plots are created. Plots-to-DDS playbook.
Soft programmes (not this walkthrough's job)
Living income, regen, Scope 3 or scheme packs may later mould the same plot and delivery records. Soft claim and co-build only. See capture once, multi-programme evidence. This walkthrough stays on EUDR chain of custody concepts.
What we are not inventing here
- Exact Dashboard menu labels, icons or step wizards
- Customer names, tonne volumes or ship dates
- Competitor CoC behaviour
If you need a product walkthrough with live UI, book a demo or get started in open beta.