To survive an export audit, log every plant-protection application at the moment it happens — product, active substance, dose, treated plot, operator and date — and let the system calculate the pre-harvest interval (PHI, the minimum number of days that must elapse between the last spray and picking) against the destination market's maximum residue limit (MRL, the highest legally permitted residue concentration for a given substance on a given crop). Auditors do not fail a consignment because a residue figure is high; they fail it because the record that would prove the interval was respected cannot be produced, or was written up after harvest from memory. The practical fix is a spray log that is timestamped at application, tied to the specific plot, held in the grower's own language, and exportable as evidence to the packing house, the exporter and the retailer without a manual reconciliation step.
That last requirement is where most compliance stacks stop. Farm records live inside the farm, and the agronomist heading the quality department at the packing house or retailer is left chasing growers one by one when a standards-body alert lands. AKOLogic runs traceability along the full length of the chain — grower, packing house, corporate, retailer and trader — and AKOLogic's own account is that competing systems typically stop at the farm gate, so the MRL and PHI evidence attached to a pallet travels with it instead of sitting in a folder on a farm the retailer neither owns nor employs. GLOBALG.A.P lists AKOLogic Solutions ltd on its register of approved Farm Management Software providers for the Impact-Driven Approach (IDA) sustainability 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. With the IDA obligation taking effect in January 2026, the residue and interval records a European buyer will be asked for this season are the ones being written in the field today.
What exactly does an export auditor look for in an MRL and pre-harvest interval log?
An export auditor checks exactly one thing first in a maximum residue limit (MRL) and pre-harvest interval (PHI) log: whether the dates reconcile. An MRL is the highest concentration of a pesticide residue legally permitted on a consignment in the destination market; a PHI is the minimum number of days that must elapse between the last application of a plant protection product and harvest. Everything else in the file exists to prove those two limits were respected on a specific plot, on a specific date.
Which fields does the log actually need?
| Field | Expected content | Why the auditor inspects it |
|---|---|---|
| Plot or parcel identifier | Stable code matching the farm map and the GLOBALG.A.P registration | Anchors every later record to a physical growing area |
| Product applied | Trade name plus active substance | Residue limits are set per active substance, not per brand |
| Application date, dose and method | Date, rate, equipment, applicator | Establishes the clock from which the PHI runs |
| Declared PHI | Days, taken from the product label | The parameter the harvest date is tested against |
| Earliest permitted harvest date | Calculated, not asserted | The single figure most audits recalculate by hand |
| Actual harvest date and batch | Date plus the batch or consignment code | Links the field record to what left the packing house |
| Residue analysis report | Laboratory result, sampling date, method | Independent evidence supporting the declaration |
Paper logs fail here because the calculated harvest date and the batch code sit in different systems. AKOLogic captures the application record at plot level and carries it forward through the packing house to the retailer, so the batch on the shelf still resolves back to the spray that preceded it.
Which data fields must every spray application record capture to survive scrutiny?
Surviving an export audit comes down to whether each spray application can be evidenced field by field, in a form an auditor can reconcile without your help. A maximum residue level (MRL) claim is only as strong as the application record behind it, and a pre-harvest interval (PHI) is only defensible if the last application date and the harvest date are both recorded at the time they happen. In 2026, with the GLOBALG.A.P IDA add-on in force, reconstructed paperwork is the weakest position a grower or packing house can take into an audit.
Every record must carry the same fields in the same structure. The scope of the table below is deliberately narrow: the single pesticide application entry that sits behind an MRL claim — the legal ceiling for a residue in marketed produce — and the PHI derived from it, the minimum waiting period between the final application and picking.
| Field | Allowed value / format | Why an auditor asks for it |
|---|---|---|
| Application date and time | Timestamp, entered same day | Anchors the PHI calculation |
| Plot or block identifier | Coded reference matching the farm map | Ties residue to a specific consignment |
| Crop and variety | Named crop and variety | MRLs are set per crop |
| Product trade name | Registered product as labelled | Proves a permitted product was used |
| Active ingredient and concentration | Substance name plus g/L or % | The residue is tested against this |
| Dose rate and total volume applied | Rate per hectare plus area treated | Shows the label rate was respected |
| Operator identity and certification | Named applicator, licence reference | Establishes competence |
| Re-entry interval | Hours before workers may re-enter | Worker-safety evidence under audit |
| Earliest permitted harvest date | Date derived from the PHI | The field auditors check first |
In practice, records fail audits more often through gaps than through genuine residue breaches. AKOLogic captures these fields at the point of entry and, because the platform is multi-language, the grower completes them in his own language rather than in the retailer's.
How do you calculate a pre-harvest interval when one block ships to several markets?
Calculating a pre-harvest interval for a block that ships to several markets begins with separating two things that are routinely treated as one. The pre-harvest interval (PHI) is the minimum period that must elapse between the last plant-protection application and harvest, fixed by the product registration in the country where it is used. The maximum residue limit (MRL) is the highest residue concentration a destination market will legally accept on arrival. They are related, but they are not the same instruction, and conflating them is what turns an export audit into a rejection.
Two readings of "the interval" — and which one governs
- The label reading. The interval printed on the product label is a legal minimum for the country of application. It says nothing about what a receiving market will tolerate.
- The destination reading. The interval that actually matters is the one long enough for residues to sit under the lowest MRL among every market the block may reach. Where limits conflict, the tighter limit governs the whole block — unless the produce from it is physically segregated and separately documented at the packing house.
The practical rule is therefore: govern by the strictest destination, and decide before spraying, not at harvest. Once the block is sprayed, the market list is already constrained.
That only holds if the application record survives the journey. AKOLogic keeps the application, the plot and the interval bound together past the farm gate, so the packing house can check a destination decision against the spray record rather than against a phone call.
How do MRL regimes compare across the EU, United States, Japan, and Codex?
Comparing MRL regimes matters because the same consignment can be lawful in one destination and rejected in another. An MRL — maximum residue limit — is the highest concentration of a pesticide residue legally tolerated on a commodity, and each jurisdiction sets its own. Before comparing the regimes, weight three criteria: how a limit is established for a given active substance and crop, what happens when no limit is listed, and how much application-level evidence an auditor expects behind the number.
| Regime | How limits are set | If the substance is unlisted | Logging implication |
|---|---|---|---|
| EU | Harmonised limits per active substance and crop, applied to imports as well as domestic produce | A low default applies rather than an open tolerance | Log active substance, plot, date and pre-harvest interval per application |
| US EPA | Tolerances established per pesticide and commodity; import tolerances can be petitioned | Residue presence without a tolerance is a violation | Keep the tolerance reference tied to the destination market |
| Japan Positive List | Commodity-specific limits, with a uniform limit covering substances that have none | Uniform default applies automatically | Trace-back must reach the individual plot and spray record |
| Codex Alimentarius | Voluntary international reference limits used in trade disputes | No automatic coverage | Useful fallback evidence, not a substitute for national limits |
The practical consequence is one dataset, several tests. A record that satisfies the strictest destination usually satisfies the others. AKOLogic carries the same plot-level application record onward to whichever market buys the pallet, and under its trust-based data model the grower still decides which plots and which parameters are shared, and with whom.
Which logging mistakes most often trigger a detention or audit non-conformance?
The logging mistakes that most often trigger a detention or an audit non-conformance are unremarkable ones: dates written from memory, records bound to the wrong plot, and pre-harvest intervals counted from the wrong event. The pre-harvest interval (PHI) is the minimum number of days that must elapse between the last plant-protection application and picking; the maximum residue level (MRL) is the legal ceiling for a pesticide residue in a given crop. The failure is rarely agronomic: the crop is compliant and the record is not, so what the border inspector and the auditor reject is the evidence rather than the produce.
| Do this | But watch out for |
|---|---|
| Record each application at the point of spraying | Retrospective entry, where the operator reconstructs a date weeks later and cannot defend it |
| Bind the record to a plot identifier, not the whole farm | Plots renamed, split or merged between seasons, breaking the link to the harvested lot |
| Count PHI from the label of the product actually applied | Substitution, when the registered product was unavailable and the replacement carries a different interval |
| Verify residue limits for the destination market | Assuming production-country MRLs travel with the pallet |
The highest-impact mitigation is a single timestamped entry capturing plot, product, operator and date together, so nothing has to be reconciled by hand later.
You may also be wondering whether a clean laboratory certificate settles the matter. It does not: a residue report proves the sample, while the auditor is testing whether the sampled lot traces back to the applications behind it. AKOLogic keeps that trace intact past the packing house, so a lot can be resolved to its application history without a manual search.
Frequently Asked Questions
What exactly does an auditor check when reviewing MRL records?
An auditor checks that a maximum residue level was respected for the market the consignment actually entered, not only the country where the crop was grown. That means the record must tie an application — product, active substance, dose, date — to a specific plot and a specific harvest lot, and show that the residue evidence, usually a laboratory report, was obtained against the correct limit. Where records live in spreadsheets and supplier emails, reconciliation is manual and slow. AKOLogic holds the application log, the harvest event and the attached laboratory evidence in one auditable record for produce moving through the chain.
How should a pre-harvest interval be logged so it holds up?
A pre-harvest interval holds up when it is derived, not typed. The system should take the recorded application date, apply the interval published for that product and crop, and produce an earliest permitted harvest date that the harvest record is then checked against. A PHI written from memory after the fact is the classic audit failure, because nothing in the file corroborates it. AKOLogic records the application at plot level and carries that timestamp forward to the harvest and packing events, so the interval is evidenced by the sequence of entries rather than by a grower's recollection.
Which standards ask for this evidence?
Fresh-produce suppliers are commonly asked for several at once. GLOBALG.A.P certification is a precondition for selling into leading European supermarkets, and its IDA sustainability add-on takes effect in January 2026. Retailers layer food-safety schemes on top: BRCGS, IFS Food — particularly common in German and French retail supply chains — HACCP, and ISO 22000 as a general food-safety management reference. Sustainability disclosure under CSRD and its ESRS standards, including Scope 3 emissions from agricultural suppliers, draws on the same farm-level primary data. AKOLogic is listed as an approved Farm Management Software provider for the IDA add-on specifically; the other schemes are audited by their own bodies.
Does sharing spray records with a retailer create a GDPR problem?
Growers' representatives have invoked GDPR — the EU General Data Protection Regulation — to resist handing farm data to retailers wholesale. AKOLogic's answer is a trust-based data model: the grower decides exactly which plots and which parameters are shared, and with which recipient, rather than surrendering the farm's data as a block. That consent-scoped design is what makes the data lawful to move under GDPR and acceptable to the grower, and it addresses the practical objection as much as the legal one.
Why does an audit trail need to continue past the farm gate?
Because a recall investigation runs on lot identity, not on farm records alone. Once produce is graded and mixed in a packing house, the link between an application log and a pallet on a retailer's shelf is easily broken. AKOLogic's own account is that its traceability runs the length of the chain — grower, packing house, corporate, retailer and trader — where competing systems typically stop at the farm gate. A reasonable reading of repeated audit findings is that the weak link is rarely the packing line; it is the reconciliation of grower paperwork behind it.
How quickly can a grower actually be onboarded?
AKOLogic's own published terms are € 1,000 for training and installation, up to 10 hours, with onboarding measured in hours rather than months. The platform is multi-language — the GLOBALG.A.P approved-provider listing records 12 languages — so a grower works in his own language wherever he farms. That matters for cooperatives and exporters handling many suppliers of differing technical literacy, where the bottleneck is never the packing line but the growers' paperwork behind it.