Crop data without retyping From grower to buyer Plots and operations in your own systems

Custom Dacom integration development

Appfront builds integrations with Dacom, the crop registration system in which growers record their fields and cultivation activities. Dacom exchanges data with buyers and advisers, including under the EDI-Crop standard. We connect that data to your own systems: grower registrations at your company as a buyer or trader, checks and certification, harvest and delivery planning, and figures per crop or region in your own dashboard.

What is a Dacom integration?

Dacom is a crop registration system in which growers record, per field, what they have done: sowing, fertilising, crop protection, irrigation and harvesting. Growers register in the app or on a computer, and the data can be shared with buyers and advisers. Dacom works with standardised cultivation data under EDI-Crop and offers partner integrations for sharing data between grower and buyer.

A buyer, such as a processor of potatoes, sugar beet or vegetables, receives cultivation data from hundreds of growers. That data has to be checked against the buyer's requirements, for example which products were used and when. Without an integration, it arrives as a file or PDF, is checked by hand, and is not in the system that plans harvest and delivery. An adviser only sees clients' registrations if they send them on.

We build custom integrations because the integration has to fit your role: are you a buyer, trader, adviser or contractor, which data do you need, which requirements do you check, and in which system does the data need to end up? We look at which route for exchanging data with Dacom fits in the first step, together with you and, where necessary, with Dacom. Growers give their own consent for what they share.

Registrations at the buyer

Growers' cultivation data straight into your system, per grower, field and crop, without files or PDFs.

Checks against your requirements

Registrations checked against the requirements of you as a buyer or of certification, with deviations flagged for review.

Harvest and delivery

Cultivation data linked to harvest and delivery planning, and figures per crop in your dashboard.

How we build your Dacom integration

We start with your role and your systems: which data you receive, from how many growers, what you check, and where things are still done by hand.

1
Mapping data and requirements

Which cultivation data, from which growers, which requirements and which systems.

2
Building the integration

The exchange with Dacom connected to your system, with the grower's consent.

3
Checks and planning

Checks against your requirements, and integration with harvest, delivery or advice.

4
Testing and maintenance

Testing with real registrations, going live before the season, and maintenance when things change.

What a Dacom integration actually does

The components below come up in almost every Dacom integration. Which ones you need depends on your role.

Plots

Fields and crops per grower, by growing year.

Cultivation activities

Sowing, fertilising, crop protection, irrigation and harvesting.

Validation

Registrations tested against the requirements of the buyer or certification.

Permission

Which data is shared with whom, per grower.

Planning

Cultivation data for harvest and delivery planning.

Dashboard

Figures per crop, grower and region in your dashboard.

Who we build a Dacom integration for

The integration is intended for anyone who uses growers' cultivation data in their own systems.

Processors

Many growers per crop. Checking against requirements is the core.

Traders and cooperatives

Sales for members and growers. Delivery planning matters most.

Crop advisers

Advice based on registrations. What you need is insight per client.

Agricultural contractors

Work for many growers. Passing operations back to the grower is the core.

Technology and integrations

This page is about integrations with Dacom. For custom parcel registration, see our page on parcel registration for arable farming, for certification our page on GlobalG.A.P. crop registration, and for the sector our page on agri-food software. You can read about our approach on custom software development.

Dacom crop registration EDI-Crop Fields and crops Cultivation activities Consent per grower Checks against requirements Harvest and delivery planning Certification Dashboard Log per exchange

Why Appfront for your Dacom integration?

Crop data that arrives as PDFs gets checked late, or not at all. We build on that: records straight into your system, checks against your requirements, and data that feeds your planning.

No files

Records arrive directly, per grower and per plot.

Checks on time

Deviations stand out before the harvest, not after.

Grower stays in control

The grower decides what is shared.

Security and privacy in a Dacom integration

The integration processes growers' crop data, which is business data they share with their consent. Access is set up per role, and it is recorded per grower which data is shared with whom.

The integration runs in a European data centre, with encrypted storage, daily backups and a log of every exchange.

Frequently asked questions about a Dacom integration

Questions that buyers and advisers ask before getting started.

Dacom is a crop registration system in which growers record, per plot, what they have done, such as sowing, fertilising, crop protection and harvesting. Growers record in the app or on a computer, and can share data with buyers and advisers.

Dacom exchanges data with buyers and advisers, including via the EDI-Crop standard and through partner integrations. Which route suits you and which data is available is something we look at in the first step, together with you and, where necessary, with Dacom.

Yes. Growers decide for themselves which data they share with whom. The integration records per grower what has been shared, and uses only that data. If a grower withdraws consent, the exchange stops for that grower, and what was received earlier remains visible.

Yes, against the requirements you set, for example which products are permitted, pre-harvest intervals or the completeness of the record. Deviations are held for review, so you see them before the harvest. Per grower and plot you can see what was checked, by whom and with what result.

They need a different route, for example another registration package or an input form. The integration can bring multiple sources together, so you see all growers in a single overview.

The integration reports it and records what went wrong. The exchange is retried or queued for review, so no record is lost.

For buyers, traders and advisers who need crop data from many growers in their own systems, where it currently arrives as a file or PDF.

Growers' crop data straight into your system?

Tell us which data you receive, from how many growers, what you check and which system it needs to go into. We'll show you what the integration looks like.

Edit content