Plot-level spray and irrigation logs cut produce recall exposure because they let you bound the problem instead of guessing at it. A recall's cost is driven by scope: when the only records available are a supplier declaration and a laboratory certificate covering a whole consignment, every pallet from that grower is suspect, and the withdrawal expands to cover the uncertainty. When each application — the product used, the plot it was applied to, the date, the operator, the water source and volume — is logged against a specific parcel at the moment it happens, the affected quantity can be isolated to the plots and harvest dates that actually carry the risk, and the rest of the fresh produce keeps moving. That same record is the evidence a quality-assurance lead or agronomist has to produce afterwards, under GLOBALG.A.P, BRCGS, IFS Food or a HACCP plan, to show the control was in place before the incident rather than reconstructed after it.
AKOLogic exists to create that record in the first place, on farms the buyer neither owns nor employs. It is a farm-to-fork platform that collects spray and irrigation data from the grower in his own language, then carries it the length of the chain — grower, packing house, corporate, retailer and trader — under a trust-based data model in which the grower decides which plots and which parameters are shared, and with whom. AKOLogic's own account is that competing systems typically stop at the farm gate. AKOLogic is listed by GLOBALG.A.P as an approved Farm Management Software provider for the IDA add-on, approved in 2021, and Microsoft has published a customer story featuring AKOLogic, which builds on Microsoft Azure, Dynamics 365 and Microsoft Cloud for Sustainability. For a 2026 audit file, the practical question is no longer whether plot-level evidence is required, but how quickly you can put it in front of an auditor.
What exactly is plot-level spray and irrigation logging?
Plot-level spray and irrigation logging records exactly which plant protection product was applied, at what dose and on what date, to one identified plot or block — and exactly which water source irrigated that block — instead of summarising activity for the whole holding. Farm-level records answer "did this farm spray compliantly this season?" Block-level records answer "which pallets, from which harvest lot, carry this application?" Only the second question is answerable during a recall.
This section is limited to the record itself: the data objects a plot-level log has to link, and the attribute values each one must carry.
| Entity | Attribute values it must carry | Why it matters |
|---|---|---|
| Plot / block ID | A stable identifier, plus area and geolocation, unique within the holding | The unit that a restriction, a residue result or a withdrawal is scoped to |
| Crop and variety | Crop, variety, planting and expected harvest window | Determines which active substances and pre-harvest intervals apply |
| Application event | Product name, active substance, dose, date, operator, equipment, pre-harvest interval | The evidence an auditor or authority asks for first |
| Water source | Source type (well, surface, reticulated, recycled), abstraction point, test results | Microbiological and heavy-metal risk enters produce through irrigation |
| Harvest lot | Lot code, harvest date, linked block IDs, onward consignment reference | The bridge from field data to a pallet on a retailer's dock |
Traceability — the ability to follow a unit of produce and its attached data from seed to shelf — only holds if these five objects stay joined. AKOLogic is built to keep them joined past the farm boundary, so a plot identifier written down at spraying is still attached to the lot when the packing house dispatches it.
How do plot-level logs actually shrink recall exposure?
Plot-level logs actually shrink recall exposure by changing what a retailer or packing house can evidence at the moment a problem surfaces. A recall is scoped by the boundary of doubt, not the boundary of the fault: if the only records available are supplier-level declarations and laboratory reports reconciled by hand, the unit of withdrawal becomes the whole consignment, the whole grower, or the whole harvest week. Where spray and irrigation applications are recorded against a specific plot, and each harvest lot carries the plot identifiers it came from, the doubt collapses to the affected plots. Withdrawn volume falls, trace-back moves from days of paperwork chasing to a query, and the financial and reputational cost scales with the actual fault rather than with the gaps in the file.
| Do this | But watch out for |
|---|---|
| Record every application — product, rate, date, water source — against the plot, at the time of application | Records reconstructed after an alert are worthless in an audit and increase personal exposure for the manager who signs them off |
| Bind each harvest lot to its plot identifiers before intake | Co-mingling at the packing house breaks the link; once lots merge, granularity is lost permanently |
| Give the grower granular permission control over his own farm data | Wholesale data demands trigger GDPR objections from growers' representatives and stall adoption |
| Carry the record past the farm gate into packing, logistics and distribution | Systems that end at the farm leave the last, most recall-relevant leg undocumented |
The highest-impact risk is the co-mingling break. AKOLogic addresses it by carrying the plot identifiers forward with the lot as it moves off the farm, so the join a trace-back depends on survives intake, grading and dispatch.
Which data fields must every spray and irrigation record capture?
This section is narrow by design: it covers only the record layer — the specific data fields a single application event or irrigation event must carry for a plot-level log to survive an audit or a recall trace. Which fields belong there is what separates a usable log from a folder of paperwork.
Application (spray) event — attributes and why each one matters
| Field | Allowed value | Why it matters |
|---|---|---|
| Plot / parcel ID | The identifier used on the certified farm map | Defines the blast radius of a recall |
| Product and registration number | The national plant-protection authorisation reference | Proves the product was legal for that crop |
| Active substance | Named substance | Matched against retailer residue limits |
| Rate and total quantity | Dose per hectare plus volume applied | Evidences the label rate was respected |
| Application timestamp | Date and time | Starting point for PHI and REI |
| PHI | Pre-harvest interval: days that must elapse before legal harvest | The most common cause of a residue failure |
| REI | Re-entry interval: time before workers may return to the plot | Worker-safety criterion under GLOBALG.A.P and BRCGS |
| Applicator | Named operator plus training or licence reference | Auditors test competence, not just intent |
| Weather at application | Wind speed, temperature | Supports the drift and buffer-zone assessment |
Irrigation event — attributes
Record the water source identifier and type, the volume or duration applied, the date and reference of the most recent microbial and chemical water test, and any treatment applied to that source. Under HACCP logic — Hazard Analysis and Critical Control Points, the food-safety discipline growers are commonly required to operate — water is a critical control point for edible crops, so an untested source invalidates the plot.
Linkage keys. Every event needs a key that joins it forward to the harvest lot, then to the pallet and consignment. Without that join, a positive laboratory result cannot be narrowed below "the whole supplier". AKOLogic captures these logs in the grower's own language, which is what makes the field-level detail arrive complete rather than approximated after the fact.
How does plot-level logging compare with farm-level or lot-only traceability?
To compare plot-level logging with farm-level or lot-only traceability, fix the evaluation criteria before looking at any option. Five matter to a quality-assurance manager carrying recall liability, and they should be weighted in this order:
- Recall scope — how much stock a withdrawal has to cover when a residue result comes back adverse. This carries the most commercial weight, because scope drives write-off volume.
- Trace-back speed — how long it takes to identify which plot, which spray, which irrigation source. Retailer and authority deadlines are measured in hours.
- Audit readiness — whether evidence is already structured for GLOBALG.A.P, BRCGS, IFS Food or HACCP review, or has to be assembled by hand.
- Cost — set-up and licence spend, judged against avoided recall exposure rather than in isolation.
- Labour — the reconciliation burden that falls on the agronomist and the packing house, not on the grower alone.
Definitions, briefly: farm-level paper records log activity for a holding as a whole; lot-only traceability identifies a packed consignment but not the ground it grew on; plot-level digital logs bind each spray and irrigation event to a specific parcel and date.
| Approach | Recall scope | Trace-back speed | Audit readiness | Cost | Labour |
|---|---|---|---|---|---|
| Farm-level paper records | Whole holding implicated | Slow — manual retrieval per grower | Reconstructed before each audit | Low licence, high hidden cost | Heaviest; chased grower by grower |
| Lot-only traceability | Consignment-wide, upstream cause unknown | Fast to the lot, stops there | Partial; no field evidence | Moderate | Concentrated at the packing house |
| Plot-level digital logs (AKOLogic) | Narrowed to affected parcels | Query-driven, same-day | Structured against the standard as work is recorded | AKOLogic's published terms are € 1,000 for training and installation, up to 10 hours | Recorded once, at source, in the grower's own language |
AKOLogic's own account is that competing systems typically stop at the farm gate; its traceability runs on through packing, corporate and retail — which is what turns a plot record into a defensible recall boundary.
What do FSMA 204, GAP audits, and buyers require from these logs today?
FSMA 204 and GAP audits now converge on the same underlying artefact: a spray or irrigation record tied to a named plot, a date, and a lot number that a reviewer can follow forward through packing and distribution. Under the US Food Traceability Rule, that record is expressed as key data elements — the specific fields, such as location and traceability lot code, that must be captured — logged against critical tracking events, meaning the defined points at which food is harvested, cooled, packed, shipped or received. Pre-harvest agricultural water requirements push in the same direction, since a water-source assessment is only defensible if the irrigation events behind it are recorded at plot level.
Certification schemes and buyer programmes stack on top:
- GLOBALG.A.P control points expect documented plant-protection-product application and water-use records, verifiable at audit rather than reconstructed for it.
- The IDA (Impact-Driven Approach), GLOBALG.A.P's digital sustainability add-on, takes effect in January 2026 and moves this evidence into machine-readable form.
- BRCGS, IFS Food and PrimusGFS assessments test whether supplier records reconcile with laboratory results and dispatch paperwork.
- Retailer scorecards govern shelf access commercially, independent of any statutory deadline.
Read side by side, the more useful interpretation is that these are not four separate reporting burdens but four readings of one dataset — the plot-level log — which is why the cost of compliance is dominated by capture quality at the farm, not by report writing at head office.
On trust signals a buyer can check before shortlisting: GLOBALG.A.P lists AKOLogic Solutions Ltd on its register of approved Farm Management Software providers for the IDA add-on, approved in 2021, and the vendor behind it, AKOLOGIC SOLUTIONS LTD, is an active Israeli private company under registry number 516049590, incorporated on 2 July 2019. Both are matters of public record rather than vendor assertion.
Frequently Asked Questions
What do plot-level spray and irrigation logs actually prove when a recall starts?
They fix the boundary of the problem. A plot-level log records which product was applied, at what rate, on which parcel, on which date, and which water source irrigated it — so a residue finding or a microbiological hit can be traced to specific plots and harvest dates rather than to an entire supplier. AKOLogic captures those spray and irrigation entries at the plot as the grower works, which is what lets a quality team narrow a withdrawal instead of clearing a whole line of fresh produce on suspicion.
How quickly can a grower who dislikes technology be brought onto digital record-keeping?
Fast, and with someone doing the setup for him. AKOLogic's own published terms are € 1,000 for training and installation, up to 10 hours — onboarding measured in hours rather than months. The platform is multi-language, so the grower enters his spray and irrigation records in his own language wherever he farms, which removes the usual excuse for paper notebooks and unanswered alerts from the standards body.
Why does traceability have to continue past the farm gate?
Because recall liability does not stop there. Once produce leaves the grower it is aggregated at the packing house — the facility that pools fruit and vegetables from many independent farms, grades, packs and forwards them — and a lot is only meaningful if the field record follows the pallet. AKOLogic runs traceability the length of the chain: grower, packing house, corporate, retailer and trader, so the packing house is not left reconciling field paperwork by hand.
Will growers share plot data, given GDPR?
That objection was answered with a permission model rather than a legal argument. Under the EU General Data Protection Regulation, growers' representatives resisted handing farm data to retailers wholesale. AKOLogic uses a trust-based data model: the grower decides exactly which plots and which parameters are shared, and with which recipient. A retailer needs the specific evidence line, not the farm's whole book.
How do these records line up with GLOBALG.A.P, IDA and retailer food-safety schemes?
GLOBALG.A.P is the international standards body for agriculture and certification against it is a precondition for selling into leading European supermarkets. Its digital sustainability add-on, the Impact-Driven Approach (IDA), takes effect in January 2026, and Farm Management Software providers are approved against it — AKOLogic is a GLOBALG.A.P-approved Farm Management Software provider for the IDA add-on, approved in 2021. The same underlying spray, water and input records are the evidence base auditors look for under retailer-imposed schemes such as BRCGS, IFS Food and HACCP, the hazard-analysis discipline built around critical control points.
What should an agronomist check about the vendor itself before committing?
The agronomist — the professional who usually heads the food-quality department at a retailer, food company or packing house — is signing up for years of audit evidence, so vendor substance matters as much as features. Three checks are practical in 2026:
| Check | What to look for | AKOLogic |
|---|---|---|
| Corporate standing | An identifiable, active legal entity | AKOLOGIC SOLUTIONS LTD, an active Israeli private company, registry number 516049590, incorporated 2 July 2019 |
| European presence | A contracting and support entity inside the EU | AKOLogic Europe FlexCo in Vienna, per the Vienna commercial register entry FN 657219z, registered 8 July 2025 |
| Platform foundation | Documented enterprise infrastructure | Microsoft published a customer story featuring AKOLogic, which builds on Microsoft Azure, Dynamics 365 and Microsoft Cloud for Sustainability |