Digital agriculture: which interventions fund it, checked at source

For holdings, at the date of our check the agency portal lists DR 20 investments in the livestock sector, DR 16 investments in vegetables and potatoes, DR 19 non-productive on-farm investments, DR 26 setting up irrigation systems, DR 30 support for the installation of young farmers and sub-measure 4.1 for simple machinery purchases. Orchards have their own intervention, DR 15. Processing carries DR 22, for conditioning, storage and processing of agricultural and fruit products, and DR 23, for processing into food and transformed products. Producer groups have DR 33, and rural public utility infrastructure DR 25, DR 27 and DR 28.

The basis on which software enters is the stated objective of the interventions themselves: strengthening market orientation and increasing the competitiveness of farms, including a greater focus on research, technology and digitalization. For irrigation the agency points explicitly to Specific Objective 2 of Articles 73 and 74 of Regulation (EU) 2021/2115 of 2 December 2021. There is therefore no budget line called digitalization: there is the demonstrated contribution of the solution to the competitiveness of the holding, and that is written and defended inside the project.

Sessions are announced individually through the project submission sessions section, and the live state is read in the available funds counter the agency publishes: the intervention, the sector, the session allocation, the launch date and time, the closing date and time, the submission cap, the value and number of projects submitted, the funds remaining. The agency itself warns that the values update with both submitted and withdrawn projects, so available funds can fall or rise during a session.

We publish no ceilings, aid intensities or scores taken from unofficial sources, and at the date of the check we had no submission deadline to quote for the investment interventions. What can be stated without inventing figures: farm digitalization scores at selection wherever the intervention's grid provides for it, and a project that documents its digital component seriously — with specifications, a budget and an identified supplier — stands better than one that mentions it in passing.

European Digital Innovation Hubs offer digital maturity assessments, technology testing and adoption guidance. They are useful before investing, but the nature of the support is often described incorrectly: an EDIH delivers services, not money in the account.

More important for anyone seeking funding: the farm is not the applicant in an EDIH call. The applicant is the hub, and the enterprise receives support through the hub as non-financial state aid granted under a contract. Any material inviting you to submit a project to an EDIH describes the mechanism wrongly, and time lost on that track is time taken from preparing the real file.

For holdings: management applications with a work log, plot maps, herd records, input stocks, cost per crop and reports for inspections. For processing units: batch traceability, raw-material intake, labelling and production reports. For direct sales: simple ordering platforms for customers, shops and hospitality. Sensors and weather stations are budgeted together with the application that interprets them — sensors without visualization mean data nobody uses.

Indicatively, digitalizing a small holding sits inside the bands we publish for small companies: EUR 1,000–5,000 for online presence, EUR 5,000–25,000 for internal processes and above EUR 25,000 for integrated flows. The figures are indicative and move with the number of plots or production lines, the integrations and the volume of migrated data; the firm estimate comes in writing after analysis.

We are not agricultural consultants, we do not draft funding applications and we issue no eligibility verdicts. Even for software, whether a cost qualifies belongs to the intervention guide and the evaluator, and if a solution we designed does not fit, we say so before submission.

What we refuse even when it costs us: we do not propose features that inflate the budget without serving the holding. When price reasonableness is checked, one unjustified line damages the whole budget rather than only its own row — and a module bought and never used stays a real cost after the project ends.