From Plot to Container: Proving Your Volumes Match Your Polygons Under EUDR
Perfect polygons cannot save a filing whose volumes exceed what the plots could grow. Yield plausibility math, mixing risks and the proof chain buyers want.
There is a second way to fail EUDR scrutiny that has nothing to do with geometry. Your polygons can be closed, valid and beautifully mapped, and the filing still falls apart on a question a reviewer can ask with a calculator: could these plots have grown this much product? A due diligence statement carries both the geolocation and the quantity, which means every filing quietly asserts an equation. Twenty-five tonnes of cocoa against plots that could plausibly yield four hundred is fine. Six hundred tonnes against the same plots is a declaration that somewhere, product from unlisted land entered the lot. This post is about that equation: how to run it on yourself before anyone else does, where mixing actually creeps in, and what a defensible plot-to-container proof chain looks like.
The plausibility math
The check is one line:
plausible annual output = total plot area × realistic yield per hectare
Worked example, a cocoa cooperative in West Africa.
Step 1: sum the mapped area. The registry holds 350 plots totalling 812 hectares. Step 2: pick a defensible yield figure. Regional smallholder cocoa yields run roughly 400 to 600 kilograms per hectare; take 450 as a documented midpoint. Step 3: multiply: 812 × 450 = 365,400 kilograms.
Result: these plots plausibly produce about 365 tonnes of cocoa per year.
Now compare with what the statements declare. Containers totalling 300 tonnes across the season: comfortable. Statements totalling 600 tonnes against the same plot list: the plots cannot have grown it, and the surplus 235 tonnes came from land nobody declared. No satellite image is needed to spot this; the filing refutes itself. Which is exactly why running the calculation internally, per supplier and per season, is the cheapest audit you will ever perform.
Why the answer cannot be mass balance
Certification schemes taught the industry a comfortable habit: mass balance, where compliant and non-compliant volumes mix physically and the paperwork balances at the aggregate. EUDR does not work that way. The regulation requires each product placed on the market to be traceable to the specific plots that produced it, and mixing with commodities of unknown or undeclared origin makes the entire mixed lot non-compliant, not the blended percentage. Segregation, or at minimum controlled aggregation where every contributing plot is on the statement, is the operating model. If a warehouse cannot say which farmers' deliveries are in a lot, the lot cannot honestly say which plots grew it.
Where mixing actually creeps in
Almost never as fraud at the top. It enters low and quietly. Peak-season side-buying, when a cooperative tops up a short container with product from non-member farmers who are not in the registry. Shared drying yards and warehouses, where lots physically merge before anyone assigns them. Aggregators who buy across village lines and deliver a single anonymous heap. Each is an ordinary commercial behaviour that was harmless for decades and is now a compliance breach, because the container's statement lists plots that did not grow part of its contents.
The fix is not moral exhortation, it is capture at the weighbridge: every delivery recorded against a farmer ID at the moment of weighing, every lot built from recorded deliveries, no anonymous intake. Where side-buying is commercially unavoidable, the honest options are two: bring those farmers and their plots into the registry, or keep their product in a separate, non-EU-destined stream. What is not an option is averaging it away.
The proof chain, end to end
A defensible chain has four links, each boring on its own. Farmer to plots: the registry, stable IDs, mapped geometry. Farmer to deliveries: weighbridge or collection records with dates and kilograms. Deliveries to lots: which intake built which lot, preserved through processing. Lots to statements: the container's DDS listing exactly the plots behind its contributing deliveries. With those four links, the plausibility equation closes at every level: no farmer delivers more than their plots support, no lot contains unrecorded intake, no statement declares volume its plots cannot carry.
Run the reconciliation at season close, not at audit time. A farmer whose deliveries imply 1,900 kilograms per hectare is either the best agronomist in the region or aggregating neighbours under his ID, and finding out in October is a conversation while finding out during a buyer review is a crisis.
What buyers are starting to ask for
EU operators carry the legal exposure, checks target a share of them every year, and fines scale to 4 percent of turnover, so their diligence is flowing upstream fast. The requests arriving in producer inboxes now go beyond the GeoJSON: delivery records for the season, the member registry, the reconciliation between the two. Exporters who can answer inside a day are discovering it functions as a commercial advantage, because a buyer choosing between two origins at equal price will take the one whose numbers already add up.
Frequently asked questions
What yield figure should we use, and who decides it is realistic?
Use published regional benchmarks or your own multi-year delivery history, and write down the source. The point is not precision, it is defensibility: a documented 450 kilograms per hectare beats an undocumented 800 every time someone checks.
Our declared volumes exceed plausible output because members underreported plots. Now what?
That is the benign version of the problem and it has a benign fix: map the missing plots and add them to the registry and the statements. The equation does not care why it fails, but reviewers do, and incomplete mapping is curable in a way undeclared sourcing is not.
Is certified mass balance product simply banned from the EU then?
Certified product is fine; the mass balance accounting alone is what cannot carry an EUDR claim. Plenty of certified supply chains are re-plumbing to segregated or fully documented aggregation precisely so the certificate and the plot-level traceability coexist.
Do authorities really run this kind of cross-check?
The infrastructure points that way: statements carry quantity and geolocation together, checks are risk-based, and volume-versus-area is the easiest red flag to automate. Assume the calculator will be applied, because you can apply it to yourself today for free.
Related reading
Validating plot data by hand doesn't scale past a handful of suppliers
Qelvyn builds the internal tools traders and cooperatives use to validate due diligence statements before submission, track plot-to-container traceability, and catch a rejected GeoJSON file before the EU Information System does. If your EUDR data pipeline has outgrown manual checks, tell us what you're tracking and we'll say plainly whether a system pays for itself.