The Farming Equipment and Technology Fund puts up to £75,000 per farm towards equipment and technology. The question farmers keep asking: can you use it for software? The short answer is no. FETF explicitly excludes standalone software purchases. But the longer answer matters more, because the equipment it does fund generates data that your farm management software needs to process. If your software cannot use that data, you have bought an expensive piece of hardware that works for the supplier's ecosystem instead of yours.
FETF 2026 operates across three themes: Productivity, Animal Health and Welfare, and Slurry. Grant values range from £1,000 to £25,000 per theme, up to £75,000 combined. All items must be new or ex-display and meet minimum specifications.
What IS eligible is physical equipment that includes integrated software as part of the hardware purchase. An EID handheld reader that comes with its own app is fundable. Buying a software subscription for an EID reader you already own is not.
This is where it gets interesting for farm software. Many FETF-eligible items produce data that farm management software needs to process. The grant pays for the hardware. Your software determines whether that hardware works for you or just for the equipment vendor's own dashboard.
| FETF Equipment | Data It Generates | What Software Must Do |
|---|---|---|
| EID handheld readers | Individual animal ID, weight, treatment, movement records | Import EID scans, link to animal records, submit movements to LIS |
| GPS guidance systems | Field-level application data, tramline accuracy, area coverage | Download GPS data, link to crop records, generate compliance reports |
| Yield monitoring equipment | Per-field yield data with GPS coordinates | Import yield maps, compare against inputs, calculate gross margins per field |
| Soil sampling equipment | Nutrient levels, pH, organic matter by field zone | Store soil test results, generate variable rate application maps, track SFI evidence |
| Weighing systems (livestock) | Individual and batch weights with dates | Import weight data, track growth rates, identify underperformers |
| Camera grading systems | Automated quality assessments with image records | Store grading data, link to batch records, generate traceability reports |
| Robotic / automated systems | Operating hours, performance metrics, alerts | Monitor equipment status, log maintenance, track operating costs |
Connect with us about farm management software · · Replies within 24 hours
Most farm management software does not integrate cleanly with most hardware. An EID reader from one manufacturer exports data in a format that one software platform handles well and another ignores entirely. A John Deere GPS system sends its data to John Deere Operations Center easily. Moving that same data into another farm system usually needs a manual export and import.
This means the farm software you run determines how much value you extract from FETF-funded equipment. If your software can import, process, and act on the data your hardware generates, the grant investment compounds. If it cannot, you have an expensive piece of equipment that generates data nobody uses.
Equipment vendors design their hardware to work best within their own software ecosystem. This is not a conspiracy: it is a natural commercial incentive. John Deere equipment feeds John Deere software. Gallagher EID readers work best with Gallagher's own platform. Tru-Test scales integrate most smoothly with their own livestock management tools.
Your farm data can end up split across three or four vendor dashboards. None of them talk to your main farm system. None talk to your accounts or your compliance records. The grant paid for the hardware. The vendor controls the data.
The alternative is software that puts you in control. You want one system that reads data from any EID reader, whatever the make. It should take GPS data from any guidance system, and weight records from any scale. It should then hold all of it in one view of the farm. This is not a theoretical advantage. On one farm the data reaches a decision. On another it sits in separate vendor portals that nobody opens after the first week.
The equipment is not the problem. A reader, a scale and a guidance system each record correctly.
The problem is that each maker describes an animal, a field and a weight in its own way. Your farm system describes them differently again. Somebody must therefore write a rule that matches one to the other, for every pair.
A wrong rule does not raise an error. It passes a value that the receiving system accepts, and the number is then wrong with no warning.
We build farm systems on engage.re. Your record types are declared before any data exists, and the server refuses a write outside that declaration. A wrong meaning therefore fails at the moment of the write, and not months later in a report.
We explain why a connection alone does not fix this in MCP and A2A move messages. We explain how to keep your data portable in vendor lock-in, what can you prove.
A bespoke farm management system can be built to integrate with whatever hardware your farm actually runs, regardless of manufacturer. If you buy EID readers through FETF, the bespoke system imports their data directly. If you buy GPS guidance, the system reads the application files. The hardware generates the data. Your system uses it. No vendor lock-in. No manual re-entry.
For farms investing £25,000-£75,000 in FETF-funded technology, the software that ties it all together is not an afterthought. It is the difference between technology that transforms your operation and technology that collects dust.
Connect with us about farm management software · · Replies within 24 hours
Our live farm demo opens without a login, and it covers the equipment data in this article. Sign in as owner and see the FETF grant evidence capture in the operations log, or as worker and geotag the equipment. It is a working system, not a screenshot.