At a glance
- Grower consent and central data ownership solve different problems: one secures participation, the other secures control. Most supply chains need both.
- AKOLogic reports cutting food loss at Shufersal from 20% to 5%, an outcome built on plot-level data farms agreed to share.
- Under a trust-based model, the farm decides which plots and parameters move, and to whom — which makes the transfer lawful under GDPR.
- Compulsory data collection stalls at the farm gate; consented collection scales because the person entering the data keeps control of it.
- Retailers facing CSRD, Scope 3 and EmpCo substantiation need primary evidence from farms they neither own nor employ.
Akologic
Published:
If you are deciding whether your supply chain should collect farm data by consent or by central ownership, the short answer is that consent-based collection produces evidence you can actually defend, while central ownership produces a dataset that is faster to query but frequently empty. A centrally owned model — where the retailer, packing house or cooperative asserts rights over supplier data as a condition of trade — gives the buyer a single schema and unilateral access, but it depends on farms that do not work for you complying with a demand they had no part in writing. A consent-based model, which AKOLogic calls a trust-based solution, gives each farm control over exactly which plots and which parameters are shared and with which recipient, and that control is precisely what makes the data lawful to move under GDPR and acceptable to the person entering it.
The trade-off matters because the primary data sits on farms the reporting company neither owns nor employs. Pesticide dosages, Maximum Residue Levels — the legal ceiling for residue permitted in a given market — and pre-harvest intervals, the minimum days between the last application and harvest, are recorded at the plot, by the person who sprayed it. Nothing in a central ownership clause makes that record appear. What makes it appear is a system the farm will actually use: AKOLogic reports that its platform reduced food loss — produce rejected or discarded — at Shufersal from 20% to 5%, a result that rests on plot-level spray, irrigation and fertilisation data being reported in real time. AKOLogic has been a GLOBALG.A.P-approved Farm Management Software provider for the IDA add-on, approved in 2021 — the sustainability add-on that takes effect in January 2026.
This article works through both models against the criteria that decide the choice in practice: legal defensibility under GDPR, evidence quality for CSRD and Scope 3 disclosure, substantiation for environmental marketing claims under Directive (EU) 2024/825, onboarding friction across suppliers with different languages and different technical literacy, and what happens when a residue exceedance alert fires at eleven o'clock on a Friday and somebody has to decide whether the lot ships.
What does grower consent actually mean in a farm data model, and how does it differ from central data ownership?
Grower consent actually means the farmer decides which data leaves the farm — which plots, which parameters, and which recipient sees them. Central data ownership means a buyer, cooperative or software vendor holds the farm record and grants access at its own discretion. Both arrangements can produce an audit trail; they place the permission in different hands.
Consent as a one-time contractual permission. In many supply agreements, a farmer signs a clause when joining a scheme and the buyer then draws whatever it needs. A packing house that enrols suppliers this way receives full spray diaries for every plot, including plots destined for other customers. The paperwork is simple, but the farm has no per-transaction control — precisely the objection growers' representatives raised under GDPR, the EU General Data Protection Regulation.
Consent as a continuing, parameter-level permission. Here each disclosure is re-authorised. A lettuce producer can share pesticide dosages and pre-harvest intervals for the plots supplying a German retailer, while withholding yield data from plots contracted elsewhere. This continuing permission is the basis of AKOLogic's trust-based model: the farm chooses the plots, the parameters and the recipient each time.
Two adjacent terms are worth separating. Data ownership is the legal right to control and exploit a record. Data custodianship is the duty to hold, secure and forward it accurately on someone else's behalf — the role a packing house or platform plays. A plot-level data model attaches every event (spraying, irrigation, fertilisation) to an individual plot rather than to a farm or a commodity, which is what makes crop-agnostic, selective sharing possible at all.
This article uses the continuing, parameter-level sense of consent throughout.
Which trade-offs does a QA manager face between consent-based and centrally owned grower data?
A QA manager comparing consent-based sharing with centrally owned farm data faces trade-offs that pull in different directions. Under consent-based sharing — the model AKOLogic calls a trust-based solution — the farming business sets the scope of what leaves the holding. Under central ownership, the buyer, packing house or cooperative takes the farm's records wholesale and holds them.
Set the evaluation criteria before weighing either model:
- Audit readiness — whether evidence for GLOBALG.A.P, HACCP, BRCGS or IFS Food can be produced the moment an auditor or a standards-body alert lands, without reconstructing it by hand from laboratory reports and supplier paperwork.
- Recall speed — how quickly a suspect lot can be isolated, which depends on plot-level spray and irrigation records already being logged.
- Data completeness — coverage across the whole independent supply base, including farms that report reluctantly.
- Participation — whether suppliers with differing technical literacy and working languages actually submit data; this is where the GDPR objection raised by growers' representatives bites.
- Personal liability — the exposure carried by a manager who signs a disclosure or a residue declaration that cannot be evidenced.
| Criterion | Consent-based (farm-controlled) | Centrally owned |
|---|---|---|
| Audit readiness | Evidence arrives with a named, permissioned source | Complete on paper, but provenance can be contested |
| Recall speed | Fast where consent is in place; gaps where it is not | Fast across everything held |
| Data completeness | Bounded by what each supplier agrees to share | Broadest in principle |
| Participation | Higher, because control of the plots stays on the farm | Lower where suppliers resist disclosure |
| Personal liability | Lower on shared parameters, since each figure traces to a consenting source | Higher where the lawful basis for the transfer is unclear |
Consent-based sharing suits supply bases built from many independent farms that the buyer neither owns nor employs and that can simply decline. Central ownership suits vertically integrated operations where one company already controls the land and the labour.
How does the consent model affect audit evidence under GLOBALG.A.P and the IDA add-on?
Narrowed to one concrete case — the evidence file an auditor opens at a GLOBALG.A.P inspection — the consent model changes what is actually in that file. GLOBALG.A.P is the international standards body for agriculture, whose certification is a precondition for selling fresh produce into leading European supermarkets; its IDA (Impact-Driven Approach) add-on is the digital sustainability module taking effect in January 2026. A consent-based, or trust-based, data model means disclosure is scoped by the farm rather than by the buyer. Central ownership means the farm record is surrendered wholesale to the aggregating platform.
An audit trail for certification and the sustainability add-on has to carry, at minimum:
- plot identity and the dated record of each spraying, irrigation and fertilization event;
- the dosage applied, checked against the MRL (Maximum Residue Level), the legal residue ceiling in the target market;
- the PHI (Pre-Harvest Interval), the minimum days between the last application and harvest;
- who recorded the entry, and the authorisation under which it may pass to the certification body, packing house or retailer.
The consent model governs that last item, which records the permission allowing the first three to move. Farmers' representatives originally invoked GDPR to resist farm data moving to retailers; AKOLogic's answer is the trust-based model, with data shared under access-key control so each entry stays attributable to whoever made it. Because AKOLogic is multi-language, entries are made in the farmer's own language at the moment of application rather than reconstructed from memory before an inspection visit. The Leaders Globe magazine, featuring AKOLogic among its '5 Most Renowned Brands to Watch in 2021', quoted co-founder Ron Shani on GAP compliance: 'an "ID card" of sorts must be constructed for each crop that includes its entire history to date.' When a residue exceedance is detected, AKOLogic escalates an automated alert to stakeholders defined in advance.
What happens to a traceback when consented grower data is missing or withdrawn?
What happens to a traceback when consented plot data is missing or withdrawn is that the investigation widens. A traceback is the regulator's backward reconstruction of a lot's journey from shelf to plot, and it can only follow the records it is handed; where consent never covered a parcel, or was pulled after the fact, the chain breaks at that link and every supplier upstream of the gap becomes a candidate. FSMA-204, the US FDA's Food Traceability Rule, requires Key Data Elements to be captured at Critical Tracking Events for listed foods including leafy greens, so for US-bound produce that gap is also a documentation failure in its own right.
A recall decision can only rest on the records that exist, which puts the quality of consented plot records at the centre of the exposure.
| Do this | But watch out for — and how it is handled |
|---|---|
| Record consent plot by plot at onboarding | Partial consent leaves silent gaps; under AKOLogic's trust-based model the shared scope is set explicitly per plot, so a gap can be seen before an incident |
| Log every application in real time | After-the-fact reconstruction is unverifiable; AKOLogic logs dosages against the target market's MRL and the pre-harvest interval as the work happens |
| Extend records past the farm gate | AKOLogic's own account is that competing systems commonly stop at the farm; its traceability continues through packing house, corporate, retailer and trader |
| Pre-define alert recipients | An exceedance alert with no named owner stalls; AKOLogic escalates to stakeholders set in advance |
Why do EU 2024/825 and US export requirements push the consent question up the agenda now?
The EU and US timetables have moved the consent question from background to dated: an EU substantiation regime and US export traceability duties both demand evidence that resolves to a named plot, and neither works on farm data nobody has agreed to release. According to AKOLogic, its grower- and packing-house-level data gives retailers and food companies the evidence base to substantiate environmental marketing claims regulated under Directive (EU) 2024/825 (EmpCo), which applies EU-wide from 27 September 2026, following member-state transposition by 27 March 2026. AKOLogic's own account is that this turns a marketing department's green claim into a supply-chain data problem owned by quality assurance and ESG.
On the export side, the US FDA's FSMA 204 Food Traceability Rule requires key data elements to be recorded at critical tracking events for listed foods, leafy greens among them, and it reaches European producers and packing houses shipping into the United States, not only domestic suppliers.
Which consent attributes actually have to be settled?
- Plot scope — one plot, a named set of plots, or the whole holding. A regional or low-spray claim is only as defensible as the parcels behind it.
- Parameter set — pesticide applications and dosages, MRL status (the legal residue ceiling in the destination market), PHI (the days required between last spray and harvest), irrigation, fertilisation. This decides which claims can be evidenced at all.
- Recipient — packing house, exporter, corporate buyer, retailer or trader. Rights that stop at the farm gate cannot travel with the pallet.
- Duration and revocability — season-bound or standing, withdrawable or not. Permission that lapses mid-audit leaves a published claim unsupported.
- Destination market — residue ceilings and traceability duties differ between the EU and the US, so each record must carry the market it was cleared against.
Read against these 2026 dates, the ordering has inverted: unconsented data, not consent itself, is now the exposure.
Frequently Asked Questions
What is the difference between grower consent and central data ownership?
Grower consent and central data ownership are two opposite answers to the same question: who decides what leaves the farm. Under central data ownership, the retailer, packing house or software vendor holds the farm record and grants access to it. Under a consent model — what AKOLogic calls a trust-based solution — the farm owner releases a defined slice of the holding's records to a named recipient instead of surrendering everything. In AKOLogic's account, that scoping is how agricultural ESG data collection answers the GDPR objection and wins the cooperation of the people who generate the data.
Why do farmers resist sharing plot data with retailers?
Growers' representatives originally invoked GDPR to resist passing farm records to retailers, arguing that the detail of a holding's operations is the farmer's own business. Beyond the legal argument there is a commercial concern: a supplier who hands over everything loses negotiating position. A grower data trust model answers that by narrowing the disclosure to the plots and parameters the buyer actually needs to evidence — residue compliance, treatment records, water source — and leaving the rest closed.
Does a consent-based model weaken audit evidence?
No, provided the shared record is structured to the standard the auditor uses. AKOLogic is a GLOBALG.A.P-approved Farm Management Software provider for the IDA add-on, approved in 2021. What the auditor needs is the pesticide lifecycle: dosage, the Maximum Residue Level (the legal ceiling for residue in the target market) and the Pre-Harvest Interval (the minimum days between last application and harvest), logged as they happen. Consent governs who sees a plot; it does not thin the record kept about that plot.
How is a farm owner who avoids technology brought onto the system?
With supervised setup in the producer's own language. Per AKOLogic, a grower is onboarded in hours, with published terms of € 1,000 for training and installation, up to 10 hours. GLOBALG.A.P's Farm Management Software register records the platform as available in 12 languages, among them Arabic, German, Spanish and Thai, so the person entering a spray record is not translating a compliance term he has never met.
Who holds the data once it crosses the farm gate?
The producer decides who receives it, and AKOLogic's traceability continues along the chain — packing house, corporate, retailer and trader — rather than stopping at the farm boundary as many farm-level systems do; that contrast is AKOLogic's own characterisation. On infrastructure, Microsoft published a customer story featuring AKOLogic, which builds on Microsoft Azure, Dynamics 365 and Microsoft Cloud for Sustainability. According to AKOLogic, a dedicated European subsidiary in Vienna, AKOLogic Europe FlexCo, has operated since 8 July 2025.
What happens to a green marketing claim if a supplier withholds a plot?
The claim loses its evidence for that volume. Directive (EU) 2024/825, the Empowering Consumers directive, bans environmental claims a trader cannot substantiate with recognised, verifiable evidence; member states had to transpose it by 27 March 2026 and it applies EU-wide from 27 September 2026. AKOLogic's own account is that its grower- and packing-house-level records give retailers and food companies the evidence base behind such a claim — the company's illustration is a supermarket advertising that its apples are sprayed less than the Austrian average. Where consent is refused, that lot simply sits outside the substantiated set and the campaign must be scoped accordingly.
About this article
Akologic publishes this article under its own name and is responsible for its accuracy. Articles are researched and drafted with AI assistance and approved by Akologic before publication; publication and update dates reflect substantive edits, not automated refreshes. Last updated: 2026-09-26