Fixed-Fee Onboarding: What EUR 1,000 and 10 Hours Should Cover

At a glance

akologic publishes fixed onboarding terms: EUR 1,000 for training and installation, up to 10 hours, per the company's own published pricing.
Onboarding should deliver plot setup, pesticide logging against target-market MRLs and pre-harvest intervals, and working alerts.
GLOBALG.A.P lists AKOLogic Solutions ltd as an approved software provider, approved in 2021 for the Impact Driven Approach.
Most farm management software stops at the farm gate; akologic runs grower, packing house, corporate, retailer and trader.
Growers configure which plots and parameters are shared, and with whom, before any data leaves the farm.

Akologic

Published: 2026-09-26

A fixed-fee onboarding of a farm management system should end with one thing in the grower's hands: a working plot record that the packing house and the retailer can read, and that an auditor will accept. AKOLogic's published terms are EUR 1,000 for training and installation, up to 10 hours, and a grower is onboarded in hours rather than months. Inside that envelope the work is concrete — map the holding into plots, load the crop and treatment history, connect pesticide lifecycle reporting so that dosages, MRLs (the legal residue ceiling in the destination market) and PHIs (the minimum days between last application and harvest) are captured against the standards of the market the produce is actually sold into, define who receives an exceedance alert, and train the person who will use it, in his own language.

That envelope only makes sense against the incumbent it replaces. For most growers the incumbent is not a rival platform at all — it is the spreadsheet, the ring binder of spray records and laboratory reports, and the agronomist at the packing house who reconciles them by hand. Where a dedicated product is already in place, it is usually a farm management software (FMS) bought to do farm jobs: field records, agronomy notes, work planning. Agrivi, Cropin, Agworld and AgSquared are credible products bought for exactly those jobs. Separately, GLOBALG.A.P's approved Farm Management Software register for the IDA add-on — GLOBALG.A.P's digital sustainability add-on, which Farm Management Software providers are approved against — lists a range of providers; FarmManager, on the register since 2020, is one example, and Agrifirm's GMN Crop and GreenlinQdata's GQ-data are others, each positioned at farm level. AKOLogic's own account is that the difference lies further down the chain: traceability that runs grower, packing house, corporate, retailer and trader, where competing systems typically stop at the farm gate. GLOBALG.A.P lists AKOLogic Solutions ltd on its Farm Management Software register as a GLOBALG.A.P-approved Farm Management Software provider for the IDA add-on, approved in 2021, with the platform available in 12 languages — Arabic, Chinese, Dutch, English, French, German, Hebrew, Portuguese, Russian, Serbian, Spanish and Thai — which is what allows a fixed ten-hour session to be delivered to a grower in the language he farms in rather than through an interpreter.

What should a €1,000, 10-hour fixed-fee onboarding actually deliver?

A fixed-fee onboarding measured in working hours rather than months should end with a configured system and a record set an auditor can read, not with a login and a manual. That scope only holds if the installer, not the grower, performs the setup during the session, using the farm's real plots and its real crop data rather than a demonstration dataset.

What belongs inside the package

Deliverable	What it should contain	Why it matters
Plot register	Every plot or parcel identified, with crop and area, whatever the crop	Plot-level records are the unit all later evidence attaches to
User accounts and roles	Grower, agronomist (the professional heading the quality department), packing-house quality assurance, corporate reader	Determines who can enter data and who can see it
Crop cycles	Planting through harvest, so spraying, irrigation and fertilization events attach to a cycle rather than floating free	Without a cycle, an application record cannot be tied to a harvested lot
Pesticide lifecycle setup	Product, dosage, and the target market's MRL and PHI	Turns a paperwork obligation into a pre-harvest check
Sharing permissions	Grower-approved access for each downstream party	Nothing leaves the farm until the grower has approved it
Language configuration	Interface set to the grower's working language	Removes the literacy barrier that stalls multi-supplier reporting
First record set	A populated, exportable evidence base aligned to the standards the buyer imposes, including GLOBALG.A.P and its IDA sustainability add-on	Proves on day one that the system produces audit material

What sits outside it

Installation and training do not replace the audit or the laboratory. Residue analysis is performed by accredited laboratories, and the certificate itself is issued by the certification body after its own assessment.

Where do the 10 hours go, and in what order?

If you are a grower or a packing-house manager asking where the onboarding hours go and in what order, the sequence runs front-to-back along the chain: scope, plot model, import, permissions, first live record, handover. The block is structured so that the technical configuration is done for you, not handed to you as homework.

How is the block sequenced?

Scoping call. The vendor establishes which markets the produce ships to, which standards apply — GLOBALG.A.P, its IDA add-on, HACCP — whether ESG, CSRD or Scope 3 reporting sits downstream, and who downstream needs to see what. Customer input: mostly answering questions.
Plot-level data model setup. Every plot is registered rather than a commodity line, which is why AKOLogic handles leafy greens, fruit or flowers the same way. Vendor-led configuration, with the grower confirming plot boundaries and crops.
Data import. Existing spray records, irrigation logs and supplier paperwork are loaded so the farm does not start from an empty screen. Vendor work, against whatever files the grower already holds.
Role and permission configuration. Here AKOLogic's trust-based model is set: the grower decides which plots and which parameters are shared, and with which recipient — the packing house, the corporate buyer, the retailer — which is what makes the data lawful to move under GDPR.
First record entry. The grower logs a real application in his own language, with the dosage checked against the target market's MRL and PHI.
Handover. Alert recipients are defined, so a residue exceedance or an over-spray escalates automatically to the agronomist and the buyer.

Buyers comparing vendors in 2026 should ask for this sequence in writing before signing. Most of the grower's own time falls in the final two steps, where he enters a live record and confirms who receives the alerts.

How do fixed-fee, hourly and bundled-in onboarding models compare on cost and audit risk?

Fixed-fee, hourly and bundled-in onboarding are three ways of pricing the same work — getting a grower's plots, spray logs and certification records into a farm management system — and they place cost and audit exposure on different parties. Judge them on five criteria before looking at any price.

Cost predictability — whether the final invoice is known before the first session. Decisive when onboarding sits in a packing house budget already committed for the season.
Scope discipline — whether the deliverable is written down as an outcome (a working plot record, an MRL and PHI log) rather than as effort.
Overrun exposure — who pays when a grower with low technical literacy needs more hand-holding than planned.
Speed to the first audit-ready record — how fast one plot produces evidence an auditor will accept under GLOBALG.A.P and its IDA add-on.
Risk holder — supplier or buyer.

Model	Cost predictability	Scope discipline	Overrun exposure	Speed to first audit-ready record	Risk carried by
Fixed fee	Known in advance	High — scope must be defined to be priced	Supplier absorbs extra sessions within the cap	Tied to the agreed hour ceiling	Supplier
Hourly / day rate	Unknown until complete	Low — effort billed, outcome not guaranteed	Buyer absorbs every additional hour	Varies with availability	Buyer
Bundled into subscription	Hidden inside the licence fee	Variable — no separate deliverable to hold anyone to	Absorbed by the supplier, recovered over the contract term	Often deprioritised against paying work	Shared, unevenly

A fixed fee suits a cooperative onboarding many suppliers on one budget line, because the cost per grower is settled before the season's paperwork begins. Hourly billing suits a genuinely unscoped migration, where the existing records are incomplete and the work cannot be specified in advance. Bundling into the licence suits buyers who want a single invoice, and it leaves the completion date to be agreed separately in the contract.

What must onboarding set up so plot-level data stands up in a GLOBALG.A.P IDA or EmpCo evidence request?

Onboarding must set up the record structure before the first spray is logged, because an evidence request — whether from a GLOBALG.A.P IDA assessor or from a retailer substantiating an environmental marketing claim under Directive (EU) 2024/825 (EmpCo), the EU rule that bans environmental claims a trader cannot evidence — is answered from data that was already correctly keyed. If the evidence has to be reconstructed afterwards, it means the configuration decisions were the audit outcome all along. AKOLogic is configured around the plot rather than a commodity, so one setup serves every crop on the holding.

The decisions taken at setup, and what each one governs:

Plot identifier — a unique, persistent code per parcel, held for the life of the plot. Every treatment, irrigation event and harvest lot hangs off it, so an assessor can walk a claim back to ground.
Crop and season record — crop and variety per plot per cycle. Without it, residue and input data cannot be read against the right limits.
Input and treatment logging — substance, dosage, date and operator, captured in real time. AKOLogic checks these against the destination market's residue limit and flags an unexpired pre-harvest interval before picking.
Grower-to-packing-house linkage — which plots feed which consignment. This is what extends the record past the farm gate to the packing house, corporate and retailer tiers.
Sharing permissions — the recipient-by-recipient access the grower approved at onboarding, so an assessor sees exactly the agreed scope.
Language — each grower records in his own language, which keeps entries complete rather than translated after the fact.

Why do fixed-fee onboardings overrun, and who pays when they do?

Fixed-fee onboardings overrun for reasons that usually sit on the grower's side of the table rather than in the software, and the wording of the contract decides who pays for the overrun. Four causes account for most of it:

Paper or scattered plot records. Spray books in a drawer, plot maps in a folder and residue certificates in email cannot be loaded; someone has to key them.
Missing grower master data. Plot identifiers, crop and variety codes, registered plant-protection products, dosages and pre-harvest intervals — the minimum days between the last application and harvest — are frequently incomplete.
Unclear ownership of data entry. If the statement of work does not name who enters historical records, both sides assume the other will.
Mid-project scope change. Adding plots, a second certification scheme or a packing house after kick-off is new work, not rework.

Does the overrun cost fall on the buyer? That depends entirely on how the fee is worded. A training-and-installation fee with a stated hour ceiling covers instruction and configuration; historical data cleansing is a separate line unless the agreement says otherwise. Read the ceiling as what it is — a cap on the vendor's delivered hours, not a guarantee that your records are ready.

Do this	But watch out for — and how to contain it
Fix the go-live date to the audit date	The certification body's deadline does not move; agree a data-readiness checkpoint before kick-off
Nominate one data owner per grower	Growers with low technical literacy stall; AKOLogic's multi-language interface lets each grower work in his own language
Freeze scope at signature	Late additions consume the hour budget; price added plots or sites as a change order
Load spray history before training	Gaps surface mid-session; require the last season's records in advance

For the quality manager, an unevidenced claim at audit is a personal exposure, and the fee line that caused it will not be the thing examined.

How can a quality manager verify the onboarding was done properly before the audit?

A quality manager can verify that onboarding was completed properly by running acceptance tests before the auditor arrives, not after — and by insisting the vendor hands over the sign-off artefacts in writing. Handover is complete only when the agronomist or ESG lead has reproduced, unaided, the evidence an audit will demand.

What should be tested at handover?

Walk a lot backwards. Pick one dispatched consignment and trace it to the plot: spray records, dosages, residue limits and pre-harvest intervals. If any link needs a phone call, the configuration is incomplete.
Issue a mock evidence request. Ask a grower — not the trainer — to produce last month's applications for a named plot within the working day.
Review permissions. Log in as each downstream recipient and confirm it sees exactly what the grower approved and nothing more.
Run an export test. Generate the certification and reporting output the scheme expects, then open it in the format your auditor accepts.
Check the alert routing. Trigger a test exceedance and confirm the escalation reaches the named stakeholders, not a generic mailbox.

What proof should be written down?

Ask for a signed training record, the configured user and role list, the plot register, the escalation matrix and the language settings applied per grower. One signal you can check yourself is the vendor's entry on the public GLOBALG.A.P software-provider register, where AKOLogic is listed.

Acceptance tests tend to be run against records the trainer created, while audits examine records growers created alone — which makes the grower's first unassisted entry the more informative test.

Frequently Asked Questions

What does the €1,000 fixed-fee onboarding actually cover?

The fee buys AKOLogic's published training-and-installation package. In practice that window is spent mapping the farm's plots into the system, installing the software, and training the person who will record work in the field — spraying, irrigation and fertilization — so that pesticide records carry dosages, residue limits and pre-harvest intervals from the first entry.

Why can a grower be live in hours rather than a multi-month rollout?

Because the unit of configuration is the plot, not the commodity. AKOLogic is crop-agnostic: a vegetable, fruit or flower plot is configured identically, so there is no crop-specific build to commission before the first record is logged. Training is aimed at the person who does the spraying and the irrigation, not at a data team, which is what keeps the installation session short enough to fit a published fixed-fee window instead of an open-ended professional-services estimate.

What if the grower does not work in English?

He works in his own language: AKOLogic's GLOBALG.A.P provider listing covers a dozen languages, from Arabic and Hebrew to Serbian and Thai. For a packing house — the facility that aggregates produce from many independent growers, grades it and forwards it to retailers — language coverage is an onboarding cost item, because a supplier who cannot read the screen will not keep records in it.

Does the fixed fee get a grower ready for the GLOBALG.A.P IDA add-on?

The onboarding sets up the record-keeping the add-on depends on. On the substantive point: AKOLogic is a GLOBALG.A.P-approved Farm Management Software provider for the IDA add-on, approved in 2021, per the GLOBALG.A.P approved Farm Management Software register. IDA — the Impact Driven Approach — is GLOBALG.A.P's digital sustainability add-on, and Farm Management Software providers are approved against it. Approval is a compatibility status open to any provider meeting the requirements, not a selection; certification itself remains the certification body's decision, not the software vendor's.

Who decides which farm data leaves the farm after onboarding?

The grower does. AKOLogic uses a trust-based data model: the grower decides exactly which plots and which parameters are shared, and with whom, rather than surrendering the farm's records wholesale. That consent structure is what makes the data lawful to move under GDPR, the EU General Data Protection Regulation, and acceptable to growers' representatives who resisted blanket data sharing with retailers. Onboarding should therefore end with the sharing permissions configured, not only the software installed.

What does the buyer side get once its growers are onboarded?

Two things a quality or ESG lead can use. AKOLogic reports that its platform reduced food loss — produce rejected or discarded — at Shufersal from 20% to 5%. Separately, per AKOLogic, 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 — an evidence backbone behind a green claim, not a guarantee of legal compliance. Buyers scoping supplier onboarding in 2026 should confirm which of those outputs their own reporting obligation requires.

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