EU plant protection product register aggregator
A single database of the EU's national plant protection product registers, with scheduled synchronization, change detection and active substances grouped across languages.
Every member state publishes its own register of plant protection products, each with a different format, language and update frequency. This aggregator builds an EU plant protection products database from the official registers of 14 countries: it downloads them, brings them together in a single database, detects new products, withdrawals and status changes, and groups active substances even when each country writes them in its own language. You get one place to check what is authorized, where, and when that changed.
Who it is for
- Registration departments at manufacturers that track their own products and their competitors'.
- Distributors and exporters that check authorizations country by country.
- Plant protection registration consultancies that today go through dozens of portals by hand.
- Cooperatives and technical services that need to know what can be used in each country.
- Agricultural data companies that want their own database they can keep up to date.
What an EU plant protection products database solves
- Different portals. Following the registers by hand means visiting each portal, downloading files with different structures and comparing versions.
- Names that do not match. The same substance appears as azoxystrobin, azoxistrobina or azoksistrobin depending on the country.
- Changes that go unnoticed. Each synchronization is compared with the previous one, and new products, withdrawals and status changes are logged with their date.
- Sources that fail silently. If a portal does not respond, it is logged as an incident and the rest carry on.
What you can do with it
- Synchronize the official registers of France, Italy, Finland, Sweden, Slovenia, the Netherlands, Denmark, Spain, Austria, Croatia, Germany, Portugal, Czechia and Poland.
- On each run, download the latest official file, add new products, update status changes and mark products that have disappeared as withdrawn, without deleting them.
- Schedule synchronization every week and run it by hand for one or more countries.
- Load other registers on an ad hoc basis, plus the uses (crop and pest) from the countries that publish them.
- Match the most common active substances across languages with an extendable dictionary of variants, with their international name.
- Split the substances in combination products and standardize authorization statuses.
- Always keep the original data next to the standardized data, with a link to the source and the extraction date.
- Translate crops and pests into Spanish with an in-house dictionary, without AI services.
- Check a dashboard with coverage by country, imports, incidents and the most frequent substances.
- Search products with filters and open their record, with substances, uses, change history and equivalents in other countries.
- Compare a substance across Europe: in which countries it is authorized and in how many products.
- See the matrix of uses by substance and country, and add uses by hand that synchronization does not overwrite.
- Review the change log and the incident log by source.
- Export filtered products to CSV and upload files by hand, with a preview and column detection.
Benefits
- You stop checking 14 portals one by one.
- You find out about withdrawals and status changes without going through every register.
- You compare substances across countries even when each one uses its own name.
- Every data point keeps its origin and date, so you can check it at the official source.
Industry context
General industry data with its public source. These are not results of this product.
- A plant protection product can only be placed on the market or used if it has been authorized in the member state concerned. Source: Regulation (EC) No 1107/2009, Article 28(1).
- Each member state has to make information on authorized or withdrawn plant protection products publicly available by electronic means, and update it at least every three months. Source: Regulation (EC) No 1107/2009, Article 57.
What you get with each license
Price upon request, depending on license type and scope. Maintenance and support are contracted separately for every license type.
- The aggregator installed on your server or in your cloud, under a license to use, with your own synchronization schedule.
- Initial setup of the countries you are interested in and a first synchronization.
- Initial training for administrators.
- The complete source code, to add countries, integrate it into your platform or maintain it with your team.
- Installation and configuration documentation.
- A technical handover session with your team.
- A warranty against defects for the agreed period.
- Everything in the source code license.
- Our commitment not to license the product to third parties in the agreed sector or territory for the agreed term, for example a single agricultural data provider in one market.
- The right to embed the asset in a commercial product of your own, identified in the contract.
- The right to distribute it to your customers as part of that product, without asking for authorization for each installation and with no limit on end customers, unless otherwise agreed.
- It does not include reselling or sublicensing it on its own.
- It is not exclusive, unless otherwise agreed.
- Maintenance, support and adaptations are contracted separately.
Technical specifications
Language and runtime: TypeScript 5.9, and JavaScript in the synchronization scripts, on Node.js 20 (the version it is delivered with, declared in the scheduled synchronization workflow). Minimum supported version: Node.js 20.18.1 (required by undici 7, which is installed).
Frameworks: Next.js 15.5 and React 19.2.
Database: PostgreSQL. The application and the scripts connect through Neon's serverless driver over HTTP: Neon, or PostgreSQL behind a proxy compatible with that driver.
Operating systems: Linux, Windows or macOS with Node.js.
Interface languages: Spanish.
Required infrastructure:
- PostgreSQL, under the connection conditions above.
- A task scheduler with database access and Internet access for synchronization, for example GitHub Actions or cron.
- Access to the official register portals of each country.
Private deployment: The query application can run on your infrastructure without third-party services. Synchronization needs Internet access to each country's official portals.
Main libraries:
| Library | Version | License |
|---|---|---|
| next | 15.5.20 | MIT |
| react | 19.2.7 | MIT |
| @neondatabase/serverless | 1.1.0 | MIT |
| xlsx (SheetJS) | 0.18.5 | Apache-2.0 |
| adm-zip | 0.5.18 | MIT |
| undici | 7.28.0 | MIT |
| lucide-react | 0.454.0 | ISC |
Dependencies with specific license terms:
- @img/sharp-libvips-* 1.2 (libvips binaries installed by sharp, an optional dependency of Next.js): LGPL-3.0-or-later. The sharp 0.34 binaries for Windows and WebAssembly declare Apache-2.0 AND LGPL-3.0-or-later.
Compatibility and integrations: official registers of France (E-Phy), Italy (Ministero della Salute), Finland (KemiDigi), Sweden (KEMI), Slovenia (FURS), the Netherlands (CTGB), Denmark (BMD), Spain (REGFIWEB), Austria (BAES), Croatia (FIS), Germany (BVL), Portugal (SIFITO), Czechia (eAgri) and Poland (MRiRW); CSV, XLSX, ZIP and JSON files; scheduled workflow for GitHub Actions.
Redistribution terms
The asset's own code can be embedded in the licensee's commercial products under the source code, sector or territory exclusive and OEM licenses, on the terms of the contract. With the installed license, the software is used and not redistributed. Specific license terms apply to the libvips binaries (LGPL-3.0-or-later); see the list under Technical specifications.
Installation requirements
Installed on your server or in your cloud, including compatible cloud platforms, with a PostgreSQL database. Synchronization runs from any task scheduler with database access and Internet access.
Integrations
Official registers of France (E-Phy), Italy (Ministero della Salute), Finland (KemiDigi), Sweden (KEMI), Slovenia (FURS), the Netherlands (CTGB), Denmark (BMD), Spain (REGFIWEB), Austria (BAES), Croatia (FIS), Germany (BVL), Portugal (SIFITO), Czechia (eAgri) and Poland (MRiRW).
Frequently asked questions
How does it detect that a product has been withdrawn?
By comparing the downloaded register with the one already in the database: if a registration number stops appearing, the product is marked as withdrawn and the change is logged with its date. It is never deleted.
Does it use artificial intelligence?
No. Substance matching and the translation of crops and pests are done with dictionaries and rules, so the result can be reproduced.
Can a country that is not included be added?
Yes. Each country has its own connector, and adding a new one does not affect the rest. With the source code license you can do it yourself.
What happens if an official portal changes its format?
That connector fails, the incident is logged and the other countries synchronize as usual. The connector has to be adapted.
Can the data be reused freely?
It depends on each authority. Several registers are published as open data, but commercial use has to be checked against each source's terms. The tool does not replace checking the current authorization.
Is maintenance included?
No. Maintenance (updates, bug fixes and connector adaptations) and support (questions, training and adaptations) are contracted separately.
They fit with this asset
Request
Request information on P-AGR-01
Fill in the form with the asset reference and the license type you're considering. I reply in writing. If you need to review code, tick the NDA box and we'll sign one before anything is shared.