Custom FarmResult integration
FarmResult, based in Wierden, makes farm management software for poultry farming, pig farming and integrators: an app for the farmer and a desktop environment for the chain partner. FarmResult already has integrations with housing systems, slaughter data and feed deliveries. But a feed company's ERP, a slaughterhouse's quality system or an integrator's own dashboard are not always included. Appfront builds the integration between FarmResult and those systems, so the farm's data is recorded once and is correct throughout the chain.
What is a FarmResult integration?
A FarmResult integration lets the FarmResult farm management software exchange data with the systems around it. FarmResult was founded in 2011 by Richard ten Cate and brings the data of a poultry or pig farm together in one app: animal health, feed, weight, climate, mortality, medicine records and tasks, with alerts for deviating results and a comparison with previous rounds. For integrators, FarmResult brings together the links in the chain, from rearing, breeding and hatchery to laying hens or broilers and the slaughterhouse. The integration puts that data into your own systems and sends back what FarmResult needs.
According to its own website, FarmResult has standard integrations for slaughter data, feed deliveries and feed invoices, as well as integrations with ERP systems such as Microsoft Dynamics 365 and SAP. A custom integration covers the rest: an ERP or accounting system that is not supported as standard, your own data warehouse, a quality system, planning for placement and slaughter, or an overview for the adviser. Without an integration, that data travels by export or email, and someone ends up working with last week's figures.
We build custom integrations because every chain is set up differently. Whether you are an integrator, a feed company or a slaughterhouse, the systems you use, the data you need from the farmer and which side is the source for which data all determine how the integration works. FarmResult mentions standard APIs but does not publish public API documentation. In the first step, together with you and FarmResult, we look at which integration options exist for your environment.
Record once
On the farm, in the app.
Chain connected
Feed, planning and slaughter.
Overview
Your figures in one place.
How we build your FarmResult integration
We start with your chain: how FarmResult is set up at your company and at the connected farms, which systems run alongside it, which data currently moves by export or email and who uses it. Then we build the first integration, usually the flow that takes the most manual work, such as feed and weight data to the ERP or the slaughter planning. You work with it for a few rounds. Other flows and checks follow once that runs well. After that, we maintain the integration when FarmResult, the regulations or your other systems change.
Farms, systems, manual work.
The biggest time saving first.
More flows and checks.
Go-live, monitoring, and maintenance when things change.
What a FarmResult integration actually does
The components below appear in almost every FarmResult integration. Which ones you need depends on your place in the chain and the systems you use.
Integration data
Feed, weight and mortality.
Feed
Deliveries and stock.
Planning
Placement, delivery and slaughter.
Quality
To your quality system.
Permission
Recorded per farmer.
Reporting
To your own overview.
Who we build a FarmResult integration for
The integration is intended for organisations that work with FarmResult and also have systems that do not talk to it as standard. The more farms and houses in your chain, the more it delivers.
Integrations
The whole chain in view.
Compound feed companies
Feed and results connected.
Slaughterhouses
Planning and quality.
Large farmers
Multiple locations.
Technology and integrations
This page is about integrations with FarmResult. If you work with Pig'Up or Geofolia, see our page on the ISAGRI integration; for sharing farm data with the farmer's consent, see our page on the JoinData integration; for your ERP, our page on the Microsoft Dynamics 365 integration; and if you want your own software for the supply chain, our page on agri-food software. You can read about our approach on building software.
Why Appfront for your FarmResult integration?
A slaughter schedule drawn up with last week's weights, a feed delivery recorded differently in two systems, or an adviser who receives the figures by email: each costs a supply chain money and visibility. That is what we build on: record data once at the farm, give every data point a clear source, and an integration that shows you when something went wrong.
Less retyping
Data comes along automatically.
Reliable
One source per data item.
Visible
Errors in the log.
Security and privacy in a FarmResult integration
The integration processes farm data from livestock farmers, such as production, feed and medicine use. It sends only the fields that are needed and gives a supply chain partner access only to the farms and data for which the farmer has given consent. Every exchange is logged with time and content.
The integration runs in a European data centre, with encrypted connections. Keys and passwords are stored securely and are not visible to staff. If a farmer withdraws consent, the exchange stops for their farm.
Frequently asked questions about a FarmResult integration
Questions asked by integrators, feed companies and livestock farmers before they get started.
A connection between FarmResult's barn management software and another system you use, such as your ERP, quality system, planning or your own reporting. Feed, weight and flock data then flow across automatically, without exports or email.
Barn management software from Wierden for poultry farming, pig farming and integrators, founded in 2011 by Richard ten Cate. The farmer works in an app, while the supply chain partner works in a desktop environment with the data the farmer shares.
Yes. According to its own website, FarmResult integrates with existing barn systems and has standard integrations for slaughter data, feed deliveries, feed invoices and ERP systems such as Microsoft Dynamics 365 and SAP. A custom integration is for the systems and flows not covered there.
FarmResult mentions standard APIs for bringing data into the supply chain, but does not publish public API documentation. Which integration options are available for your environment, and under what conditions, we clarify with you and FarmResult in the first step.
The farmer. With FarmResult, the farmer shares their farm data with the supply chain partner via the app. The integration respects that: only data from farms that have given consent, and only the fields that are needed.
The integration retries, and puts an exchange that keeps failing in an error list with the reason. You can see which farm and which flock it concerns, and send it again after correcting it.
For integrators, feed companies and slaughterhouses with many connected farms, and for livestock farmers with multiple sites and their own administration. A farmer with a single barn and the standard integrations usually doesn't need one.
Want FarmResult to work with your other systems?
Tell us how FarmResult is used in your chain and which systems run alongside it. We'll show you how an integration can take over the manual work.