Digital farm logbook and pesticide records

How do you record every treatment without losing an afternoon each week? In Spain, the electronic pesticide record becomes mandatory on January 1, 2027. We build the logbook that records in the field, georeferenced, and syncs with the SIEX national system.

Royal Decree 34/2025 · electronic pesticide record mandatory from 1-1-2027

The data that makes it possible

Here the "data" is twofold: a regulation with a date, and public APIs that almost nobody uses. Each comes with its own caveats.

Royal Decree 34/2025 and SIEX

Spain’s digital farm logbook is voluntary as a general rule (article 9.1), but one obligation already has a date: the electronic record of pesticide treatments applies from January 1, 2027.

a deadline with a date: 1-1-2027

The data belongs to the farmer

The official SIEX technical document states that the information is the property of the farmer, and it accepts private logbooks synced with the system: your logbook can be yours and still comply.

private synced logbooks accepted

FEGA-ITACYL fertilization APIs

Eight public fertilization APIs (Fertilicalc, soils, waters) with tokens also available to private companies: the official engine behind nutrient plans, almost unknown.

8 public APIs · tokens for companies

Technical illustration: a hand holds a phone showing the farm map with three parcels marked in the field
Illustration: the logbook is filled in where the work happens, with the parcel underfoot.

What we build for you

A logbook that fits your farm, co-op, or service company: every treatment recorded from a phone, in the field, with a GNSS position and a geotagged photo; rule checks before saving, so every record arrives correct; upload to the official pesticide record and sync with SIEX; and nutrient plans computed on the official fertilization APIs. If you already use a DSS or a farm ERP, we connect through an API or MCP, so your data is entered once.

A field record, georeferenced and checked before saving

Every treatment is logged from a phone on the parcel itself, with the GNSS position and a geotagged photo. Before saving, the logbook checks the rule: product allowed for that crop, dose within limits, safety interval, and a suitable weather window. The record arrives correct the first time and uploads to the national pesticide record and SIEX without a second pass.

GNSS + geotagged photo · checked before saving

A nutrient plan on the official APIs

From your parcels and your soil and water data, we compute the fertilization plan on the eight public FEGA and ITACYL APIs, the same engine behind Fertilicalc. The result is the nitrogen and other nutrient units each parcel needs, within what the rules require, and it is stored in the logbook itself.

FEGA-ITACYL APIs · 8 public services

Traceability with context, and an export for inspection

Each record keeps position, date, product, and the context of that day: the crop status Sentinel-2 saw and the SiAR weather. When an inspection comes, you export the full, traceable logbook in one step, with every treatment placed on its parcel and its moment. The data is entered once and serves both to comply and to decide.

dated traceability · export for inspection

Who it is for

For those who must keep the records, and for those who must receive them:

Be ready before January 1, 2027

Tell us how you record your treatments today. We will propose the logbook that meets the rule without duplicating work.

Talk to the team