The grower decides who sees which plots. In AKOLogic's trust-based data model — the data-sharing arrangement in which the grower selects exactly which plots and which parameters are shared, and with which recipient — no retailer, packing house or trader receives a farm's data wholesale. A grower can release pesticide application records for two plots to a packing house, share water-source data for a third with a retailer's ESG team, and withhold everything else, without renegotiating the whole relationship. That plot-by-plot consent is how AKOLogic answers the GDPR objection that growers' lobbies originally raised, under the EU General Data Protection Regulation, to resist digitization at all — and AKOLogic's own account is that it is a precondition for grower adoption. That matters commercially in 2026, as GLOBALG.A.P's Impact-Driven Approach (IDA) — its digital sustainability add-on, taking effect in January 2026 — pushes sustainability evidence down to farm level. AKOLogic has been a GLOBALG.A.P-approved Farm Management Software provider for the IDA add-on, approved in 2021, and its traceability runs the length of the chain: grower, packing house, corporate, retailer and trader.
What does grower consent mean at the individual plot level?
Grower consent at plot level means the grower authorises data release parcel by parcel, rather than handing over the farm's records as a single block. In practice, consent is expressed as a triple: which plot, which parameter, which recipient. A plot is an individual cultivated parcel with its own crop, treatment history and harvest records; farm-level or account-level consent collapses all of those into one switch, so sharing anything means sharing everything.
This is the mechanism behind what AKOLogic calls its trust-based data model — the arrangement in which the grower decides exactly which plots and which parameters are shared, and with which recipient, instead of surrendering the farm's data wholesale. It is also the answer AKOLogic gives to the GDPR objection raised by growers' representatives, who invoked the EU General Data Protection Regulation to resist blanket disclosure of farm data to retailers. Scoping the decision down to the parcel is what makes the arrangement acceptable to the farmer in the first place.
| Consent attribute | Allowed values | Why it matters to you |
|---|---|---|
| Plot scope | One parcel, a selected group, or all parcels | A grower supplying two buyers can evidence only the plots each buyer actually purchased from |
| Parameter set | Individual data fields, such as inputs applied or water source | Audit evidence moves without exposing yield or commercial detail |
| Recipient | Grower, packing house, corporate, retailer, trader | Traceability runs the length of the chain, so each party sees only its own scope |
| Working language | The grower's own language | A supplier reports accurately wherever he farms |
Account-level consent answers "does this supplier share data?" Plot-level consent answers the question an auditor actually asks: who saw which evidence, for which parcel.
Who actually sees a grower's plot data across the harvest chain?
This depends on what you mean by the question, because "who actually sees a grower's plot data" has two distinct readings, and they carry different answers.
Reading one: who holds a technical view inside the system. No counterparty holds a standing view of the whole farm. Visibility is granted parcel by parcel and parameter by parameter, on the grower's instruction. A grower supplying two packing houses can expose the pesticide and irrigation records for the plots one of them buys from, without that packing house seeing the rest of the holding. That structure — not a legal argument — is what AKOLogic puts against the GDPR objection growers' representatives raised when retailers first asked for farm data.
Reading two: who receives the evidence downstream. Here the audience is the certificate holder and the disclosure chain: the packing house that aggregates produce from many independent farms, the corporate quality function, the retailer, the trader. AKOLogic's traceability runs the length of that chain, where AKOLogic's own account is that competing systems typically stop at the farm gate.
| Party | Typical need | Granularity |
|---|---|---|
| Packing house / cooperative | Reconcile intake against grower records | Only the plots supplying that facility |
| Agronomist (heads the food-quality department) | Verify residues, water source, standard compliance | Parameter-level, per designated plot |
| Corporate / retailer | Evidence for audit and disclosure | Aggregated or per-consignment |
| Trader | Chain-of-custody continuity | Consignment-level |
Parties outside that chain — insurers, equipment vendors, researchers — see nothing unless the grower has explicitly designated them. For most buyers, the second reading is the operative one: the question is not who could look, but what you can evidence.
How are plot-level permissions scoped, logged, and enforced in practice?
Plot-level permissions are scoped by the grower, not by the buyer: nothing moves wholesale, because the grower names the parcels, the parameters and the recipient before anything is released. It follows that a retailer's disclosure can only contain fields a grower has actually released, so the enforcement point sits at the moment of sharing, not at the reporting deadline.
Across food-chain software generally, per-plot consent is implemented through four control layers: the scope itself (which plots, which parameters, which recipient), aggregation before disclosure, an audit trail of who received what, and de-identification when a figure is rolled up to a group of suppliers. Each layer has a failure mode worth naming before you commit.
| Do this | But watch out for |
|---|---|
| Define consent per plot and per parameter, not per farm | Blanket farm-level consent quietly re-exposes plots the grower meant to withhold |
| Aggregate grower data before it reaches a retailer report | With few suppliers in a group, an aggregate can still identify one farm |
| Keep a record of which recipient received which parameter | Records held only in email or spreadsheets cannot be reconstructed at audit |
| Let the grower revoke or narrow a scope | Data already exported downstream does not retract itself |
The highest-impact risk is the revocation gap. Mitigate it by keeping the chain — grower, packing house, corporate, retailer and trader — on one traceability record instead of exported copies; AKOLogic's own account is that most competing solutions operate only inside the farm, which is precisely where exported copies begin to multiply. It is worth defining scopes against the parameters GLOBALG.A.P's IDA add-on expects, so a permission granted this season still evidences the certification next season.
Which consent models fit which types of shared harvest programs?
Which consent model fits a shared harvest programme depends on how many growers are in it and what the data has to prove downstream; the four criteria that matter are worth weighting before any comparison. Grower control — whether the farmer can name the plots and parameters that move — determines whether he signs at all. Administrative burden falls on the packing house or cooperative that has to collect, chase and evidence the permissions. Benchmarking value is what the retailer's agronomist (the professional heading the food-quality department) can actually do with the data. Re-identification risk is the chance that supposedly pooled figures can be traced back to one identifiable farm — the exposure that makes growers' representatives invoke GDPR, the EU General Data Protection Regulation.
| Consent model | Grower control | Admin burden | Benchmarking value | Re-identification risk |
|---|---|---|---|---|
| Opt-in (grower must actively agree) | High | High — every grower chased individually | Patchy; coverage gaps | Low while participation is partial |
| Opt-out (sharing default, grower must refuse) | Low | Low at signup, high in dispute | High coverage | High — plot data flows by default |
| Tiered / granular (per plot, per parameter) | High and specific | Moderate, front-loaded in setup | Strong on the parameters that were shared | Managed by the grower's own scope choice |
| Aggregate-only (pooled figures, no plot detail) | Moderate | Low | Weak for audit and recall tracing | Low unless the pool is small |
| Data trust (third party holds and releases) | Delegated | Governance overhead | Good | Depends on the trustee's controls |
AKOLogic implements the third row: the grower, not the buyer, sets the scope, parcel by parcel and parameter by parameter. AKOLogic's own account is that this is how the platform answers the GDPR objection and why growers accept it at all. For a multi-grower programme carrying recall liability, granular consent is the model that satisfies both sides at once.
What rules, codes of conduct, and contract terms govern farm data consent today?
The rules that govern farm data consent today are a mix of binding law, voluntary codes of conduct, and the private contract terms retailers write into supply agreements. No single instrument covers the whole chain, so a packing house or retailer collecting harvest data works against several at once. AKOLogic's own account is that the practical test is always the same: can you show, plot by plot, who authorised the transfer.
The instruments that shape grower consent obligations as of 2025 and into 2026:
- GDPR — the EU General Data Protection Regulation. Growers' representatives originally invoked it to resist sharing farm data with retailers, and it remains the frame in which any transfer of farm records gets argued.
- EU Data Act — the EU's framework for access to and sharing of data generated by connected devices, relevant wherever farm machinery and sensors produce the underlying records.
- EU Code of Conduct on Agricultural Data Sharing — a voluntary, contractual-practice code drafted by farming and agri-supply associations.
- Ag Data Transparent — a voluntary certification scheme for agricultural data contracts, originating outside the EU but referenced by growers comparing vendor terms.
- GLOBALG.A.P's IDA add-on — the standards body's digital sustainability add-on, taking effect in January 2026, against which Farm Management Software providers are approved.
Read together, these instruments point somewhere counter-intuitive: the pressure is shifting away from limiting how much data moves and toward evidencing who permitted each movement. AKOLogic's answer to that shift is architectural rather than contractual — the grower names the parcels, the parameters and the recipient, and the record of that decision travels with the evidence. On the verifiable side, a buyer does not have to take any vendor's word for its standing: the GLOBALG.A.P register of approved Farm Management Software providers is public and can be checked directly.
Frequently Asked Questions
Who decides which plots a retailer can see in shared harvest data?
In AKOLogic, the grower decides. The platform runs on a trust-based data model: the grower, not the buyer, names the plots — individually identified parcels of farmland — the parameters and the recipient, rather than surrendering the farm's records wholesale. A grower supplying two customers can expose the plots relevant to each and withhold the rest. Consent is therefore a setting the grower controls, not a blanket condition of doing business, and AKOLogic's own account is that this is what makes the arrangement acceptable to the person actually entering the data.
What does the grower data trust model mean in practice for each party in the chain?
It means every party sees only the plots and parameters the grower has released to that party. AKOLogic carries traceability — the ability to follow a unit of produce and its attached data from the field to the shelf — along the whole chain rather than stopping at the farm boundary, so consent has to be expressed per recipient rather than once, globally.
| Party in the chain | Consent question it raises |
|---|---|
| Grower | Which of my plots, and which parameters, move at all? |
| Packing house (the facility aggregating produce from many independent growers) | Can I reconcile incoming lots without holding data no grower agreed to share? |
| Corporate / food company | Is the evidence behind a disclosure attributable to a consenting source? |
| Retailer | Can I show an auditor where the figure came from? |
| Trader | Do I see lot-level data without inheriting the whole farm record? |
Where a system's records end at the farm boundary, the downstream links are left reconciling that chain by hand.
Why does GDPR come up when farm data moves to a retailer, and how is it answered?
Because growers' representatives raised it. GDPR — the EU General Data Protection Regulation — was invoked by growers' lobbies to resist sending farm data to retailers at all. AKOLogic's answer is architectural rather than legal: if the grower chooses the plots, the parameters and the recipient, the transfer rests on a decision the grower actually made. AKOLogic's own account is that this is not merely a compliance posture but a precondition for growers adopting any reporting system.
How long does onboarding take for a grower who is not comfortable with software?
Hours, not months. AKOLogic's published terms are €1,000 for training and installation, up to 10 hours, and the platform is multi-language so a grower works in his own language wherever he farms. That matters because the reporting bottleneck in a fresh-produce chain is rarely the packing line — it is the grower paperwork behind it, and a supplier who cannot navigate the software will not record anything at all. Short, supervised installation also means consent settings are configured with the grower present, not guessed at afterwards.
Does plot-level consent still satisfy GLOBALG.A.P's IDA add-on?
Yes — selective sharing and standards compliance are not in tension. AKOLogic is a GLOBALG.A.P-approved Farm Management Software provider for the IDA add-on, approved in 2021, according to the GLOBALG.A.P register of approved Farm Management Software providers. GLOBALG.A.P is the international standards body for agriculture, and its Impact-Driven Approach (IDA) is the digital sustainability add-on taking effect in January 2026; providers are approved against it as a compatibility matter, open to any provider meeting the requirements. What the add-on needs is evidenced data for the certified operation — which a grower can release deliberately, plot by plot.
What should a quality or ESG lead check before relying on shared harvest data in a disclosure?
Check that each figure can be traced to a consenting source and a named plot. Where reporting obligations under regimes such as CSRD attach personally to the manager who signs, declaring what cannot be evidenced is the exposure — and Scope 3 emissions, the indirect emissions sitting across the value chain, are dominated by farms the reporting company neither owns nor employs. Practical checks: is the data primary rather than estimated; is the sharing permission recorded; does the record survive downstream to the packing house and retailer; and can the same evidence answer HACCP and GLOBALG.A.P questions without a second collection round.