Design Direction / Business System

Trong Duc Cocoa Operating System

This folder is structured as a deliverable-ready HTML pack. It translates the company’s vertical chain into decision screens that management, field teams, procurement, processing, and export sales can actually use.

600
Farmer relationships to organize
Current network size referenced in project materials.
3
Supply provinces to coordinate
The pack keeps province-level planning visible on every major screen.
50-100t
Annual bean processing range
Factory and procurement screens are sized around this operating scale.
EU
Primary export readiness lens
Compliance, proof, and batch evidence are treated as first-class workflows.

What this pack is for

Instead of a single generic dashboard, the company needs a family of operating surfaces. Each screen in this pack is scoped to one business question: who the farmers are, where farms are, what beans were bought, how batches moved through the factory, which customers were served, and whether documentation is strong enough for Europe-facing trade.

01 / Upstream
Farmer network Profiles, support history, production potential, loyalty, and digital adoption.
02 / Source
Farm traceability GPS, boundaries, photos, EUDR evidence, and land-risk verification.
03 / Core ops
Procurement + factory Bean intake, grading, payment reconciliation, line yield, and batch genealogy.
04 / Market
Sales + compliance Order pipeline, customer trust proof, regulations, and export document packs.

The metrics shown throughout are a mix of assessment findings and proposed future-state KPIs, so the company can use these pages both as discussion artifacts and as UI direction.

Visual logic

Warm industrial tones, light paperwork textures, and restrained product-UI density.

Cocoa Traceability Operational clarity
  • Management screens emphasize status, exception handling, and next actions.
  • Field and procurement screens emphasize offline reality, geography, and data quality.
  • Export and compliance screens emphasize proof, completeness, and buyer readiness.

Screen directory

Open the pages below as individual deliverables or move through them as a narrative from farm to Europe-ready shipment.

Recommended product architecture

The real system should not start with ecommerce polish. It should start with a durable farm-to-batch operating spine, then layer sales and customer trust on top.

Core record
Farmer profile
Farm polygon
Bean receipt
Processing batch
Primary users
Agricultural team
Field collectors
Procurement + finance
Factory + QC
Europe proof
Identity
Geolocation
Source certainty
Lot genealogy
Commercial output
Support offers
Risk screening
Supplier economics
Traceable SKU sales

Non-negotiable design principles

  • Offline-aware input because field internet is inconsistent.
  • Vietnamese-first data collection, with English exports for European buyers.
  • Minimal duplicate entry between departments.
  • Evidence-first traceability, not just reporting after the fact.
  • Role-specific views instead of one overcrowded dashboard.

Suggested rollout sequence

If Trong Duc wants the highest operational return, sequence the build around data reliability first, then analytics depth, then market-facing storytelling.

Phase A Farmer, farm, GPS, photos, visit forms, and procurement receipts.
Phase B Batch genealogy, quality links, payment reconciliation, and department reporting.
Phase C Customer proof packs, export readiness, compliance vault, and sales intelligence.