The Aggregation Problem: Why Smallholder Supply Chains Lose Origin at the First Handoff

Pooling is rational

A farmer with half a hectare cannot fill a truck. Aggregation exists because it is the only economically viable way to move smallholder produce, and no traceability system that asks aggregators to stop pooling will ever be adopted. The design question is not how to prevent mixing but how to describe it accurately.

Identity before intake

Origin survives pooling only if identity is captured before the produce enters the pool. Once sacks are combined, no downstream technology can separate them. This is why farm registration and plot mapping are not preparatory work — they are the traceability system. Everything after intake is bookkeeping on identifiers that must already exist.

Proportional attribution, honestly stated

When forty farms contribute to one lot, the defensible claim is not that the lot came from farm seventeen. It is that the lot came from a defined, mapped set of forty plots, with quantities recorded per contributor. Buyers and regulators accept proportional attribution when it is transparent about its own method. They reject it when it is presented as something more precise than it is.

Volume reconciliation as the integrity check

The strongest defence against fraudulent inflow is arithmetic. If a mapped plot area and regional yield range imply a plausible maximum output, and the recorded intake exceeds it, the system should flag the discrepancy at the moment of intake rather than at audit. Reconciliation catches the failure mode that documentation alone never will: produce from unmapped land entering a mapped supply chain.

Designing for the aggregator, not against them

Aggregators adopt systems that make their own work easier — receipts, payment records, quality grading — and abandon systems that only serve the buyer above them. The traceability layer should be a by-product of the aggregator’s daily operation, not an additional task they perform for someone else’s benefit.